Virtual CUCM in VMware Change IP Address of publisher node

[alfredobosca]

Hello for all,

I am migrating the cluster of CUCM in PRO to VMware. Once is created the PRO cluster on VMware I need to change the IP address of Publisher node. In order to change the IP address I applied the next technote publisher by Cisco: http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/116292-install-cucm-00.html. It seems that doesn't works with VMware CUCM.

When change the IP address like the previos technote appear one database error message.

On this case I have verified:

- service "A Cisco DB" is reseted and STARTED OK

- Stop the CEF service from serviceability page

At finally I think that the procedure is different between Physical and Virtual CUCM.

Best regards,

[Suresh Hudda]

What steps you have followed..

Below are the main steps..

1. System > Server and click Find, Change the IP address here. then...

2. Change IP address from OS admin page or run this command from CLI "set network ip eth0 <new ip address> <subnet mask> 

Suresh

[alfredobosca]

I have realized these steps and isn't works with Vmware.

[alfredobosca]

Before change the IP of Publisher member is necessary to remove the subscriber from the cluster. So the publisher won't try to contact the DB of Subscriber member.

[Rajan · Accepted solution]

Hi Alfred,

As Suresh pointed the procedure remains the same. Since you see this error message after changing IP, have you tried the first solution.

Solution 1

This issue can occur when you try to login to the server after changes are made in the Publisher server, such as changing the hostname or IP address either through CLI or the OS admin page. In this case, complete these steps to resolve the issue:

1. Revert the changes made back to the old settings in order to let you log in.

2. Go to Cisco Unified CM Administration > System > Server and make the required changes for the hostname or IP address.

3. Make the same changes via CLI or the OS admin page.

   The CUCM will restart itself.

4. After restarting check if services are loaded properly.

5. Use the utils service list CLI command in order to check if the services are up and running.

6. Restart the whole cluster manually again to have all the services loaded properly.

HTH

Rajan