×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Need clarification on db replication

Answered Question
Jul 4th, 2013
User Badges:

Hi there,  a quick question: from the following screenshot based on cucm unified CM DB Status, can any one confirm to me that there is database replication issue here.


Screenshot A indectate that both database are 2 which is good. but screenshot B shows there are is problem. which one is correctly reflecting the database replication status?


Screenshot A

All servers have a replication   count of 541.



All servers have a good   replication status.

Server

Number   of Replicates Created

Replicate_State

10.103.35.6

541

2 - good

10.103.35.7

541

2 - good



Screenshot B


Replication Server List (cdr list   serv) from every server for debugging purposes only.



Server

cdr   list serv

10.103.35.6

SERVER                   ID STATE   STATUS     QUEUE   CONNECTION CHANGED

-----------------------------------------------------------------------

g_ausyd1as_41_ccm8_6_2_21900_5  2 Active     Local           0              

g_ausyd1as_42_ccm8_6_2_21900_5   3 Active     Connected       0 May 17   20:28:31

10.103.35.7

SERVER                   ID STATE   STATUS     QUEUE   CONNECTION CHANGED

-----------------------------------------------------------------------

g_ausyd1as_41_ccm8_6_2_21900_5   2 Active     Connected       0 May 17   20:28:31

g_ausyd1as_42_ccm8_6_2_21900_5  3 Active     Local           0              

Correct Answer by Aman Soi about 4 years 1 month ago

Hi Roy,


Both the screenshots are correct.


First screenshot shows DBreplication which is fine.


Second Screenshot also shows replication and is OK.HAd DBReplication been problem , it would have shown DROPPED instead of Active.Values 2 and 3 correspond to ID State[which could be identity] of Pub abd SUB. Had there been third server in cluster, it would have ID state as 4.


regds,

aman

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Aman Soi Thu, 07/04/2013 - 05:16
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Hi Roy,


Can u share the output of utils dbreplication runtimestate from Publisher using CLI?


regds,

aman

Correct Answer
Aman Soi Thu, 07/04/2013 - 07:34
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Hi Roy,


Both the screenshots are correct.


First screenshot shows DBreplication which is fine.


Second Screenshot also shows replication and is OK.HAd DBReplication been problem , it would have shown DROPPED instead of Active.Values 2 and 3 correspond to ID State[which could be identity] of Pub abd SUB. Had there been third server in cluster, it would have ID state as 4.


regds,

aman

ciscoroyzhang Thu, 07/04/2013 - 18:55
User Badges:

Hi aman,  thanks for the reply.  the result from "untils dbreplcation status" is same as the scrrenshot B, I was bit confuresed with 2 and 3 in the screenshot B. thanks for clarifying this.... cheers Roy

Aman Soi Thu, 07/04/2013 - 19:49
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Hi Roy,


Thanks for rating.


regds,

aman

madhusudhanam Thu, 07/04/2013 - 20:22
User Badges:

Hello Roy / Aman,


The below Information may help i believe.


Replicate_State counter

Use the Syslog viewer in the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT) in order to check the Replicate_State counter for the Number of Replicates Created and State of Replication object on all nodes. The value on each node must equal 2. This counter represents the state of replication, which includes these possible values:

  • 0 (Not Started)—No subscribers exist or the Database Layer Monitor service is not running and has not been running since the subscriber was installed.


  • 1 (Started)—Replication is currently being setup.


  • 2 (Finished)—Replication setup is completed and working.


  • 3 (Broken)—Replication failed during setup and is not working.


  • 4—Replication is not setup correctly.


Note: This information is the same for Cisco CallManager version 5.1(3) and all 6.1 versions.


Regards,

M.Madhusudhana Rao

Actions

This Discussion