Tms Agent Replication Status - Cisco TelePresence Administrator's Manual

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.2)
page (VCS configuration > Clustering
Clustering and peers
and then click View TMS
Page 159 of 498