Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Clustering and peers
Cisco VCS Administrator Guide (X7.0)
Page 142 of 488
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.
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
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
service and can be used to
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.
different password. Any other administrator accounts and passwords will be replicated from the master
peer to all other peers.
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. However, this does not apply to traversal
call licenses, non-traversal call licenses and TURN relay licenses; these licenses can be installed on
any cluster peer and are available for use by any peer in the cluster.
call licenses, non-traversal call licenses and TURN relay licenses; these licenses can be installed on
any cluster peer and are available for use by any peer in the cluster.
Ethernet speed
The
is not replicated. Each peer may have slightly different requirements for the
connection to their Ethernet switch.
IP configuration
configuration is not replicated across peers. Each peer must have a different IPv4 address and a
different IPv6 address.
n
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
each peer.
each peer.
Note that the IP protocol is replicated, because each peer must support the same protocols.
DNS configuration
are not replicated across peers - each peer can use a different set of DNS servers.
However, the DNS domain name is replicated across peers.
Logging