Last week we changed a Subscriber´s IP Address. We followed this document:
Everything appeared to be fine, but when we checked CM Database Status in Unified Reporting, an Unified CM SQLHOSTS problem was found. (the sqlhosts file on Subscriber does not match the publisher)
We tried to reset DBReplication, but the problem is still there. We followed this document:
Below you will find a copy&paste of the details. In Publisher´s sqlhosts file, the IP Address of the Subscriber´s CCM reference didn´t changed; it´s still the old one. ( subscriber´s old IP = 10.97.231.201 ; new one= 10.98.231.21)
Server sqlhosts File 10.97.231.21 g_hdr group - - i=1 g_sii_pub_ccm9_1_1_20000_5 group - - i=2 sii_pub_ccm9_1_1_20000_5 onsoctcp 10.97.231.21 sii_pub_ccm9_1_1_20000_5 g=g_sii_pub_ccm9_1_1_20000_5 b=32767,rto=300 g_sii_sub_ccm9_1_1_20000_5 group - - i=3 sii_sub_ccm9_1_1_20000_5 onsoctcp 10.97.231.201 sii_sub_ccm9_1_1_20000_5 g=g_sii_sub_ccm9_1_1_20000_5 b=32767,rto=300 ###NOTE: Need to use ipv4 address in host column of sqlhosts file and not hostname sii_pub_car9_1_1_20000_5 onsoctcp 10.97.231.21 sii_pub_car9_1_1_20000_5 b=32767 10.98.231.21 g_hdr group - - i=1 g_sii_pub_ccm9_1_1_20000_5 group - - i=2 sii_pub_ccm9_1_1_20000_5 onsoctcp 10.97.231.21 sii_pub_ccm9_1_1_20000_5 g=g_sii_pub_ccm9_1_1_20000_5 b=32767,rto=300 g_sii_sub_ccm9_1_1_20000_5 group - - i=3 sii_sub_ccm9_1_1_20000_5 onsoctcp 10.98.231.21 sii_sub_ccm9_1_1_20000_5 g=g_sii_sub_ccm9_1_1_20000_5 b=32767,rto=300
Thanks for your help.
Have you performed a cluster reboot?
if this helps, please rate
+1 on Java response. I've seen this multiple times. The solution is to reboot the entire CUCM cluster which usually resolves the issue. However, i've had one time where it required root access to modify and correct the issue. Its only be one time and I can't remember which version it was. I know that it was caused by a bug in the system.
Yes. we did a cluster reboot.
I first rebooted the publisher, and when all its services where up I rebooted the subscriber.
The problem unfortunately remains.
Is there any way to edit the SQLHOSTS file, or something??
No, the file is populated upon boot process automatically (thus the cluster reboot) and there's no way to change it without root access, as mentioned by Kelvin, I'd suggest you open a TAC.
if this helps, please rate
I managed to solve the problem. I deleted the subscriber´s server reference (via web admin page) and performed a re-install of the subscriber. Replication and everything else is fine now.
Doing a bit of investigation, I found that someone reinstalled the publisher after the installation of the subscriber.
Thanks for the help