Specifications

3-41
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
• 2—This value indicates that replication is good.
• 3—This value indicates that replication is bad in the cluster.
• 4—This value indicates that replication setup did not succeed.
d. To view the Replicate_State performance monitoring counter, choose System > Performance >
Open Performance Monitoring. Double-click the publisher database server (first node) to expand
the performance monitors. Click Number of Replicates Created and State of Replication.
Double-click Replicate_State. Click ReplicateCount from the Object Instances window and click
Add.
Tip To view the definition of the counter, right click the counter name and choose Counter
Description.
Step 5 If all the servers have a good RTMT status, but you suspect the databases are not in sync, you can run
the CLI command utils dbreplication status (If any of the servers showed an RTMT status of 4, proceed
to
Step 6).
This status command can be run on all servers by using utils dbreplication status all or on one
subscriber by using utils dbreplication status <hostname>.
The status report will tell you if any tables are suspect. If there are suspect tables, you will want to do a
replication repair CLI command to sync the data from the publisher server to the subscriber servers.
The replication repair can be done on all subscriber servers (using the all parameter) or on just one
subscriber server by using the following:
utils dbreplication repair usage:utils dbreplication
repair [nodename]|all
.
After running the replication repair, which can take several minutes, you can run another status
command to verify that all tables are now in sync. If tables are in sync after running the repair, you are
successful in fixing replication.
Note Only do Step 6 if one of the servers showed an RTMT status of 4, or had a status of 0 for more than four
hours.
Step 6 Generate and view the Cisco Unified CM Database Status report, which provides debugging
information for database replication. For each subscriber server that has a bad RTMT status, check that
the hosts, rhosts, sqlhosts, and services files have the appropriate information.
Generate and view the Cisco Unified CM Cluster Overview report. Verify that the subscriber servers
have the same version, verify that connectivity is good, and verify that time delay is within tolerances.
If the preceding conditions are acceptable, do the following to reset replication on that subscriber server:
a. At the subscriber server, perform the CLI command utils dbreplication stop
Do this for all subscriber servers that have an RTMT value of 4
b. At the publisher server, perform the CLI command utils dbreplication stop
c. At the publisher server, perform the CLI command utils dbreplication reset <hostname> where
<hostname> is the hostname of the subscriber server that needs to be reset. If all subscriber servers
need to be reset, use command utils dbreplication reset all