Topic Last Modified: 2011-01-31

In the Edge Server pool topology, two or more Edge Servers are deployed as a load-balanced pool in the perimeter network of the data center. Hardware load balancing is used for traffic to both the external and internal Edge interfaces.

If your organization requires support for more than 5,000 Access Edge service client connections, 1,000 active Web Conferencing service client connections, or 500 concurrent A/V Edge sessions, and high availability of the Edge Server is important, this topology offers the advantages of scalability and failover support.

For simplicity, the Scaled Consolidated Edge Topology (Hardware Load Balanced) figure does not show any Directors deployed but in a real world production deployment they are recommended. For details about the topology for Directors, see Components and Topologies for Director. The reverse proxy is also not load balanced but if it was, it would require a hardware load balancer. DNS load balancing is not an option for load balancing reverse proxy traffic.

Note:
For clarity, the .com DNS zone represents the external interface for both reverse proxy and consolidated Edge Servers, and the .net DNS zone refers to the internal interfaces. Depending on how your DNS is configured, both interfaces could be in the same zone (for example, in a split-brain DNS configuration).

Hardware Load Balancer Requirements for A/V Edge

Following are the hardware load balancer requirements for A/V Edge:

Hardware Load Balancer Requirements for Web Services

Following are the hardware load balancer requirements for Web Services:

Hardware Load Balancer Requirements for Reverse Proxy

Following are the hardware load balancer requirements for reverse proxy:


Scaled Consolidated Edge HLB Topology

In This Section



    Scaled consolidated edge topology (hardware load balanced)