We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer

Microsoft Office Communications Server Deployment Example

  • Last updated on

 This article applies to:

  • Barracuda Load Balancer running firmware version 3.3.1.005 or higher
  • Barracuda Load Balancer 340 or above
  • Microsoft® Office Communications Server 2007 R2 Enterprise Edition

This article assumes you are connected to the Barracuda Load Balancer web interface and have an activated subscription.

Figure 1 illustrates a complete Office Communications Server deployment with Barracuda Load Balancers. This example is used in the deployment tasks in the article How to Deploy with Microsoft Office Communications Server.

In this example, the Edge deployment uses a Route-Path topology while the Front-End deployment uses a one-armed topology. 

Figure 1. Office Communications Server Deployment Example.

OCS_Infrastructure_v3.jpg

As shown in Figure 1, the firewall should not NAT inbound traffic addressed to the Edge deployment.

Next Step

Proceed to  How to Deploy with Microsoft Office Communications Server.

Last updated on