DB replication problems on CUCM 7.13

Unanswered Question
Feb 10th, 2010

We are having problems with replication following an IP and host name change on our Pub and Sub ( Cucm 7.13 ).. Replication worked correctly before these changes.

Using the following cisco documentation .. http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html, we have made the following changes..

1/ Change the IP on the SUB admin page.  ( changes reflect correctly on sub and pub CLI following change )

2/ change the hostname of SUB on the CLI and rebooted.

3/ update to new IP and gateway address of SUB from the CLI and rebooted all nodes.. ( changes reflected correctly on sql tables on SUB and PUB following changes, however nodes are now on different subnets and cannot communicate to each other yet, so replication at this stage fails. )..

4/ change IP on PUB admin page ( again changes reflected correct on pub but not sub due to different network addresses ).

5/ updated to new IP of PUB on the SUB OS admin page.. ( this seems to update correct on admin page but does not update when checking on CLI ? ).

6/ update to new IP and gateway on PUB CLI page.. reboot all nodes again..

7/ run utils dbreplication reset all on the PUB..

From what I can see on RTMT, SUB and PUB admin pages, all the new ip addresses have updated correctly (in System servers ) but hostnames have not updated in listed Call Managers or Call Manager groups… Is this correct … However, they are all correctly listed in the Cluster overview on the OS admin page.

New SUB IP addresses and hostnames have updated when checking CLI on the PUB and SUB.. ( run sql select name,nodeid from ProcessNode )

New PUB IP address and hostname has updated on the PUB

However, new PUB IP address has not updated on the SUB ( but is correct on the OS admin page on the SUB ? )..

The replication does not start up because the PUB can only see one node on the network ( but the SUB is pingable )… PUB replication is State 0..

The replication on the SUB is stuck on 3.. ( bad in cluster ).

Does anyone have any ideas of what to do to fix this before I go back to my backups and start again..

Thanks in advance for any advice..

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
deans2006 Sun, 02/14/2010 - 19:53

Seems like you did not change the hostnames of the Publisher and Subscribers in ccmadmin, eg,

From the Cisco Unified Communications Manager Administration window, perform the following tasks:

a. Navigate to System > Server.

b. Change the host name and/or IP address of the server under Server Configuration.

Actions

This Discussion