12-05-2013 08:17 PM - edited 03-16-2019 08:44 PM
Hi All,
I have just completed a restore of a CUCM 9.1.1.20000-5 Publisher and Subscriber, all seems to be ok however replication is broken bewteen the two servers.
When I run "utils dbreplication runtimestate" from the publisher, it fails with the following:
admin:utils dbreplication runtimestate
DB and Replication Services: ALL RUNNING
DB CLI Status: No other dbreplication CLI is running...
Cluster Replication State: BATCHING SYNC Requests from nodes at: 2013-12-06-14-59
Sync Request Progress: Received 1 node requests for DB sync
Sync Request Errors: NO ERRORS
Traceback (most recent call last):
File "/usr/local/cm/bin/DbReplRTstate.py", line 1143, in ?
maxTime = getMaxDelay()
File "/usr/local/cm/bin/DbReplRTstate.py", line 604, in getMaxDelay
(rhostname, aliaslist, ipaddrlist) = socket.gethostbyaddr(temp[1])
socket.herror: (2, 'Host name lookup failure')
when i check the DB status from the reports, my pubnlisher is status = 3 (bad) and the publisher is status = 4 (initializing)
I have tried to reset the replication etc but dont seem to be getting anywhere.
Any help appreciated.
Thanks
Jason
12-05-2013 08:20 PM
After I posted this i re-run the DB status report and both Pub and Sub are now showing stats =3 (bad)..
12-05-2013 10:02 PM
Hi Jason,
Have you changed the hostname on the CUCM.
Try the following commands
"utils dbreplication dropadmindb" on Subs and then Pub
"utils dbreplication reset all" on Pub
Very good link for db issues
https://supportforums.cisco.com/docs/DOC-13672
Rate if it helps
Thanks
Ajay
12-05-2013 10:14 PM
Hi Jason,
Was the Call manager backup restored successfully on new servers?
Secondly, when u have build both the servers , did u keep all credentials same like Hostname, NTP, DNS, GW,Subnet Mask, OS Username /password, Security password and application username /password.
what is the new hardware u are using?
regds,
aman
12-08-2013 02:42 PM
THanks Guys,
No issues with the restore.
Nothing changed in regrads to hostname, ip, etc. All details were kept the same.
The new hardwrae is a VMserver, we are testing the backup and restore process in the event of a DR failure.
All looks to be working Ok, phones are registered and making calls updates made to DN and Users and being replicatied but the Replica state is still showing 3 - Bad.
I have working through the doc that Ajay has mentioned, and replication foes through the steps and I can see it initalising but then after a while it go back to state 3.
Thanks
Jason
12-08-2013 10:07 PM
Hi Jason,
can u please issue the commands and wait for sometime say 30 minutes ti check dbreplication status
a utils dbreplication stop all : PUBLISHER . wait till the command is finished on this server.
b.utils dbreplication dropadmindb : on all servers successfully. Wait till command is finished on this server and then, run on next
c. utils dbreplication reset all : on publisher
regds,
aman
12-08-2013 10:37 PM
Hi jason,
Have you checked the status before restoring ? Was it the same what you have now?
Can you check the dbstatus from RTMT as well.
Are the phones registered to SUB?
Because if phones are registered and you are able to make calls and DN status can be updated then you might be hitting some bug.
Regards,
Nishant Savalia
12-08-2013 11:08 PM
Run the unified Cmdatabase status from the reporting and please check if the following host value matches in the output.
Unified CM Hosts
Unified CM Rhosts
Unified CM Sqlhosts
Run a "utils diagnose test" from the CLI and check for any errors.
Regards
Ajay
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide