In this post we will be looking on how to load balance the Lync Sever 2013 Director Servers.
We have in the last couple of posts been dealing with hardware load balancing of the internal servers:
In Part 14 we have setup the Kemp Load Balancers that is uses internally.
In Part 15 we have setup Load Balancing of the Office Web Apps Servers.
In Part 16 we have setup a combination of DNS Load Balancing for the Lync Services and Hardware Load Balancing for the Web Services.
In Part 17 we have setup Load Balancing of all the frontend services.
Load balancing of the Director servers look very much load balancing of the frontend servers.
As with the frontend servers, you will have the choice to load balance all director service or use a combination of dns load load balancing and hardware load balancing.
DNS Load Balancing and Hardware Load Balancing
Let us start by looking at load balancing only the web services of the director servers, which means that we will use a combination of DNS LB and HLB.
In topology builder you should navigate to the Director Pool and configure the override of the internal FQDN for the webservices.
On one of the director servers, export the certificate which is used on the server.
You should also create two Virtual Services for http and https – the same way as we did in part 16 – use the newly imported certificate for the https service.
Create also a virtual service for port 444 as we did in part 17.
The virtual IP for the web services has been defined as 10.160.64.30.
The virtual services that needs to be configured is these:
The internal DNS will look like this:
That is all for load balance the internal Director web services.
Load Balance All Director Services
If you want to load balance all the director services you should not override the internal FQDN web service, but let it keep the default setting:
Create the virtual web services like we did under previous section and also make one for port 5061 (see part 17)
The Internal DNS must look like this:
That it for load balance the Director servers.
In the next post we will look at load balance the Access Edge Servers.
Lync 2013 High Availability