My CER Publisher and subscriber are having DB replication issues. This morning got alert that subscriber was active due to db issue and then it went back to publisher server. The publisher is running fine but the CER Event log saids there is problem with database replication.
At the SSH Command Line, if I do a utils dbreplication status I get this.
I tried to reset the db replication and it isn't working. Has been sitting for a few hours.
I did a 'utils dbreplication reset' on publisher CER1 and it said it needed the subscriber nodename. So I did 'utils dbreplication reset CER2' and it said it was resetting the replication and it will take 15 minutes. It's been several hours now.
Now the 'utils dbreplication status' command saids it can't be ran because replication is in progress or disabled, or only one node in cluster, etc.
On the CER2 server if I look the the dbreplication log this is what it has in it.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...