cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2109
Views
0
Helpful
3
Replies

cucm replication status Off-Line

timur_rotkin
Level 1
Level 1

Hello Everyone!!!

 

I've faced to strange issue. I have 1 publisher and 6 subscribers. After reinstalling one of subscribers, database replication status of this

subscriber shows 4.  Unified CM Database Status shows that files hosts, rhosts, sqlhosts are ok. 

In Replication Server List (cdr list serv) reinstalled subscriber contain nothing. And it doesn't appear in another subscribers.

All other subscribers including publisher have database replication status 2.

 

Maybe anyone have idea how to solve this problem?

1 Accepted Solution

Accepted Solutions

Manish Gogna
Cisco Employee
Cisco Employee

Please try the following steps:

utils dbreplication stop on all subscribers

utils dbreplication stop on publisher

utils dbreplication reset all on publisher

https://supportforums.cisco.com/document/52421/troubleshooting-cucm-database-replication-linux-appliance-model#What_does_the_Status_01234_Mean

HTH

Manish

 

View solution in original post

3 Replies 3

Manish Gogna
Cisco Employee
Cisco Employee

Please try the following steps:

utils dbreplication stop on all subscribers

utils dbreplication stop on publisher

utils dbreplication reset all on publisher

https://supportforums.cisco.com/document/52421/troubleshooting-cucm-database-replication-linux-appliance-model#What_does_the_Status_01234_Mean

HTH

Manish

 

Nadav
Level 7
Level 7

If the standard dbreplication stop on subscribers, then publisher, then reset all from the publisher doesn't do the job (and by the way replication will take awhile before the subscriber status turns to 2, you can see progress under utils dbreplication runtimestate), then I would suggest using clusterreset on the publisher (use Cisco documentation to see how this is done). But this is only if you see that you can't get it working for you with the standard solution.

I had similar problems not long ago after reinstalling a publisher, sometimes replication needs a bit of tough love :) After stopping replication on all subscribers, then publisher, then performing clusterreset on Publisher and tailing the log file to see when it's done (a few hours), I reset the replication and the cluster was good to go.

timur_rotkin
Level 1
Level 1

Thanks a lot! It worked!