3.1 Configure a Load Balancer for Your Pool
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
A load balancer is required in an Enterprise pool that has more than one Enterprise Edition Server. The load balancer performs the critical role of delivering scalability and high availability across multiple servers that are connected to a centralized database on the Office Communications Server, Back-End Database.
Only one load balancer is required, but you can optionally create two logical load balancers—one for the Front End Servers and one for the Web Components Server—if you deploy Enterprise Edition in an expanded configuration. If you want to employ two logical load balancers, you can configure two virtual IP (VIP) addresses on one physical load balancer, or you can configure two separate physical load balancers.
Note
If you are deploying a pool that has a single Enterprise Edition server connected to the Back-End Database, skip to 3.2 Configure DNS for Your Pool.
Table 2 lists the ports that you must configure on the load balancer.
Table 2. Required Ports on the Load Balancer Virtual IP Addresses
Port Required | Virtual IP | Port Use |
---|---|---|
5060 |
Load balancer VIP used by the Front End Servers |
Client to server SIP communication over TCP |
5061 |
Load balancer VIP used by the Front End Servers |
Client to Front End Server SIP communication over TLS SIP Communication between Front End Servers over MTLS |
135 |
Load balancer VIP used by the Front End Servers |
To move users and perform other "pool" level WMI operations over DCOM |
444 |
Load balancer VIP used by the Front End Servers |
Communication between the internal components that manage conferencing and the conferencing servers |
443 |
Load balancer VIP used by the Web Components Server |
HTTPS traffic to the pool URLs |
When you configure the load balancer, you will need to ask the relevant network and DNS administrator for at least one virtual IP (VIP) address and FQDN for the load balancer (one for each logical load balancer), as well as a static IP address for every server that you plan to deploy in the Enterprise pool.