Use of the tool Interpretation of results 2

YOU ARE HERE

Pre engagement Tools Logistics Kick-Off Meeting Discovery Session Usage Modelling Traffic Simulation Recommendations

Define sites Define WAN link bandwidth for each site Define bandwidth available for RTC Traffic Define Internet link bandwidth (for central sites) Create/update personas Define amount of users per site Analyze results

If you have specific guideline from customer If you are sure of what are you doing

Maximum 10 central sites in the tool Maximum 300 branch sites in the tool Branch Templates (see later in deck) Use names provided by the customer Input Units vs. Display Units WAN link speed is the total size of connection to the MPLS WAN cloud WAN link BW Allocated to RTC traffic is how a bandwidth customer wants to allow for Lync RTC This, 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 Lync RTC is all Lync traffic by default, but can be further refined as needed

Maximum 10 in the tool Assumes that Lync A/V Conferencing and Mediation servers are located together with Front End servers If Lync deployment will have multiple distributed Lync Front End pools, then enter multiple central sites (unless all Front End pools are in the same network site) These are centralized PSTN breakouts Will not be used by branch site users if branch site has its own local PSTN breakout

Internet sites are used to calculate Internet traffic from remote users, but these calculations also affect WAN calculations Typically 1:1 relationship between central sites and Internet sites Edges located in one Internet site can serve multiple central sites (1:N relationship) Branch sites will inherit Internet site from their assigned central site

Maximum 300 in the tool Branch site must be associated with one of central sites Tool assumes that all users in Branch will be assigned to the Lync Front End pool from this central site If an SBA will be used in the branch, it does not affect bandwidth modeling Branch Template approach (see next slide) If it does, then select Local PSTN Breakout = Yes (with Media Bypass on, or when Mediation server is also located in that branch, adjacent to the voice gateway) If it doesn’t, than set Low delay WAN? correctly (see next slide, read the comment in the tool)

Check out comment in the tool Set to Yes only if forcing Lync clients to use less bandwidth-consuming audio codecs

WAN links Personas and number of users For WAN links, use the lowest amount in these sites (if they are not exactly the same) For user count, use either average or maximum of users (how you want to model these sites) Individual site results – for a single branch template site Aggregated results – include all branch template sites

Users have to be grouped and entered into the tool based on personas Up to three persona types selected individually in each site “Total Users in Site” is for verification purposes If Lync servers are in a Data Center with no users in it, then just enter ”0”

Intersite traffic only Traffic of users located in this site only Traffic of remote users considered as necessary

See next slide Total WAN bandwidth for all traffic Total RTC traffic All audio, all video, all conferencing

Split by Lync modality Totals with limit/threshold checks Audio/video/conferencing total

Split by Lync modality Totals with limit/threshold checks

Individual site contribution to total amount of remote user traffic Not a traffic on a WAN link!

Helps to quickly identify which sites might be lacking bandwidth for Lync RTC traffic Useful for creating executive-level reports in a network assessment final report

Overall look at the whole Lync deployment Useful for creating executive-level reports in a network assessment final report RTC with or without video

This will change in the future… Assume O365 DC is central site Need to manually adjust bandwidth for PSTN audio to include G.711 traffic between Lync Mediation Servers and PSTN GWs/SBCs Assume O365 DC is central site PSTN Audio must be set to None Use only individual site results Do not use Aggregated Results Aggregate manually if necessary

23

Single MPLS cloud from a single WAN provider All workstations are wired when using Lync Symmetric WAN links QoS implemented and verified Historical bandwidth statistics available

Multiple inter-connected MPLS clouds Multiple MPLS providers in a single cloud with different QoS tagging and implementation Star (hub-and-spoke) or multi-layered WAN networks Highly assymetrical links (for example, cable, ADSL) VPN over Internet used as WAN On-demand connections (for example, dialup, ISDN)

The tool still can be used for modeling...

... but results might need manual adjustments All media paths need to be carefully analyzed upfront You might need to have additonal simulation endpoints

Modeling of the bandwidth consumption can still be done with Wi-Fi Modeling of AP/controller performance - work with Wi-Fi partners Make sure that you don’t provide “false safety” Risk that the customer must accept Network assessments might help to prove the need for QoS

Rule some as out of scope

YOU ARE HERE

Pre engagement Tools Logistics Kick-Off Meeting Discovery Session Usage Modelling Traffic Simulation Recommendations

http://www.microsoft.com/download/en/details.aspx?id=19011