Neighboring The Local Vcs To Another Vcs Cluster - Cisco TelePresence Administrator's Manual

Clustering and peers

Neighboring the local VCS to another VCS cluster

You can neighbor your local VCS (or VCS cluster) to a remote VCS cluster; this remote cluster could be a
neighbor, traversal client, or traversal server to your local VCS. In this case, when a call is received on your
local VCS and is passed via the relevant zone to the remote cluster, it will be routed to whichever peer in that
neighboring cluster has the lowest resource usage. That peer will then forward the call as appropriate to one
of its:
locally registered endpoints (if the endpoint is registered to that peer)
n
peers (if the endpoint is registered to another peer in that cluster)
n
external zones (if the endpoint has been located elsewhere)
n
When configuring a connection to a remote cluster, you create a single zone and configure it with details of all
the peers in the cluster. Adding this information to the zone ensures that the call is passed to that cluster
regardless of the status of the individual peers.
You also need to enter the IP address of all peers in the remote cluster when the connection is via a
neighbor or traversal client zone. You do not do this for traversal server zones, as these connections are
not configured by specifying the remote system's IP address.
Note: systems that are configured as peers must not also be configured as neighbors to each other, and vice
versa.
Neighboring your clusters
To neighbor your local VCS (or VCS cluster) to a remote VCS cluster, you create a single zone to represent
the cluster and configure it with the details of all the peers in that cluster:
1. On your local VCS (or, if the local VCS is a cluster, on the master peer),
type. This zone will represent the connection to the cluster.
2. In the Location section, enter the IP address or FQDN of each peer in the remote cluster in the Peer 1 to
Peer 6 address fields.
Note that:
Ideally you should use IP addresses in these fields. If you use FQDNs instead, each FQDN must be
n
different and must resolve to a single IP address for each peer.
The order in which the peers in the remote VCS cluster are listed here does not matter.
n
Whenever you add an extra VCS to a cluster (to increase capacity or improve redundancy, for example)
n
you will need to modify any VCSs which neighbor to that cluster to let them know about the new cluster
peer.
Cisco VCS Administrator Guide (X8.1.1)
Managing clusters and peers
create a zone of the appropriate
Page 169 of 507