Cisco MCS-7825-H3-IPC1, Руководство по обслуживанию

Страница: 139 / 974

3-39
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
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 .
Step 2
To verify database replication using the CLI, access the CLI and issue the following command to check
replication on each node. You will need to run this CLI command on each node to check its replication
status. Also, after a subscriber is installed, depending on the number of subscribers, it may take a
considerable amount of time to achieve a status of 2.
admin: show perf query class “Number of Replicates Created and State of Replication”
==>query class :
- Perf class (Number of Replicates Created and State of Replication)
has instances and values:
ReplicateCount -> Number of Replicates Created = 344
ReplicateCount -> Replicate_State = 2
Be aware that the Replicate_State object shows a value of 2 in this case. The following list shows the
possible values for Replicate_State:
•
0—This value indicates that replication did not start. 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.