Monitoring The Status Of The Cluster; Configuration That Is Not Replicated Across A Cluster - Cisco TelePresence Video Communication Server Administrator's Manual

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 Clustering page
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 warning messages raised on some peers about
inconsistent master peer configuration. These warnings 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 Clustering page show you the current status of the cluster,
and the time of the previous and next synchronization. From here you can also go to the TMS Agent
replication status page. This shows the current status of the
assist in troubleshooting replication problems.

Configuration that is not replicated across a cluster

Most items of configuration are replicated from the master to all peers, with the exceptions listed
below.
System name
The system name is not replicated. It must be different for each peer in the cluster.
Administrator accounts
The password for the default admin administrator account is not replicated. Each peer can have a
different password. Any other administrator accounts and passwords will be replicated from the
master peer to all other peers.
Option keys
Option keys are not replicated. Each peer must have an identical set of option keys installed, but you
must purchase these separately for each peer in the cluster.
Ethernet speed
The Ethernet speed is not replicated. Each peer may have slightly different requirements for the
connection to their Ethernet switch.
IP configuration
LAN configuration is not replicated across peers. Each peer must have a different IPv4 address and a
different IPv6 address.
IP gateway configuration is not replicated. Each peer can use a different gateway.
n
IP routes (also known as static routes) are not replicated. If these are used, they can be different for
n
each peer.
Note that the IP protocol is replicated, because each peer must support the same protocols.
DNS configuration
Cisco VCS Administrator Guide (X6.1)
(VCS configuration > Clustering).
TMS Agent service and can be used to
Clustering and peers
Page 103 of 401