Adding And Removing Peers From A Cluster; Changing The Master Peer; Monitoring The Status Of The Cluster - Cisco TelePresence Administrator's Manual

some peer-specific configuration items
n
user account details (when running in TMS Agent legacy mode)
n
You may need to wait up to one minute before changes are updated across all peers in the cluster.

Adding and removing peers from a cluster

After a cluster has been set up you can add new peers to the cluster or remove peers from it. Instructions for
this are contained in Cluster creation and maintenance deployment
Note: systems that are configured as peers must not also be configured as neighbors to each other, and vice
versa.
If peers are deployed on different LANs, there must be sufficient connectivity between the networks to
ensure a low degree of latency between the peers - a maximum delay of 15ms one way, 30ms round-trip.
Peers in a VCS cluster can be in separate subnets. Peers communicate with each other using H.323
messaging, which can be transmitted across subnet boundaries.
Deploying all peers in a cluster on the same LAN means they can be configured with the same routing
information such as local domain names and local domain subnet masks.

Changing the master peer

You should only need to change the Configuration master when:
the original master peer fails
n
you want to take the master VCS unit out of service
n
Note that if the master fails, the remaining peers will continue to function normally, except they are no longer
able to copy their configuration from the master so they may become out of sync with each other.
To change the master peer you must log in to every other VCS in the cluster and change the configuration
master on each peer:
1. Log in to the VCS and go to the
2. Change the Configuration master to the peer you want to set as the new master (the numbers match
against the Peer IP address fields underneath).
3. Click Save.
4. Repeat this for every peer in the cluster, ensuring that you select the same new master on each peer.
Note that during this process you may see alarms raised on some peers about inconsistent master peer
configuration. These alarms will be lowered when every peer in the cluster is configured with the new master.

Monitoring the status of the cluster

The status sections at the bottom of the
time of the previous and next synchronization.
If the VCS is running in TMS Agent legacy mode, you can go to the
This shows the current status of the TMS Agent database and can be used to assist in troubleshooting
replication problems.
Cisco VCS Administrator Guide (X7.1)
Clustering page (VCS configuration
Clustering page show you the current status of the cluster, and the
Clustering and peers
guide.
> Clustering).
TMS Agent replication status page.
Page 140 of 479