Specifications

3-40
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
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.
• 3—This value indicates that replication is bad in the cluster.
• 4—This value indicates that replication setup did not succeed.
Step 3 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.
Step 4 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.