Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Clustering and peers
Cisco VCS Administrator Guide (X7.2)
Page 154 of 498
If the VCS is running in TMS Agent legacy mode, you can go to the
page.
This shows the current status of the TMS Agent database and can be used to assist in troubleshooting
replication problems.
replication problems.
Peer-specific configuration
Most items of configuration are applied to all peers in a cluster. However, the following items (marked with a
†
on the web interface) must be specified separately on each cluster peer.
System name
The system name must be different for each peer in the cluster.
Option keys
are specific to each peer. 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.
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 specific to each peer. Each peer may have slightly different requirements for the
connection to their Ethernet switch.
IP configuration
configuration is specific to each peer. Each peer must have a different IPv4 address and a different IPv6
address.
n
IP gateway configuration is peer-specific. Each peer can use a different gateway.
n
IP routes (also known as static routes) are peer-specific. If these are used, they can be different for each
peer.
peer.
Note that the IP protocol is applied to all peers, because each peer must support the same protocols.
DNS configuration
are peer-specific - each peer can use a different set of DNS servers. However, the DNS
domain name is applied across all peers.
Logging
The Event Log and Configuration Log on each peer only report activity for that particular VCS. You are
recommended to set up a remote syslog server to which the logs of all peers can be sent. This allows you to
have a global view of activity across all peers in the cluster. See the
recommended to set up a remote syslog server to which the logs of all peers can be sent. This allows you to
have a global view of activity across all peers in the cluster. See the
section for further details.
Conference Factory template
The template used by the
application to route calls to the MCU is peer-specific, as it
must be unique for each peer in the cluster.
CA certificates
The security certificates and certificate revocation lists (CRLs) used by the VCS must be uploaded
individually per peer.
individually per peer.