Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Lowest resource usage is determined by comparing the number of available traversal calls (maximum - current use)
on the peers, and choosing the peer with the highest number. Peers that are in maintenance mode are not
considered.
on the peers, and choosing the peer with the highest number. Peers that are in maintenance mode are not
considered.
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.
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.
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:
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 primary peer), create a zone of the appropriate type.
This zone will represent the connection to the cluster.
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.
6 address fields.
Note that:
■
Ideally you should use FQDNs in these fields. Each FQDN must be different and must resolve to a single IP
address for each peer. With IP addresses, you may not be able to use TLS verification, because many CAs will
not supply certificates to authenticate an IP address.
address for each peer. With IP addresses, you may not be able to use TLS verification, because many CAs will
not supply certificates to authenticate an IP address.
■
The order in which the peers in the remote VCS cluster are listed here does not matter.
■
Whenever you add an extra VCS to a cluster (to increase capacity or improve redundancy, for example) you
will need to modify any VCSs which neighbor to that cluster to let them know about the new cluster peer.
will need to modify any VCSs which neighbor to that cluster to let them know about the new cluster peer.
Troubleshooting Cluster Replication Problems
Cluster replication can fail for a variety of reasons. This section describes the most common problems and how to
resolve them. For more detailed information:
resolve them. For more detailed information:
.
Some peers have a different primary peer defined
1.
For each peer in the cluster, go to the System > Clustering page.
2.
Ensure each peer identifies the same Configuration primary.
Unable to reach the cluster configuration primary peer
The VCS operating as the primary peer could be unreachable for many reasons, including:
■
Network access problems
■
VCS unit is powered down
■
Incorrectly configured addresses
■
TLS verification mode is set to Enforce but some peers have invalid or revoked certificates
■
Different software versions on peers
■
DNS settings not correct in cluster
189
Cisco TelePresence Video Communication Server Administrator Guide
Clustering and Peers