Specifications

3-39
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
Recommended Action
Depending on what type of interruption you experience, you will need to gather different data that will
help determine the root cause of the interruption.
Use the following procedure if a lack of resources interruption occurs.
Procedure
Step 1 Collect Cisco CallManager traces 15 minutes before and after the interruption.
Step 2 Collect SDL traces 15 minutes before and after the interruption.
Step 3 Collect perfmon traces if available.
Step 4 If the traces are not available, start collecting the perfmon traces and track memory and CPU usage for
each process that is running on the server. These will help in the event of another lack of resources
interruption.
Database Replication Fails Between the Publisher and the Subscriber
Replicating the database represents a core function of Cisco Unified Communications Manager clusters.
The server with the master copy of the database acts as the publisher (first node), while the servers that
replicate the database comprise subscribers (subsequent nodes).
Tip Before you install Cisco Unified Communications Manager on the subscriber server, you must add the
subscriber to the Server Configuration window in Cisco Unified Communications Manager
Administration to ensure that the subscriber replicates the database that exists on the publisher database
server. After you add the subscriber server to the Server Configuration window and then install Cisco
Unified Communications Manager on the subscriber, the subscriber receives a copy of the database that
exists on the publisher server.
Changes that are made on the publisher server are not reflected on phones that are registered with the
subscriber server.
Possible Cause
Replication fails between the publisher and subscriber servers.
Recommended Action
Verify and, if necessary, repair database replication, as described in the following procedure:
Procedure
Step 1 Verify database replication. You can use the CLI, Cisco Unified Reporting, or RTMT to verify database
replication.
• To verify using the CLI, see Step 2.
• To verify using Cisco Unified Reporting, see Step 3.
• To verify using RTMT, see Step 4.