User manual BARRACUDA LOAD BALANCER WITH MICROSOFT LYNC SERVER 2010 TECHNICAL NOTES V1.0

[. . . ] Do not run the Lync Topology Builder until instructed to by this deployment guide. All of the Services on the Barracuda Load Balancer must be configured before running the Topology Builder. Additional References Barracuda Load Balancer Administrator's Guide: o http://www. barracudanetworks. com/documentation/#Load_Balancer Ports for Microsoft Lync Server o http://technet. microsoft. com/en-us/library/gg398833. aspx Microsoft Lync Documentation o http://technet. microsoft. com/en-us/library/gg398616. aspx Deploying the Barracuda Load Balancer with Microsoft Lync Server 2010 Terminology The following table lists some of the terms used in this document. Table 1: Terminology Front-End Server Edge Server Fully Qualified Domain Name (FQDN) Service Definitions A Lync Server in the internal network running the Front End Lync Services. A Lync Server deployed in the perimeter network running the Edge Lync Services. [. . . ] Configure Enterprise Pool Services Do this on the internal-facing Barracuda Load Balancers. To configure all the Services needed for an internal Lync deployment, perform the following steps on the internal-facing Barracuda Load Balancer: 2. 1. Add each Service listed in Table 3: Required Services for internal Lync deployment - they are all required. To add a Service: In the Service Name box, enter the name for the Service. In the Virtual IP Address box, enter the IP address for the FQDN of your Internal Lync Pool. Select the protocol and in the Port box, enter the port for the Service in the table. In the Real Servers box, enter the IP address for every Front-End server in your Lync Pool. Table 3: Required Services for internal Lync deployment Service Name MTLS Front Virtual IP Address IP for FQDN of Internal Enterprise Lync Pool e. g. 192. 168. 1. 11/24 for frontpool. domain. local Protocol TCP Port 5061 Real Servers IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) DCOM WMI Front Internal Conf Front IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool TCP TCP 135 444 HTTPS Front TCP 443 Copyright ©2011 Barracuda Networks Inc. V3. 5110201010201 Page 5 of 11 Deploying the Barracuda Load Balancer with Microsoft Lync Server 2010 2. 3. The Services in Table 4: Optional Services for internal Lync deployment are optional. Table 4: Optional Services for internal Lync deployment Service Name Application Sharing (optional) QoE Agent (optional) Response Group Service (optional) Conferencing Attendant (optional) Conferencing Announcement (optional) Outside Voice Control (optional) Virtual IP Address IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool IP for FQDN of Internal Enterprise Lync Pool Protocol TCP Port 5065 Real Servers IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) IP Addresses of your Front-End servers (K and L from the example) TCP 5069 TCP 5071 TCP 5072 TCP 5073 TCP 5074 2. 4. For each Service created, edit the Service by clicking the Edit graphic next to the Service entry in the table. On the Service Detail page that appears: In the General section, set the Service Type to TCP Proxy. In the Advanced Options section, set Session Timeout to 0 (session never times out). For the DCOM WMI Front Service only, edit each Real Server associated with the Service by clicking the Edit graphic next to each Real Server entry in the table. On the Real Server Detail page that appears: In the Server Monitor section, set the Testing Method to TCP Port Check. It is better to test port 5061 for this Service because port 135 always passes the TCP port check, even if Lync Services are not responding. 3. Configure Internal A/V Services (if applicable) If you have more than 10, 000 users in this pool, it is recommended that you separate out the A/V Services of your Internal Lync Pool and do not colocate the A/V services on the Front End pool. If you choose to colocate A/V Services on your Front End Pool, no further changes to configuration are required. Separating out the A/V Services into its own pool will require two more Barracuda Load Balancers operating as a High Availability pair. Contact Barracuda Technical Support if your deployment has more than 10, 000 A/V users for assistance. Copyright ©2011 Barracuda Networks Inc. V3. 5110201010201 Page 6 of 11 Deploying the Barracuda Load Balancer with Microsoft Lync Server 2010 Do this on the internal-facing Barracuda Load Balancers. To configure all the Services needed for a load-balanced Lync Edge deployment, perform the following steps on the internal-facing Barracuda Load Balancer: 4. 1. [. . . ] Perform these steps on all of the Barracuda Load Balancers that serve HTTPS traffic. Using the Certificates Microsoft Management Console (MMC), export the certificates along with their private keys from the Lync Servers. Import the certificates into the corresponding Barracuda Load Balancer using the Basic > Certificates page. For each HTTPS Service, go the Basic > Services page and edit the Service. [. . . ]