In the last two posts (part 14 and part 15) we have been setting up Kemp load balancers for our internal Lync servers. We will now continue with this setup, and load balance the frontend servers.
As I started with in Part 14 you can load balance the frontend servers in two ways.
DNS Load Balancing and Hardware Load Balancing the Web Services
Hardware Load Balancing all Lync Services
This post is the first part where we uses both DNS load Balancing for the native Lync services (like sip) and the hardware load balancer for the web services in Lync.
First we need to change to topology so that the internal web services uses another name that the pool name – in this case cswebint.exchangepro.local
Publish the topology, and run step 2 and 3 in the lync deployment wizard to request a new frontend certificate and install that one on all three frontend servers.
Export the certificate and import it on the hardware load balancer (see part 14 for how to)
Navigate to Virtual Service and add the virtual IP and type port 80. Click Add this Virtual Service
Remove Transparency and Force L7
Make the below selection
On real server, set the check port to 80 and click Set Check Port – the Click Add New
Add the three frontend servers ip addresses
Click back twice and see that the service is green
Click Add New Again
Type the VIP address again and type 443 in port and give the service a name
Remove the transparency and set the certificate and the below parameters.
Navigate to real server and set the below and click Add New.
Add the three frontend servers
Click Back twice and see that the service is Green.
We have now made the Hardware load balancer ready, the last thing that we need is to change the DNS so that FEPOOL01.exchange points to the three frontend servers, and cswebint.exchangepro.local points to the VIP on the Hardware load balancer.
The other Web service records must also be created and should also point to the Virtual IP. Create them in the exchangepro.dk DNS zone.
In the next post we will be looking at the other alternative where we uses the load balancer for all Lync traffic.