In this recipe, we will learn how to analyze and interpret the results, and determine what sites are Lync-ready.
Browse to the Graphical results sheet and click on the Update tables and graphs green button.
We will be presented with summary site tables and two diagrams, which will give immediate visual indication of readiness, as shown in the following image (note that we have split the sections for better readability):
The first picture to look at is the one for Central Sites. The light bar in the preceding graph indicates our total RTC bandwidth availability for RTC (200 mbps), and the dark bar is the calculated amount of bandwidth required (57.51 mbps) to support Lync traffic for all branch sites associated with the Datacenter central site. The good news here is that we can safely assume our WAN capacity to the datacenter is more than enough.
The following graph provides a detailed breakup of the available bandwidth versus the bandwidth required for each branch office.
For example, New York's total WAN capacity is 100 mbps, with 20 mbps reserved for RTC, and the latter is the value reflected in the next image:
Without digging into the actual numbers for now, we can get an immediate overview through the bar diagram and make the following statements:
Now, browse to the Deployment readiness tab and review the pie diagrams; these contain a summary of the number of sites that require a WAN upgrade or perhaps usage adjustments before they can be considered Lync-ready.
What useful information can we retrieve from the preceding images? Remember when we configured the Flag in red when WAN BW usage exceeds this value to 70 percent? This is where the parameter is reflected. It works as a "warning level" that tells us how many sites go beyond 70 percent WAN usage for the total link capacity. Be careful about this point. The takeaway from this output is that if we could reserve a greater amount of WAN bandwidth for RTC, possibly up to 70 percent, this would result in only one site, exceeding this threshold.
In a real-world scenario, you will want to set this threshold to a level that you know will not affect your existing line-of-business applications that already make use of your WAN. Acquiring real-time network usage statistics from your WAN carrier or through specialized network monitoring software is paramount to determine an acceptable threshold.
The following pie diagram takes into account the overall network readiness based on the bandwidth we originally allocated in the calculator (20 percent):
As shown in the previous diagram, we are provided with two outputs, one with a video and one without. The takeaway from this is as follows:
If we need to further break down to actual values, another useful resource is the sites tab. Scroll down and then sideward until the following is displayed on your screen:
This table reveals the following:
You might have noticed that the tool allows for great flexibility in setting up and customizing several parameters for each site.
It is important to notice that values might have to be adjusted in specific circumstances, and ultimately, you are leveraging statistical usage models (personas) that cannot guarantee a perfect match with the real world. An exact calculation is only revealed through usage; furthermore, network usage can continuously vary depending on the user's evolution, trends (video adoption is a slowly but constantly growing one), and evolving business objectives.
In these aspects, the tool provides an excellent overview, and ultimately, it is an essential resource to highlight likely network bottlenecks that need to be addressed before deployment as an essential milestone in every successful Lync deployment project.
18.225.255.187