It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer ADC

Understanding Microsoft Lync Server Deployment Options

  • Last updated on

This article refers to the Barracuda Load Balancer ADC and Microsoft® Lync® Server 2010 or 2013 Enterprise Edition.

For a list of prerequisites, see Microsoft Lync 2010 and 2013 Server Deployment.

In your environment, the inbound firewall must not NAT inbound traffic addressed to the Edge deployment.

Lync Server Front-End Server Deployment Options

Because the servers in a Lync Server enterprise pool communicate with each other using the VIP address of the pool, create a TCP Proxy service and associate the servers with it to facilitate this communication. The servers and the Barracuda Load Balancer ADC must be deployed using a one-armed topology in either a single or multiple subnet configuration.

Deploying internal Lync pools using a two-armed Route-Path topology, Direct Server Return (DSR) Mode does not work and is not supported.

Lync Edge Server Deployment Options

Load-balanced Edge deployments are supported using either a one-armed Route-Path topology using a TCP Proxy service or a two-armed Route-Path topology using a Layer 4 service. For maximum performance, a two-armed Route-Path topology is recommended.

Direct Server Return deployment does not work and is not supported.

Deployment Example

The following diagram shows an example Edge deployment. You can use this example as a reference in your next step of deploying the Barracuda Load Balancer ADC in your Lync Server environment.

Lync Deployment Example


Next Step

Deploy the Barracuda Load Balancer ADC in your Lync Server environment. For instructions, see How to Deploy with Microsoft Lync Server 2010 and 2013.

Last updated on