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

General Health and Troubleshooting Tips Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems Step 3 Step 4 • 3-This value indicates that replication is bad in the cluster. • 4-This value indicates that replication setup did not succeed. To verify database replication using Cisco Unified Reporting, perform the following tasks: a. From the Navigation drop-down list box in the upper, right corner in Cisco Unified Communications Manager Administration, choose Cisco Unified Reporting. b. After Cisco Unified Reporting displays, click System Reports. c. Generate and view the Cisco Unified CM Database Status report, which provides debugging information for database replication. Once you have generated the report, open it and look at the Cisco Unified CM Database Status. It gives the RTMT replication counters for all servers in the cluster. All servers should have a replicate state of 2, and all servers should have the same number of replicates created. If you see any servers whose replicate states are not equal to 2 in the above status check, inspect the "Replication Server List" on this report. It shows which servers are connected and communicating with each node. Each server should show itself as local (in its list) and the other servers as active connected. If you see any servers as dropped, it usually means there is a communication problem between the nodes. d. If you want to do so, generate and view the Cisco Unified CM Database Status report, which provides a snapshot of the health of the Cisco Unified Communications Manager database. To verify database replication using RTMT, perform the following tasks: a. Open the Cisco Unified Real-Time Monitoring Tool (RTMT). b. Click the CallManager tab. c. Click Database Summary. The Replication Status pane displays. The following list shows the possible values for the Replication Status pane: • 0-This value indicates that replication has not started. Either no subsequent nodes (subscribers) exist, or the Cisco Database Layer Monitor service is not running and has not been running since the subscriber was installed. • 1-This value indicates that replicates have been created, but their count is incorrect. • 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). 3-40 Cisco Unified Communications Manager Managed Services Guide OL-22523-01