Module 4
Designing Lync Server 2010 Jump Start
Day 1:
Topology Design Day 2: Infrastructure & Network Design Day 3: Services & Maintenance Design
Mod 1: Lync Server 2010
Design Process Overview Module 5: Designing a Mediation Server Topology
Module 9: Designing Location Services in Lync Server 2010
Module 2a: Designing a LS 2010 Topology—ONE
Module 6a: Designing Voice Infrastructure
—ONE
Module 10: Designing Response Group Services Module 2b: Designing a LS
2010 Topology—TWO
Module 6b: Designing Voice Infrastructure
—TWO
Module 11: Designing Resiliency
Module 3a: Designing for Conferencing and Ext. Scenarios—ONE
Module 7: Designing Exchange Server UM Integration
Module 12: Designing for Backup and Disaster
Recovery Module 3b: Designing for
Conferencing and Ext. Scenarios—TWO
Module 8a: Creating a Network Design—ONE
Module 13: Designing Monitoring and Archiving Server
Module 4: Planning and Designing Load Balancing Connectivity
Module 8b: Creating a Network Design—TWO
Module Agenda
• Load Balancing Requirements
• Planning for Load Balancing
• DNS-based Load Balancing
• Hardware Load Balancing
Discussion: Assess Load Balancing Requirements
• Do you think that the deployment of load balancing is
a mandatory requirement for environments with a large numbers of users?
• How does Lync Server 2010 provide for easier
configuration of hardware load balancers?
• Describe a scenario where DNS load balancing might
Lync Server 2010
DNS Load Balancing Hardware Load Balancing
Plan for keeping all Front End Servers in the Lync Server 2010 pool operational
Plan for using hardware devices that have firmware updates to support DNS load balancing
Plan for migrating previous versions of servers and clients to Lync Server 2010
Lync Server 2010
Plan for identifying the components that do not support load balancing and work on mitigation strategies
Assess load balancing requirements from a scalability perspective—servers and services
Discuss the overall load balancing plan with project stakeholders
Determine the load balancing requirements for each server role
Determine the load balancing requirements for each service
Hardware Load Balancing
Office Communication Server Clients
DNS Load Balancing
Lync Server 2010 Clients
Lync Server 2010
Discussion: Pros/Cons of Load Balancing
• When compared with a hardware load balancer, does
DNS load balancing provide an intelligent method of load balancing client connections to a Front End Server pool?
• Considering that DNS load balancing is so easy to
Lesson 2: Designing Load Balancing
• Discussion: Choosing the Appropriate Load Balancing
Solution
• Designing DNS-Based Load Balancing
• Designing Hardware-Based Load Balancing
• Designing for Servers and Services for Load Balancing
• Guidelines for Deploying DNS Load Balancing for Front
End Server Pool
• Designing a Coexistence Strategy
Discussion: Choosing Load Balancing Solution
• To save costs, a customer might want to use Windows
Network Load balancing for load balancing
HTTP/HTTPS traffic. Would you recommend this approach?
• Can DNS-based load balancing be considered a
Designing DNS-Based Load Balancing
Lync 2010 Client
Hardware Load Balancer (for web traffic)
VIP: 10.10.0.99
Lync Server 2010 Enterprise Pool Pool Name: pool.adatum.com
Front End Server: van-fe01.adatum.com (10.10.0.20) Front End Server: van-fe02.adntum.com (10.10.0.30)
1: DNS load balancing-aware client resolves SRV record and queries for IP address for pool.adatum.com 2: DNS returns all A records for
pool.adatum.com: 10.10.0.20 and 10.10.0.30
3: Client initiates connection to random Front End Server
3
Designing DNS-Based Load Balancing
Lync 2010 Client
Hardware Load Balancer (for web traffic)
VIP: 10.10.0.99
Lync Server 2010 Enterprise Pool Pool Name: pool.adatum.com
Front End Server: van-fe01.adatum.com (10.10.0.20) Front End Server: van-fe02.adntum.com (10.10.0.30)
1: Client resolves SRV record and queries for IP address of
pool.adatum.com
2: DNS returns VIP of hardware load balancer:10.10.0.99
3: Client initiates connection to hardware load balancer
3
LYNC SERVER 2010 Server Roles that
support load balancing
Enterprise Edition Front End Server
Mediation Server Director Server
Edge Server
Designing Servers & Services for Load Balancing
• Scaling requirements
• Organizational requirements
• Number of users in a given site
Deploying DNS Load Balancing Guidelines
Scenario: Should I deployDNS Load balancing on a Front End Server pool?
Is DNS load balancing supported? Is DNS load balancing recommended? Is hardware load balancer (only) recommended?
All or most users homed in the
pool run Lync Server 2010 clients. Yes Yes
Many users homed in the pool still
run older clients. Yes Yes
Interoperates only with other Lync
Server 2010 servers. Yes Yes
Interoperates with many servers running earlier versions of Office Communications Server.
Yes Yes
Running Exchange UM with
Exchange 2010 SP1 (or not running Exchange UM)
Yes Yes
Running Exchange UM with earlier
Hardware
Load Balancing DNS Load Balancing
Lync Server 2010 Clients Lync Server 2010
Office Communication Server Clients
Designing a Coexistence Strategy
• Provide hardware load balancing for all clients/servers
• Retain existing hardware load balancing setup for legacy clients and legacy servers
In this scenario, which are the servers that would require load balancing?
For load balancing SIP traffic, which form of load balancing would you deploy?
Perimeter Network
Edge Array
WAN
Lync Clients
Federated Organizations with Lync Server 2010 Edge
Servers
Federated Organizations with Office Communications Server R2 Edge Servers
Active Directory
Active Directory DNS
Front End pool
Lync Clients Monitoring Server Internal Network Edge Array WAN Lync Clients
Federated Organizations with Lync Server 2010 Edge
Servers
Federated Organizations with Office Communications Server R2 Edge Servers Perimeter Network Active Directory Active Directory DNS
Front End pool
Lync Clients Monitoring Server
Internal Network
Hard load balancer on external Edge
DNS load balancer on external Edge
DNS load balancer on enterprise pool to manage SIP traffic
Module Review and Takeaways
• Module Review Questions and Answers
©2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Azure, System Center, Hyper-V 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.
