CUCM 11.5 dbreplication (4) Setup Failed

[cristian.munoz]

Hi All

I have the following problem:

In the cluster, a Subscriber have the dbreplication runtimestate in (4) Setup Failed.

Any ideas to recover the correct synchronization?

TIA

Cristian

[Ratheesh Kumar]

Hi there

DB Replication status 4 is dropped. Have you gone thru the steps explained in this document.

https://supportforums.cisco.com/t5/collaboration-voice-and-video/troubleshooting-cucm-database-replication-in-linux-appliance/ta-p/3111185

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***

[Maren Mahoney]

Before you start the replication repair process, make sure that all nodes are NTP synced. If NTP is off, that may have caused the database replication problem in the first place.

[cristian.munoz]

Hi, the NTP is running.

NTP PUB

NTP Sub failed

TIA
Cristian

[Ratheesh Kumar]

Hi there

As Mahoney correctly pointed, your issue could be NTP related. NTP can mess up you DB replication.

Please check the diagnose commands 

• utils diagnose module ntp_reachability
• utils diagnose module ntp_clock_drift
• utils diagnose module ntp_stratum

Also check with the network side if the ntp packets between Pub >>> Sub for any kind of blocking. Packet capture should be a good way.

I also suggest to open up a TAC, may be faulty subscriber ntp file should be manually corrected.

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***

[cristian.munoz]

Hi

I see the following problem. The cluster have 4 servers, but the server node g_5_ccm11_5_1_10000_6 does not appear in this replication network.

Then, how to do for recover the replication in thos node?

TIA
Cristian

[Ratheesh Kumar]

Hi there

Just wondering about the security password on that subscriber. Is that a new build?

Have you tried the db replication steps from this document. If not, please try that. Most of the DB replication issues should be resolved with this.

Also you could try the below 

• Try restarting RIS Data collector on all the servers
• Try restarting Database Layer Monitor service on all the servers
• utils dbreplication reset all (run the command) 
• Reboot the cluster, starting with Pub then Subs

As a last resort you should plan rebuilding the Sub, opening a TAC/recovery

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***