Cisco MCS-7825-H3-IPC1 Service Guide - Page 142

General Health and Troubleshooting Tips Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems Step 3 Step 4 Run utils dbreplication clusterreset from the affected publisher server. When you run the command, the log name gets listed in the log file. Watch this file to monitor the process status. The path to the follows: /var/log/active/cm/trace/dbl/sdi From the affected publisher, run utils dbreplication reset all. Stop and restart all the services on all the subscriber servers [or restart/reboot all the systems (subscriber servers)] in the cluster to get the service changes. Do this only after utils dbreplication status shows Status 2. Database Tables Out of Sync Do Not Trigger Alert Out of sync means that two servers in the cluster do not contain the same information in a specific database table. On Cisco Unified Communications Manager Version 6.x or later, the symptoms include unexpected call processing behaviors. Calls do get not routed or handled as expected. The symptoms may occur on either the publisher or on the subscriber servers. On Cisco Unified Communications Manager Version 5.x, the symptoms include unexpected call processing behaviors. Calls do not get routed or handled as expected but only when the publisher server is offline. If you see these symptoms, you can run the utils dbreplication status command "Out of sync" displays. If "Out of sync" does not display, this is not the problem. Possible Cause Database tables remain out of sync between nodes. Replication alerts only indicate failure in the replication process and do not indicate when database tables are out of sync. Normally, if replication is working, tables should remain in sync. Instances can occur in which replication appears to be working, but database tables are "Out of sync". Recommended Action Step 1 Step 2 Reset cluster replication by using CLI commands. Ensure servers in the cluster are online with full IP connectivity for this to work. Confirm that all servers in the cluster are online by using platform CLI and Cisco Unified Reporting. If the servers are in Replication State 2, use the utils dbreplication repair server name command on the publisher server. If the servers are not in Replication State 2, use the utils dbreplication stop command on all subscriber servers. Then, use the utils dbreplication stop and then utils dbreplication reset all commands on the publisher server. 3-42 Cisco Unified Communications Manager Managed Services Guide OL-22523-01