Tms Agent Replication Status - Cisco TelePresence Administrator's Manual

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.
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:
1. On your local VCS (or, if the local VCS is a cluster, on the master peer),
type. 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.
Note that:
Ideally you should use IP addresses in these fields. If you use FQDNs instead, each FQDN must be
n
different and must resolve to a single IP address for each peer.
The order in which the peers in the remote VCS cluster are listed here does not matter.
n
Whenever you add an extra VCS to a cluster (to increase capacity or improve redundancy, for example)
n
you will need to modify any VCSs which neighbor to that cluster to let them know about the new cluster
peer.

TMS Agent replication status

The TMS Agent replication status
Agent replication status) shows the current status of the TMS Agent database.
The status report is used to assist in troubleshooting replication problems. It lists each TMS and VCS server
peer whose data (FindMe and Device Provisioning, and not VCS configuration) is being replicated between
themselves by the TMS Agent database.
For each server peer the report indicates:
the number of changes still to replicated to that server (and that have been applied to at least one of the
n
other servers)
the date of the oldest change still to be applied to that server
n
the port number being used for replication communication between the servers and whether that
n
communication is encrypted or not
Note that the TMS Agent replication status is only relevant if the VCS has the FindMe or Device Provisioning
option keys enabled and is using the legacy TMS Agent database.
Cisco VCS Administrator Guide (X7.1)
page (VCS configuration > Clustering
Clustering and peers
create a zone of the appropriate
and then click View TMS
Page 146 of 479