CUCM: Replication Heath Check using CLI

Posted: January 26, 2009 in CUCM
Tags:

Step#1 List number of node in the cluster using CLI:

admin: run sql select name,nodeid from ProcessNode

name               nodeid

================== ======

EnterpriseWideData   1

222.22.2.22          4

222.22.2.25          2

Step#2   : Check the replication status of each subscriber/node in the cluster

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

The following list shows the possible values for Replicate_State:

0—Replication Not Started. Either no subscribers exist, or the Database Layer Monitor service is not running and has not been running since the subscriber was installed.

1—Replicates have been created, but their count is incorrect.

2—Replication is good.

3—Replication is bad in the cluster.

4—Replication setup did not succeed.

Noticed 2 means replication stats between the two surveys are okay up and running.

STEP#3 :To check network connectivity and DNS server configuration:

Enter the CLI command that is shown in below:

admin: utils diagnose module validate_network

Log file: /var/log/active/platform/log/diag1.log

Starting diagnostic test(s)

===========================

test - validate_network    : Passed                      

Diagnostics Completed

admin:

 Cheers, Push
Advertisements

Leave a Reply , I will reply ASAP

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s