I agree. I had these kind of problems after upgrades and basically after hours and hours on TAC, we reloaded the subscriber... and magically it worked fine then. Takes about an hour to load up the subscriber again right? easy fix.
Take note though, once you do the initial publisher install, do not change ANYTHING on the publisher until the subscriber comes up. That includes IP address, names, anything in the system.
Just Wanted to report back the results of this problem.
Re-installing the subscriber servers DID NOT reslove this issue.
Opened a TAC Case.
Had tac use root access to clean up the following 4 files. /etc/hosts, /etc/services
the sqlhosts and rhosts files too.
After cleaning all four files of miscellaneous information, they did a UTILS DBREPLICATION STOP on each server starting with the 2 subs and then the pub. After this command ran succussfully they did a UTILS DBREPLICATION CLUSTERREST.
This process took 1.5 hours to complete. After this completed they rebooted the pub, waited 15 minutes and then rebooted sub1, waited 15 minutes and rebooted sub2.
Finally, all three servers sync'd up and now show 2 (good) for DB Replication.
Hope this will help someone else in this situation.
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...