I have a CUCM 184.108.40.20600-5 publisher that has been live for a few months. I recently added a subscriber but am unable to activate callmanager services on it because replication is failing.
When i run the DB replication report on the publisher i have the following errors. On the subscriber i get the opposite.
|Server||Publisher DB Reachable||Local DB Reachable|
|10.244.44.11||Source has failed due to source on 10.244.44.11 timing out|
Source has failed due to source on 10.244.44.11 timing out
I have connectivity between both and that same report also shows this:
|RTMT Counter Information|
|All servers have a replication count of 519.|
|All servers have a good replication status.|
Lastly, i have tried using utils dbreplication
Ran utils dbreplication stop on both Sub and then Pub
Ran utils dbreplication dropadmindb on both Sub and then Pub
Ran utils dbreplicatin clusterreset
Ran utils dbreplication reset all on Pub
Rebooted Subscriber (Not Publisher).
The only other item is i don't have DNS set on the publiser or subscriber.
Solved! Go to Solution.
I had a similiar issue on 8.6(2)asu1 that was caused by changing the security password on the Publisher. After changing that password, I was having trouble getting a new sub added to the cluster.
I opened a TAC caes and they ran the script to sync the secuirty password and this resolved the issue for me.
My symptoms were seeing the message: 'Source has failed due to source on' when I tried to run many of the Unified Reports. Also the dbreplication was hosed as the new sub was reported as 'not connected' and none of the dbreplcation commands were working.
Please take a look at the blog and video I posted on dbreplication runtimestate:
Please feel free to provide your feedback and any additional questions you may have on this topic.