Changing IP Addresses of CM7.x Sub/Pub that's already in production

Unanswered Question
Apr 22nd, 2010


We are in the middle of a building move and IP schema restructure.  In the interim we are also planing on upgrading CM 4.23 to CM 7.x. If we decide to migrate now to CM7 will it be a problem changing the IP addresses of the SUB and PUB later down the line when we finalize our IP schemes?

I heard that it will not be a problem to change it but can create many problems down the line and eventualy paralize the system? Which is it? What kind of things should we look out for? Should we just do the upgrade after the IP scheme is finalized?

Thanks all!!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
iptuser55 Thu, 04/22/2010 - 01:02

Changing the IP Address and even the Hostname of the CUCM from 6.1.2 onwards. The main things you need to make sure is any 3rd party apps which point to CUCM via IP Address, Extension Mobility, IP Services etc on CUCM. The other issue is the Option150 pointing to the TFTP server - need to change it to the new IP Address and CUCM backup`s- back up before you do the change and after the change back up again as the old Backup will not work due to the change . Also any TSP clients as in Switchboard, Voice Recording etc need to change as well

erickscisco Thu, 04/22/2010 - 11:32

Thank you aaronharrison, iptuser55.  So can I assume that you two have succesfully done this before and changed the IP address of a sub and pub with no implications?

I'm sure it can be done easily, but my worries are things happening later on.

Wilson Samuel Thu, 04/22/2010 - 11:50


I will request you to test with all possible options in a lab, as a pilot plan and then attempt in production set up.

You may install CCM 7 on VMWare machine pretty easily and by copying database you may build almost exact replica of the server.

All the Best!



Sam Wilson

Aaron Harrison Thu, 04/22/2010 - 12:28


Yes, done this a few times recently.

I had a node rename fall over badly on about a year or so ago on 6.1, but recently had no problems.


erickscisco Thu, 04/22/2010 - 12:41

When you changed it, how soon did it fail? What were the symptoms?


David Hailey Thu, 04/22/2010 - 15:29

I've done this multiple times on several production systems with issue for customers.  You just need to make sure to follow the steps in the documentation Aaron gave a link for and also to reboot each server after every step.  Make sure the hostnames are propagated via CLI when changed and you'll be golden.

Read, plan, and prep and you'll be good to go.


iptuser55 Fri, 04/23/2010 - 00:27

When you do the change, carry out the IP address change first via the GUI on the CUCM web pages, then access the CLI and do then change there next otherwise it causes problem. Once you can access the servers I would suggest balancing. Then do a utlis dbreplication status or  do it via the Reporting option on the GUI to check everything is ok. I`ve regularly changed them in a lab as part of other testing without any issues 

Aaron Harrison Fri, 04/23/2010 - 00:44

Symptoms were DB not starting etc. In fairness, it was the first release that supported hostname change; I've had no problems since.

rob.huffman Fri, 04/23/2010 - 06:39

Hi Erick,

Just to add a note and doc to the great tips so far from Aaron, IPT, Sam and Hailey

(+5 points each my friends for your excellent contributions)

If you want to do this on your 4.2 system before moving forward with your

upgrade to 7.x it's also supported. We did this on 4.2(3) a few years ago

Changing the IP Address for Cisco CallManager

From this  excellent doc;

Hope  this helps!


Please support CSC Helps Haiti


This Discussion