Plan307 - Plan307 - Ostrowski

Enterprise Network
Requirements for Lync

Server 2013
Mariusz
PLAN307
Ostrowski
UC Architect
Microsoft Corporation
Instructors
Mariusz Ostrowski
UC Architect
Microsoft, Voice Center of Excellence
I spent 12 years at Cisco as IPT/UC Consulting
Systems Engineer.
I joined Microsoft as UC Architect
in Microsoft Voice Center of Excellence team
I hold the following professional certifications:
Cisco Certified Internetwork Expert (CCIE) since 1999
Microsoft Certified IT Professional on Lync since 2012
I live with my wife Dorota in Poland.

I love to hike in the mountains.
Session Objectives And Takeaways

Session Objectives
Have a better understanding of broad scope of Networking and QoS, not just Lync aspect of
it.
Present the new Lync 2013 Bandwidth utilization model and the associated tool.
Key Takeaway
Discussion with networking people and common planning is crucial for success of Lync
deployment
Agenda
Networking 101
QoS - basics
QoS for Lync 2013
Network bandwidth for Lync 2013
Networking 101
Networking 101 Vocabulary

ANs
Wide Area Networks
Local Area Networks
Layers
Layer 2 (L2) nowadays most often Ethernet frames, even in WAN networks
Layer 3 (L3) IP and all associated stuff, seen in both WAN and LAN
oSs
CoS Class of Service, traffic marking mechanism used at L2 in LAN
ToS Type of Service, traffic marking used at L3 in both LAN/WAN
DSCP Differentiated Services Code Point (application of DiffServ), similar to ToS, just
more classes
Networking 101 Vocabulary

VPN
Virtual Private Network
QoS
Quality of Service
MPLS
Multi Protocol Label Switching
Networking 101 MPLS network

MPLS network
(in short: MPLS)
Multi Protocol Label Switched network

is a L3 WAN
built by a service provider
to sell its bandwidth
to many customers
and allows to guarantee a quality of service (QoS)
MPLS
MPLS
MPLS
MPLS
network allows for site-to-site (any-to-any) traffic

mechanisms provide L3 (IP) traffic separation between customers
network allow for service level agreements (SLAs) based on quality of service (QoS)
service provider often also provides Internet services (in the same MPLS cloud)
Networking 101 Network Types

Types of WANs and their topologies
MPLS nowadays, typically
Internet? Yes, is a WAN network too !

One of its kind
Public, not a private WAN
Can not guarantee vital parameters of real time transmission through it, though
What is IP VPN vs. Internet VPN?

IP VPN = MPLS
Internet VPN = WAN built as overlay encrypted tunnels over the Internet
Networking 101 A word or two

on
WiFi
Yes, the Wi-Fi is supported for Lync 2013
Including audio and video workloads
Delivering Lync 2013 Real-Time Communications over Wi-Fi

whitepaper:
http://blogs.technet.com/b/nexthop/archive/2013/01/24/white-paper-delivering-lync-2013-real-time-communication
s-over-wi-fi.aspx
http://www.microsoft.com/en-us/download/details.aspx?id=36494
Also check out another session at this

conference
Networking 101 Impairments
Latency, jitter, packet loss

What are they?
Do they affect just Lync audio (voice) ?
How about video ?
Can they affect my other Lync traffic (e.g. IM/P) ?
Networking 101 how much Lync can

survive
Recommendations
(max/optimal)
Quality Metric (avg)for delay/jitter/loss
Key Notes
Thresholds (for avg)
Round Trip Time (RTT)
(as reported by Lync Monitoring)
Not the latency!
Network Round Trip Time (RTT) is the

most common measure of latency and is
measured in ms.
This measure is the average round trip
time for RTP packets between endpoints.
When latency is high, users will likely
hear the words, but there will be delays
in sentences and words.
For RTP packets as reported in the

monitoring reports:
< 200 ms is good

> 200 ms is poor
> 500 ms is bad
Network Infrastructure Requirements Lync Server 2013

http://technet.microsoft.com/en-us/library/gg425841.aspx
Provision your network to ensure a maximum end-toend delay (latency) of 150 milliseconds (ms) under
Understanding QoE Alerting
peak load.
A Primer on Lync Audio Quality Metrics
(NOTE: a non-Microsoft source)
http://blog.insidelync.com/2012/06/a-primer-on-lync-audio-quality-metrics/

survive
Recommendations
(max/optimal)
Key Notes
Jitter
Variability of packet delay

Results in a distorted or choppy audio
experience.
Jitter can increase total latency
(due to increase of de-jitter buffer)
< 20 ms is good
> 30 ms is not good
(but can be ok)
> 45 ms is considered very bad



survive
Recommendations
(max/optimal)
Key Notes
Represents the % of packets that did not
make it to their destination.
Packet loss rate
Packet loss will cause the audio to be

distorted or missing (on the receiver
end).
< 3% is considered good

> 5% will impact audio
> 7% is not good
(some consider +7% huge)
> 10% is very bad


QoS basics
QoS
What 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 a word from Microsoft IT

The importance of QoS
cannot be overstated in our
100,000+ user Enterprise
Voice production environment.
We experienced a significant
increase in quality after
uniformly enforcing and
Optimizing Lync 2010 Enterprise Voice Performance:auditing QoS settings.
http://technet.microsoft.com/en-us/library/jj650858.aspx
Network congestion
Thing of the past ?
Its not anymore about 64 Kbps WAN link being saturated at 100% all the time
Nowadays its about
critical 15MB antivirus version update
thrown from GigEth server in DC
to 500 users on 100 Mbps WAN link
15
500
7500
60000
MB update
users
MB total
Mbit total
100 Mbit/s WAN link

600 seconds
10 minutes of WAN congestion (*)
(*) this is simplified math, in reality periods of congestion will be shorter, but spread in much longer ti
QoS mechanisms
Bottom line - treat different types of traffic
differently
Based on defined traffic classes
Different treatment = different QoS

mechanisms
Queuing is the most common
Shaping and congestion avoidance are the other ones
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 marking
L2 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:
QoS traffic classification

methods
Port based (L3)
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
Short Overview of QoS Mechanisms and Their
PCs are also capable of DSCP marking, and if that is trusted classification of this type can
A
Interoperation:
QoS - queuing
QoS based on DSCP markings - example

Yes, these things can get really complex
Beware of different QoS Policies

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

Layer 3 link
Admin (data)
Admin (voice)
Classroom
(video)
QoS Policy (5 classes)

802.1p value
Voice:
6
Video:
5
Signaling:
4
Default:
0
Scavenger:
1
Faculty (data)
Faculty (voice)
Classroom
(video)
QoS Policy (3 classes)

DSCP queue
46
7
36
6
26
5
0
3
14
1
802.1p value
Voice:
6
Video:
5/4
Default:
0/1
DSCP
46
36/26
0/14
queue
4
3
1
QoS and Lync 2013
QoS for Lync what Lync client

has
to
do
If Lync marks its traffic, then network can do
the job
Apply DSCP traffic marking via GPO
Managing Quality of Service (QoS)

in Network Planning for Lync Server 2013:
Microsoft Lync Server 2010

Quality of Service (QoS) Deployment Guide
QoS for Lync non-client Lync

traffic
Server-initiated Lync traffic
Internet based (remote) Lync clients
Lync IP phones
Traffic coming from the SIP Trunk
Managing Quality of Service (QoS):
Validate end-to-end QoS

Beware 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.
Monitoring the QoS

Lync Monitoring Server is your best friend
In Lync 2013 the Monitoring Server role is co-located with a Front End
Also check out two other sessions at this conference

OPER200 - Lync Network Diagnostics
OPER304 - Monitoring Lync - ensuring optimal performance in operations
Network Bandwidth
for Lync 2013
Network Bandwidth for Lync 2013

Types of Network traffic in Lync 2013
Traffic flows in Lync 2013
New model for Bandwidth Modeling
Lync 2013 Bandwidth Calculator
Types of Lync 2013 traffic

Server-to-server
Intra-pool and SQL BE
Over the LAN
Inter-pool
SIP Signaling
Data replication for backup pool
User-generated
Signaling
Media
Content
Types of Lync 2013 user generated

traffic
SIP signaling
presence)
Significant
and(Includes
predictable
Instant Messaging
Peer-to-peer audio and video
Multiparty audio
Multiparty video
PSTN audio
Desktop/application sharing
Types of Lync 2013 user-generated

traffic
May be significant, but hard to predict
File transfer
PowerPoint sharing
Conference attachments
Persistent Chat communication
Lync 2013 user-generated traffic

flows
which have not changed from Lync 2010 (or not
SIP much
signaling,
that
) including IM and presence
Peer-to-peer audio (*)
Multiparty audio (*)
PSTN audio
Desktop/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
2010
Peer-to-peer video
Lync 2013 introduces H.264 SVC Stereo codec and simulcast capabilities
Lync 2013 can use RTVideo (VC-1) codec for backward compatibility
Lync 2013 supports plethora of resolutions (from sub-CIF to Full HD)
Multiparty video
Lync 2013 introduces MultiView gallery
Lync 2013
Front End
Server
Lync 2013 Video peer-to-peer
Central Site
Flow
Client-to-client
P2P with H.264 SVC

4:3 and 16:9 aspect ratios (+20:3 for Panorama)
Broad range of resolutions from sub-CIF up to 1080p
Bandwidth requirements depend on:
Video window size (user behavior)
PC capabilities (CPU cores, HW acceleration)
Typical vs. Maximum

460 Kbps typical for common window size distribution
4010 Kbps maximum for Full HD
Add 10 Kbps for RTCP
Branch Site 1
Branch Site 3
Branch Site 2
Lync 2013
Front End
Server
Lync 2013 Video peer-to-peer
Central Site
Flow
Client-to-client
P2P with H.264 SVC

4:3 and 16:9 aspect ratios (+20:3 for Panorama)
Broad range of resolutions from sub-CIF up to 1080p
Bandwidth requirements depend on:
Video window size (user behavior)
PC capabilities (CPU cores, HW acceleration)
Typical vs. Maximum

460 Kbps typical for common window size distribution
4010 Kbps maximum for Full HD
Branch Site 1
Branch Site 3
RTVideo
Backward compatibility with Lync 2010 clients
Branch Site 2
Lync 2013
Front End
Server
with AVMCU
Lync 2013 Video conferencing
Central Site
Flows
Client-to-AVMCU
Multiview with H.264 SVC
Branch Site 1
Branch Site 3
Branch Site 2
Lync 2013
Front End
Server
with AVMCU
Central Site
Flows
Client-to-AVMCU
MultiView with H.264 SVC

Multiple video streams in 16:9 aspect ratios
but clipped to square tile
Branch Site 1
Branch Site 3
Branch Site 2
Lync 2013
Front End
Server
with AVMCU
Central Site
Flows
Client-to-AVMCU

Max 5 active video tiles, but typically only 2-3
Same range of resolutions from sub-CIF up to 1080p
but in reality single tile resolution typically 240p
Desktop sharing further reduces tile size (to 180p)
Branch Site 1
Branch Site 3
Branch Site 2
Lync 2013
Front End
Server
with AVMCU
Central Site
Flows
Client-to-AVMCU

Simulcast multiple streams
Multiple active video tiles (downstream)
Various resolutions required (upstream)
Branch Site 1
Branch Site 3
Branch Site 2
Lync 2013
Front End
Server
with AVMCU
Central Site
Flows
Client-to-AVMCU

Multilayer temporal scalability

Branch Site 1
15 fps
Branch Site 3
Branch Site 2
Lync 2013
Front End
Server
with AVMCU
Central Site
Flows
Client-to-AVMCU

Lync 2010 clients present (upstream and downstream)
Multilayer temporal scalability

Add 15 Kbps for RTCP (because of Lync 2010 clients)
Branch Site 1
15 fps
Branch Site 3
Branch Site 2
New model needed for Capacity

Planning!
Typical Video Bandwidth in Lync 2013
Model is based on data from Lync 2013

Preview deployments at Microsoft and TAP
customers
Video usage (not BW!) doubled compared to Lync

2010
20.0%
18.0%
16.0%
14.0%
12.0%
P2P calls: Send/Receive

BW
10.0%
Percentage of calls
8.0%
6.0%
4.0%
P2P video calls:
2.0%
0.0%
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
Average send/receive video bandwidth
Average video bandwidth per user in Kbps
New model needed for Capacity

Planning!
Typical Video Bandwidth in Lync 2013
30.0%
MultiView conference video calls:

Typical screen real estate allows for tiles
with resolution of 424x240 (clipped to
square)
Receive: average of 2.5 video streams
Send:
average of 1.6 video streams
Data sharing reduces screen real estate
for video in most calls, results in small
video resolution of 320x180
25.0%
Conf calls: Receive BW
20.0%
Conf calls: Send BW
15.0%
Percentage of calls
10.0%
5.0%
0.0%
Average video bandwidth per user in Kbps
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-topeer scenario because many video conferences
are using content sharing that leads to much
smaller video windows and thus smaller video
resolutions.
Lync 2013 Bandwidth

Calculator
Its 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 done
Requires Microsoft Excel 2010 or 2013 (macros must be enabled)
Demo
Lync 2013 Bandwidth Calculator
Session Takeaways
Session Objectives hopefully achieved
Have a better understanding of broad scope of Networking and QoS, not just Lync aspect of
it.
Present the new Lync 2013 Bandwidth utilization model and the associated tool.
Key Takeaway
Discussion with networking people and common planning is crucial for success of Lync
deployment
Resources
Managing Quality of Service (QoS) Lync 2013
Network Bandwidth Requirements for Media Traffic Lync 2013

Lync Bandwidth Calculator

http://www.microsoft.com/download/en/details.aspx?id=19011
as well as many other articles or blogs mentioned in this slide deck
Other related session @

PLAN 305 - Lync Mobile Devices and Wi-Fi
LyncConf13
OPER200 - Lync Network Diagnostics
OPER304 - Monitoring Lync - ensuring optimal performance in
operations
PTNR301 - HP: Network Design and Deployment Strategies to
Ensure Success for Lync 2013 Enterprise Voice
2013 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.
Appendix A
Lync 2013 Bandwidth

Calculator
Its 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 done
Requires Microsoft Excel 2010 or 2013 (macros must be enabled)

Step-by-step workflow is described in Start Here tab of the tool
Central Sites
Central Sites are where Lync Front End pools will be

located
If Lync deployment will have mulitiple distributed Lync FE pools, then enter multiple
Central Sites (unless all FE pools are in the same network site)
WAN links must be defined
WAN link speed is the total size of connection to the MPLS WAN cloud
WAN link BW Allocated to RTC traffic is how bandwidth customer wants to allow for
Lync RTC
Typically should be assumed 30% of WAN link (industry-standard for RTC traffic on the WAN links)
Global Red flag threshold set to this value, but can be defined to level expected by customer
59
Central Sites Internet

access
If the Central Site has Lync Edge servers in it, then it should be
defined as Internet Site
Typically 1:1 relationship between Central Sites and Internet Sites

Central Site can also use Edges located from another Internet Site
Branch Sites will inherit Internet Site from their assigned Central Site
60
Branch Sites
Branch Sites are sites with Lync users only

Branch Site must be associated with one of Central Sites
If many similar branches, one row can summarize

them
Branch Site might have local PSTN gateways

If it does, then select Local PSTN Breakout = Yes
(with Media Bypass on, or when Mediation server is also located in that branch, adjacant to the voice
gateway)
If it doesnt, than set Use G711 for PSTN Calls over WAN? correctly
(read the
comment)
61
Personas and Users

Sites can have users
Users have to be grouped based on Personas
Up to three persona types selected individually in each site
62
Results - individual
Individual results WAN link consumption
split per modality
Intersite traffic only

Traffic of users located in this site only
63
Results - totals
Branch-level traffic totals

and limit/threshold checks
Total WAN BW for all traffic

Total RTC traffic
All audio, all video, all conferencing
64
Aggregated results
Table 1 WAN traffic aggregated in each Central Site

Split by Lync modality
Totals (WAN and Lync RTC) with limit/threshold checks
Audio / video / conferencing total
65
Aggregated results
Table 2 Internet traffic of Remote Users, aggregated in each

Internet Site
Split by Lync modality
Totals with limit/threshold checks
66
Graphical results
Lync RTC bandwidth requirements and availability

Helps to quickly identify which sites might be lacking bandwidth for Lync
Can choose which sites are to be graphed
67
Bandwidth Calculator and QoS

An example of advanced task
RESULT
RESULT
68

Plan307 - Plan307 - Ostrowski

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Plan307 - Plan307 - Ostrowski

Caricato da

Copyright:

Formati disponibili

Enterprise Network

Requirements for Lync

I live with my wife Dorota in Poland.

Session Objectives And Takeaways

Networking 101 Vocabulary

Networking 101 Vocabulary

Networking 101 MPLS network

(in short: MPLS)

Multi Protocol Label Switched network

network allows for site-to-site (any-to-any) traffic

Networking 101 Network Types

Internet? Yes, is a WAN network too !

What is IP VPN vs. Internet VPN?

Networking 101 A word or two

Delivering Lync 2013 Real-Time Communications over Wi-Fi

Also check out another session at this

Networking 101 Impairments

Latency, jitter, packet loss

Networking 101 how much Lync can

Network Round Trip Time (RTT) is the

For RTP packets as reported in the

< 200 ms is good

Network Infrastructure Requirements Lync Server 2013

A Primer on Lync Audio Quality Metrics

(NOTE: a non-Microsoft source)

Networking 101 how much Lync can

Variability of packet delay

Network Infrastructure Requirements Lync Server 2013

Understanding QoE Alerting

A Primer on Lync Audio Quality Metrics

(NOTE: a non-Microsoft source)

Networking 101 how much Lync can

Packet loss rate

Packet loss will cause the audio to be

< 3% is considered good

Network Infrastructure Requirements Lync Server 2013

Understanding QoE Alerting

A Primer on Lync Audio Quality Metrics

(NOTE: a non-Microsoft source)

When is QoS needed?

QoS a word from Microsoft IT

100 Mbit/s WAN link

Different treatment = different QoS

QoS traffic classification vs.

QoS traffic classification

A Short Overview of QoS Mechanisms and Their

QoS traffic classification

DSCP marking (most ubiquitous and

QoS based on DSCP markings - example

Beware of different QoS Policies

Remote site QoS domain #2

QoS Policy (5 classes)

QoS Policy (3 classes)

QoS and Lync 2013

QoS for Lync what Lync client

Managing Quality of Service (QoS)

Microsoft Lync Server 2010

QoS for Lync non-client Lync

Validate end-to-end QoS

Validating QoS on Lync Endpoints:

Monitoring the QoS

Also check out two other sessions at this conference

Network Bandwidth for Lync 2013