Site Topology Setup

The Site Topology feature of RealPresence Resource Manager provides a global view of the video conferencing network, showing how it is organized within groupings called Territories and direct Site Links indicating cumulative bandwidth capacity and utilization for all subnets within a Site.

Site topology information describes your network and its interfaces to other networks, including the following elements:

  • Site: A local area network (LAN) that generally corresponds with a geographic location such as an office or plant. A site contains one or more network subnets, so a device’s IP address identifies the site to which it belongs.
  • Network clouds: A Multiprotocol Label Switching (MPLS) network cloud defined in the site topology. An MPLS network is a private network that links multiple locations and uses label switching to tag packets with origin, destination, and Quality of Service (QoS) information.

    Note:

    MPLS clouds are not associated with an IP address range, so they can be used to group multiple subnets. They could also represent a service provider.

    While links to MPLS clouds have bandwidth and bit rate limitations, the cloud is infinite. In this way, clouds reflect the way in which businesses control bandwidth and bit rate.

  • Internet/VPN: An entity that represents your network’s connection to the public Internet.
  • Site link: A network connection between two sites or between a site and an MPLS network cloud.
  • Site-to-site exclusion: A site-to-site connection that the site topology doesn’t permit an audio or video call to use.
  • Territory: A grouping of one or more sites for which a RealPresence Resource Manager system is responsible.

The site topology you create within the RealPresence Resource Manager system should reflect your network design. Consider the following information and best practices when creating your site topology:

  • If possible, connect all sites to an MPLS cloud. MPLS clouds are like corporate networks, used to connect multiple subnets in multiple sites, but all servicing a company.
  • Avoid cross loops or multiple paths to a site; otherwise a call may have different paths to a single destination. The more cross, circular, and multi paths you have, the higher the number of calculations for a conference.
  • Link sites that aren’t connected to an MPLS cloud directly to another site that is connected to an MPLS cloud. Do not create orphan sites.
  • Calls are routed through a bridge, so bandwidth and bit rate limits for the site and subnet apply to all calls made using that bridge.
  • Reserve the Internet/VPN “site” for IP addresses that fall outside your private or corporate network (for example remote workers), because all calls routed to the Internet/VPN site will be routed through the site on your private or corporate network that has Internet access.