with live demos classroom (video) admin (data) admin (voice) faculty (data) faculty (voice) layer 3...

63

Upload: ophelia-wilkerson

Post on 22-Dec-2015

218 views

Category:

Documents


2 download

TRANSCRIPT

Craig Hill, Mariusz Ostrowski, Justo Oreja VegaUC ArchitectsMicrosoft Corporation

Enterprise Networking with Lync 2013: Network Bandwidth and QoS Requirements

Have a better understanding of broad scope of QoS, not just Lync aspect of it.

Discuss Lync 2013 bandwidth requirements.

Session Objectives

IntroductionQoS basicsQoS and Lync 2013Network bandwidth for Lync 2013 (especially video)

Agenda

with LIVE

DEMOs

Introduction

Lync adds new traffic in the networkNetworking can help us build our credibilityReduce support cases - Statistics from Premier

Why is network planning important?

Customer Impact

Networking Review – Impairments

Latency, jitter, packet lossWhat are they?Do they affect just Lync audio (voice) ? How about video ? Can they affect my other Lync traffic (e.g. IM/P) ?

QoS basics

QoSWhat is QoS?Quality of Service (QoS) is a combination of networking technologies that enables organizations to optimize the end-user experience for real time audio and video communications

When is QoS needed?QoS is commonly used when network bandwidth is limited(which in practice means – almost always)

QoS is needed when there is a possibility of network congestion(which again means – almost always)

QoS is the end-to-end thing

Lync Server 2013 Networking Guidehttp://blogs.technet.com/b/nexthop/archive/2013/06/04/lync-server-2013-networking-guide-network-planning-monitoring-and-troubleshooting-with-microsoft-lync-server.aspx

“QoS helps to guarantee the bandwidth available for configured traffic flows. […]

Configure QoS end-to-end.”

QoS – a Word from Microsoft IT

“The importance of QoS cannot be overstated in our 100,000+ user Enterprise Voice production environment.

In many instances of voice quality issues, the root cause was that QoS settings were not applied end to end

We experienced a significant increase in quality after uniformly enforcing and auditing QoS settings.”

“Optimizing Lync 2010 Enterprise Voice Performance”:http://technet.microsoft.com/en-us/library/jj650858.aspx

QoS mechanisms

Bottom line - treat different types of traffic differentlyBased on defined traffic classes

Different treatment = different QoS mechanismsQueuing is the most commonShaping and congestion avoidance are the other ones

How network devices distinguish various traffic typesPort VLANs 802.1p/CoS DiffServ/DSCP/TOS/IP Precedence MPLS TAGs

QoS – traffic classification vs. marking

QoS – traffic classification methods (L2)VLAN priority

All traffic on a certain VLAN is assigned to a certain traffic class (e.g. Voice VLAN)

Typical in legacy VoIP / IPT environments with just IP phones (i.e. no soft-clients)

802.1p markingL2 priority mechanism, cannot scale beyond L3 (IP subnet) boundary

Only available on Ethernet links with 802.1q tagged VLAN

A Short Overview of QoS Mechanisms and Their Interoperation:http://technet.microsoft.com/en-us/library/bb742477.aspx

QoS – traffic classification methods (L3)Port based

All traffic arriving from or destined to a certain UDP or TCP port(s) is assigned is to the same traffic class

Cumbersome in configuration and maintenance, thus not really appreciated by “networking people” (except when used for initial marking or re-marking)

DSCP marking (most ubiquitous and recommended)

Simplifies end-to-end QoS design and scales easily (if supported in HW at line rate)

Builds on top of earlier IP Precedence (TOS) approach

Based on marking that can be assigned (sometimes is assigned by default) by most IP phones and custom video devices

PCs are also capable of DSCP marking, and if that is trusted – classification of this type can be used

A Short Overview of QoS Mechanisms and Their Interoperation:http://technet.microsoft.com/en-us/library/bb742477.aspx

QoS - queuing

QoS based on DSCP markings - exampleYes, these things can get really complex…

Beware of different QoS Policies

Classroom (video)

Admin (data)Admin (voice)

Faculty (data)Faculty (voice)

Layer 3 link

Classroom (video)

Main campus – QoS domain #1 Remote site – QoS domain #2

QoS Policy (5 classes)

802.1p value DSCP queueVoice: 6 46 7Video: 5 36 6Signaling: 4 26 5Default: 0 0 3Scavenger: 1 14 1

QoS Policy (3 classes) 802.1p value DSCP queueVoice: 6 46 4Video: 5/4 36/26 3Default: 0/1 0/14 1

QoS and Lync 2013

QoS for Lync – what Lync client has to doIf Lync marks its traffic, then network can do the jobApply DSCP traffic marking via GPO

Managing Quality of Service (QoS) in Network Planning for Lync Server 2013:http://technet.microsoft.com/en-us/library/gg405409.aspx

Microsoft Lync Server 2010 Quality of Service (QoS) Deployment Guidehttp://www.microsoft.com/en-us/download/details.aspx?id=12633

Enabling QoS for Lync Server 2013https://www.shudnow.net/2013/02/16/enabling-qos-for-lync-server-2013-and-various-clients-part-1/

QoS for Lync – non-client Lync trafficServer-initiated Lync trafficInternet based (remote) Lync clientsLync IP phonesTraffic coming from the SIP Trunk

Managing Quality of Service (QoS): http://technet.microsoft.com/en-us/library/gg405409.aspx

QoS for Lync – which DSCP values to use?Lync Server 2013 Networking Guidehttp://blogs.technet.com/b/nexthop/archive/2013/06/04/lync-server-2013-networking-guide-network-planning-monitoring-and-troubleshooting-with-microsoft-lync-server.aspx

“A good starting point would be to configure all voice real-time traffic to use DiffServer Code Point 46, with video configured for 34. Configure SIP Signaling traffic to use 24. Mark other modalities according to business requirements.

Because these are only recommendations, make sure that you’re using the markings that have been agreed upon as part of your enterprise’s existing QoS strategy.”

Validate end-to-end QoSBeware of incorrectly configured network devices (routers, wireless access points, switches) which might:• set or change DSCP markings to something you did not

intend• strip DSCP markings (set to 0)

Validating QoS on Lync Endpoints:http://blogs.technet.com/b/nexthop/archive/2012/12/19/validating-qos-on-lync-endpoints.aspx

Monitoring the QoS Lync Monitoring Server is your best friendIn Lync 2013 the Monitoring Server role is co-located with a Front End

Demo

Demo #1 (Ideal World vs Reality)Lync and impact of network impairments

Demo #1

Site E is connected using 512 Kbps WAN link

File

transfer

Lync P

2P

call

CLIENTA and CLIENTB will be in a Lync P2P audio call Then CLIENTE will initiate file transfer to DC1

Demo #2

Lync QoS/DSCP – applying, troubleshooting and monitoring

Demo #2

Situation like in Demo #1CLIENTA and CLIENTB are in a Lync P2P audio call CLIENTE has a file transfer to DC1

File

transfer

Lync P

2P

call

Lync QoS (DSCP marking) enabled in CLIENTA and CLIENTB

QoS (priority queue) enabled in WAN router

Network Bandwidth for Lync 2013

Network / Bandwidth EstimationLync Server 2013 Networking Guidehttp://blogs.technet.com/b/nexthop/archive/2013/06/04/lync-server-2013-networking-guide-network-planning-monitoring-and-troubleshooting-with-microsoft-lync-server.aspx

“2.3 Bandwidth Estimation

Bandwidth estimation is the key consideration when deploying Lync Server. Actually, network estimation would be a more apt term, because the communication streams within Lync Server rely more on latency and packet loss than they do on raw available network bandwidth.

To understand the role of network estimation, you must also recognize the various communication flows within Lync Server. Coupled with the user personas, you can then use this information within the Lync Bandwidth Calculator to understand, per modality, the volume of traffic that using Lync Server will likely generate.”

Changes in Lync 2013 vs. Lync 2010 flowsLync 2013 video flows and bandwidth consumptionModeling with Lync 2013 Bandwidth Calculator

Network Bandwidth for Lync 2013

Lync 2013 user-generated traffic flows which have not changed from Lync 2010 (or not that much )SIP signaling, including IM and presencePeer-to-peer audio (*) Multiparty audio (*)PSTN audioDesktop/application sharing

* Lync 2013 introduces G.722 Stereo codec with Lync Room System

Lync 2013 user-generated traffic flows which have dramatically changed from Lync 2010Peer-to-peer video

Lync 2013 introduces H.264 SVC Stereo codec with temporal scalabilityLync 2013 can use RTVideo (VC-1) codec for backward compatibility (simulcast)Lync 2013 supports plethora of resolutions from sub-CIF to Full HD

Multiparty videoLync 2013 introduces MultiView gallery (simulcast)

Lync 2013 video flowsand bandwidth consumptionDISCLAIMER: I don’t want to cause you a headache

Lync 2013 – Video peer-to-peer

P2P with H.264 SVC4:3 and 16:9 aspect ratios (+20:3 for Panorama)Broad range of resolutions from sub-CIF up to 1080pBandwidth requirements depend on:

Video window size (user behavior)PC capabilities (CPU cores, HW acceleration)

Typical vs. Maximum 460 Kbps typical for common window size distribution4010 Kbps maximum for Full HD

Add 10 Kbps for RTCP

Lync 2013 Front End Server

Central Site

Branch Site 2

Branch Site 1

Lync 2013 – Video peer-to-peer

P2P with H.264 SVC4:3 and 16:9 aspect ratios (+20:3 for Panorama)Broad range of resolutions from sub-CIF up to 1080pBandwidth requirements depend on:

Video window size (user behavior)PC capabilities (CPU cores, HW acceleration)

Typical vs. Maximum 460 Kbps typical for common window size distribution4010 Kbps maximum for Full HD

Add 10 Kbps for RTCP

RTVideoBackward compatibility with Lync 2010 clients

Lync 2013 Front End Server

Branch Site 2

Branch Site 1

Central Site

Lync 2013 – Window size impact on videoWindow size / screen real estateSize of Lync video window can be adjusted by the Lync user at any time (up to the size of screen real estate)

Video impactVideo streams are re-requested by the receiving Lync client with either higher (= more bandwidth) or lower resolution (= less bandwidth)

Understanding Lync Video Reportshttp://blog.schertz.name/2013/06/understanding-lync-video-quality-reports/

Lync 2013 – Network impact on videoBad network conditionsBad network conditions (especially significant packet loss) can force Lync client to re-request video stream from sender

Video impactVideo streams are re-requested with lower resolution (= less bandwidth)

Video resolution decreased

Lync 2013 – Video conferencing

MultiView with H.264 SVC

Branch Site 3

Branch Site 2

Branch Site 1

Lync 2013 Front End Server

with AVMCU

Central Site

Lync 2013 – Video conferencing

MultiView with H.264 SVCMultiple video streams in 16:9 aspect ratios but clipped to square ”tile”

Add 10 Kbps for RTCP

Branch Site 3

Branch Site 2

Branch Site 1

Lync 2013 Front End Server

with AVMCU

Central Site

Lync 2013 – Video conferencing

MultiView with H.264 SVCMultiple video streams in 16:9 aspect ratios but clipped to square ”tile”Max 5 active video tiles, but typically only 2-3Same range of resolutions from sub-CIF up to 1080pbut in reality single tile resolution typically 240p

Add 10 Kbps for RTCP

Branch Site 3

Branch Site 2

Branch Site 1

Lync 2013 Front End Server

with AVMCU

Central Site

Lync 2013 – Video conferencing

MultiView with H.264 SVCMultiple video streams in 16:9 aspect ratios but clipped to square ”tile”Max 5 active video tiles, but typically only 2-3Same range of resolutions from sub-CIF up to 1080pbut in reality single tile resolution typically 240p

Simulcast – multiple streamsMultiple active video tiles (downstream)Various resolutions required (upstream)

Add 10 Kbps for RTCP

Branch Site 3

Branch Site 2

Branch Site 1

Lync 2013 Front End Server

with AVMCU

Central Site

Lync 2013 – Video conferencing

MultiView with H.264 SVCMultiple video streams in 16:9 aspect ratios but clipped to square ”tile”Max 5 active video tiles, but typically only 2-3Same range of resolutions from sub-CIF up to 1080pbut in reality single tile resolution typically 240p

Simulcast – multiple streamsMultiple active video tiles (downstream)Various resolutions required (upstream)

Multilayer – temporal scalability Add 10 Kbps for RTCP

Branch Site 3

Branch Site 2

Branch Site 1

Lync 2013 Front End Server

with AVMCU

15 fps

Central Site

Lync 2013 – Video conferencing

MultiView with H.264 SVCMultiple video streams in 16:9 aspect ratios but clipped to square ”tile”Max 5 active video tiles, but typically only 2-3Same range of resolutions from sub-CIF up to 1080pbut in reality single tile resolution typically 240p

Simulcast – multiple streamsMultiple active video tiles (downstream)Various resolutions required (upstream)Lync 2010 clients present (upstream and downstream)

Multilayer – temporal scalability Add 15 Kbps for RTCP (because of Lync 2010 clients)

Branch Site 3

Branch Site 2

Branch Site 1

Lync 2013 Front End Server

with AVMCU

Central Site

15 fps

Lync 2013 – Data sharing impact on videoData sharingOccupies major part of a screen, when used with video on the same screen

Video impactDesktop sharing reduces tile size (typically to 180p) Video streams are re-requested with lower resolution (= less bandwidth)

Lync 2013 MultiView Gallery conference with video - resolutions and bandwidthshttps://campus.partners.extranet.microsoft.com/MSEngageKBDocuments/72013/Lync%202013%20MultiView%20Gallery%20conference%20with%20video%20-%20resolutions%20and%20bandwidths.docx

Lync 2013 – Multi-screen impact on videoMulti-screenData sharing occupies first screen, and second screen is used exclusively for video experience

Video impactDedicated screen real estate allows to increase tile size (back to 240p or maybe more) Video streams are re-requested with higher resolution (= more bandwidth)

Lync 2013 MultiView Gallery conference with video - resolutions and bandwidthshttps://campus.partners.extranet.microsoft.com/MSEngageKBDocuments/72013/Lync%202013%20MultiView%20Gallery%20conference%20with%20video%20-%20resolutions%20and%20bandwidths.docx

Lync 2013Typical Video Bandwidth

The way to avoid the headache

New model needed for Capacity Planning!Typical Video Bandwidth in Lync 2013 (for P2P video calls)

Model is based on data from Lync 2013 Preview deployments at Microsoft and TAP customers

Video usage (not BW!) doubled compared to Lync 2010

P2P video calls:

Heavily depends on user behavior

Plenty of resolutions possible from 180p to 1080p

~75% of users with default video resolution of 424x240

~25% increase video window to obtain 640x360 or HD video

15-4

0

40-7

0

70-1

00

100-

130

130-

200

200-

250

250-

300

300-

350

350-

400

400-

500

500-

750

750-

1000

1000

-150

0

1500

-200

0

2000

-300

0

3000

-400

00.0%

2.0%

4.0%

6.0%

8.0%

10.0%

12.0%

14.0%

16.0%

18.0%

20.0%

P2P calls: Send/Receive BW

Average send/receive Kbps per user

Perc

enta

ge o

f ca

lls

New model needed for Capacity Planning!Typical Video Bandwidth in Lync 2013 (for conference video)MultiView conference video calls:

Depends even more on user behavior

Typical screen real estate allows for tileswith resolution of 424x240 (clipped to square)

Data sharing reduces screen real estate for video in most conferences

Not all users actually use video Receive: average of 2.5 video streamsSend: average of 1.6 video streams

15-4

0

40-7

0

70-1

00

100-

130

130-

200

200-

250

250-

300

300-

350

350-

400

400-

500

500-

750

750-

1000

1000

-150

0

1500

-200

0

2000

-300

0

3000

-400

00.0%

5.0%

10.0%

15.0%

20.0%

25.0%

30.0%Conf calls: Receive BW

Conf calls: Send BW

Average send/receive Kbps per user

Perc

enta

ge o

f ca

lls

New model documented at TechNet

For the main video the typical and maximum stream bandwidth is the aggregated bandwidth over all received video streams and over all send video streams respectively.

Even with multiple video streams the typical video bandwidth is smaller than in the peer-to-peer scenario because many video conferences are using content sharing that leads to much smaller video windows and thus smaller video resolutions.

http://technet.microsoft.com/en-us/library/jj688118.aspx

Typical vs. Maximum – which should I use?

Typical - average consumption of bandwidth, seen in rather large population of Lync users, who also behave more-less “normally”

Maximum – maximum consumption of bandwidth, dealing with rather small population of users, or if you would suspect that users you are dealing with have quite unusual speech patterns

http://technet.microsoft.com/en-us/library/jj688118.aspx

Typical vs. Max

Typical vs. Max

It’s ”just” the tool for modeling the bandwidth consumption, so you must use your head as well

Information on Lync design is needed or some assumptions must be made

Consult the User Guide, ask [email protected] when unsure, and send us feedback !

Lync 2013 Bandwidth Calculator

Lync 2010 and 2013 Bandwidth Calculator http://www.microsoft.com/en-us/download/details.aspx?id=19011

Lync 2013 special cases for Video Bandwidth (LRS, Lync 2013 Mobile)

Sorry, but the headache might be back

Bandwidth for Lync Room Systems

LRS is 90% like Lync 2013 client, but …Audio - G.722 Stereo is used for audioVideo - oh, LRS has very large screen(s), so…Amount of screen real estate allows for larger resolutions in both P2P video and MultiView gallery

Default video user experience on LRS is differentLync P2P video calls to/from LRS start in full screen mode on LRS screen (UI suppression)• means larger resolution to LRS (expect 720p or 1080p stream from the very beginning)When LRS joins Lync 2013 video conference in MultiView gallery mode:• amount of screen real estate allows for video tiles with larger resolutions• 2-screen LRS might go for even higher resolutions since video tiles are distributed on

both screens

Bandwidth for Lync 2013 Mobile clientsDevice platform impacts capabilities and thus bandwidth (especially for video)Screen real estate limitationsPerformance limitations (factors: CPU power, hardware offload – WP8 only)Lync 2013 Mobile is not using RTAudio (Siren - P2P audio, G.722 - conf audio, G.711 - PSTN audio)Lync 2013 Mobile client is leveraging H.264 SVC and can rely heavily on temporal scalability

Network type (WiFi vs. 3G/4G) might have impact

Mobile Client Comparison Tables: http://technet.microsoft.com/en-us/library/hh691004.aspx

Summary

Session Objectives: Have a better understanding of broad scope of QoS, not just Lync aspect of it.Discuss Lync 2013 bandwidth utilization.

Key TakeawayProper network planning and interaction with networking team are key factors for quality of Lync audio and video.

Session Objectives And Takeaways

References

Lync Server 2013 Networking Guide (version 2, updated in January 2014)

http://blogs.technet.com/b/nexthop/archive/2013/06/04/lync-server-2013-networking-guide-network-planning-monitoring-and-troubleshooting-with-microsoft-lync-server.aspx

Enabling Quality of Service with Microsoft Lync Server 2010 http://www.microsoft.com/en-us/download/details.aspx?id=12633

Validating QoS on Lync Endpoints http

://blogs.technet.com/b/nexthop/archive/2012/12/19/validating-qos-on-lync-endpoints.aspx

Understanding QoE Alerting http://www.microsoft.com/en-us/download/details.aspx?id=9129

Lync 2010 and 2013 Bandwidth Calculator http://www.microsoft.com/en-us/download/details.aspx?id=19011

Related Content

Q&A

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.