Comparing Consolidated Topology to Expanded Topology

Access Edge Servers can be set up in a consolidated topology or an expanded topology. The real difference between the two is that the services of Access Edge Servers, Web components, and audio/visual (A/V) components all exist on one server that shares all these roles. In an expanded topology, there are three potential configurations:

  • Single-Site Edge Server

    • Access Edge Server and Web Conferencing Server roles are on one server.

    • The Audio/Video Conferencing Server role is on another, separate server.

  • Scaled Single-Site Edge Server

    • Two or more collocated and load-balanced Access Edge Servers and Web Conferencing Servers are placed.

    • Two or more load-balanced Audio/Video Conferencing Servers are placed.

  • Multiple-Site Edge Server

    • Two or more Access Edge Servers and Web Conferencing Servers are load balanced and collocated at the primary data center.

    • Two or more Audio/Video Conferencing Server load-balanced servers are collocated at the primary data center.

And, at remote larger locations or secondary data centers, here are the possible configurations:

  • Single server with the Web Conferencing Server role, or two or more load-balanced Web Conferencing Servers

  • Single server with the Audio/Video Conferencing Server role, or two or more load-balanced Audio/Video Conferencing Servers

What this means in federation is that you have only one set of servers to deal with—one load-balanced array rather than a set of servers for each role.

However, make sure you understand that you can locate Conferencing Web servers and Audio/Video Conferencing servers wherever you want—in the same data center locally or dispersed to different locations to be located with other pools closer to users. But you can have only one farm of Access Edge Servers, at your primary site.

To enable federation in an enterprise, do the following:

  1. Go to Global Policy properties.

  2. Access the Federation tab.

  3. Select the Enable Federation And Public IM Connectivity check box.

  4. Specify the FQDN of the next-hop server (Director, load balancer, or Access Edge Server).

Comparing Consolidated Topology to Expanded Topology

Note

The settings just mentioned can be overridden in specific areas of your enterprise. Say, for example, your portion of the enterprise needs to go directly to the Access Edge Server instead of the Director defined in the Global properties. You can redefine this on the Federation tab by entering the correct FQDN.

Why define a global property? As with many settings, the exception is much easier to deal with than defining the multitude of options separately. This configuration affects all default routes for all pools. If we need an exception, it can be defined locally.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset