In this part, we will continue to Load Balance our Lync Server 2013 High Availability solution, and will look at the first part of load balancing the Access Edge Servers.
When you are deciding to use load balancing for the Access Edge Servers, you should consider these things:
Is external Edge communication critical for my organization?
If you can answer no, you might only need one Edge server, which makes everything much easier, because you can use NAT, and do not need a special network for the edge servers.
If you answer yes, then ask this question:
Is communication with Public IM and/or OCS 2007 partners critical?
If you answer no, you can save the money for the hardware load balancers and just use DNS load balancing for the edge servers.
If you answer yes, you need to buy Hardware Load Balancers, and if they also should highly available, you need to buy four.
Two for the external network and two for the internal network on the access edge servers.
If you are using HLB at one network, you also need to do it on the other network.
The topology will look like this:
In this part we will look at load balancing the DMZ Internal network, and for that we will be using the Kemp Load Balancers that we also uses as reverse proxy and deployed in part 12.
You can have a look at part 17 to see how the generic services is configured on the hardware load balancers.
The below services should be add to the DMZ Internal Load Balancers
The records for the internal DNS will look like this:
That’s it for this post – in the next part we will be looking at how to load balance the external nic with hardware load balancers, they will different from what we have done until now with the load balancers.