Technical data

DATA CENTER and CAMPUS NETWORKS DEPLOYMENT GUIDE
Deploying Brocade Networks with Microsoft Lync Server 2010 33 of 52
provides DoS security to the servers by ensuring that traffic from a hacker will be placed into the “bit bucket” and not
forwarded to the real servers. Note that the Brocade ServerIron ADX is not a single point of failure, as it can be
configured with another Brocade ServerIron ADX to provide different types of redundancy, as discussed earlier in this
document.
Latency
Latency is a critical element that needs to be taken into account when designing a network. Fabrikam wants to be
sure that latency will not degrade the performance of Microsoft Lync Server 2010. Between each site the latency
was measured as follows:
• Between San Jose and New York: 50 ms
• Between San Jose and Austin: 25 ms
• Between San Jose and Seattle: 5 ms
Fabrikam has implemented certain features in the Brocade switches to help deal with latency and jitter by providing
QoS, rate limiting, and enough bandwidth in the switches themselves—however, none of these features can
overcome the challenges of distance. Fabrikam has set up an SLA with the ISP such that latency will not exceed
100 ms.
Figure 9. Logical hardware load balancing Microsoft Lync Server 2010 servers.