CUCM 5.1(3) replication problem

Unanswered Question
Apr 1st, 2008

Hi all.

I have a cluster with one Publisher and a Subscriber. Because of some unexpected behaviour I have noticed that I was having problems with the replication between the two nodes. And the CLI commands for dbreplication confirmed that suspicion.

The way to recover from that state is already known: by using "utils dbreplication reset all" after stopping the replication in all nodes.

I also have noticed that this replication errors happens when the Publisher is restarted.

What I would like to known is why does this happens? Is this the normal behaviour or is it a bug?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
vmoopeung Mon, 04/07/2008 - 06:24

I think this happens because Publisher is the primary database server and the loss of connection to the publisher results in replication errors.


This Discussion