Change CUCM IP Address Cisco
Change CUCM IP Address Cisco
Changing the IP Address in Cisco Unified Communication Manager sounds very easy but this most crucial part as it may end up in dbreplication failures where you might encounter issues like “Database Communication Error”. So, we have to be very careful when performing the steps. Please take a backup of your Cluster before performing the below steps.
Ensure that the Cluster is Healthy:
- Login to CLI and check for dbreplication between the clusters and ensure that it is Good. Login to CLI and enter show perf query class “Number of Replicates Created and State of Replication”. If you have just Publisher you would see the Value as 0 or if you have Publisher + Subscribers you have to ensure you see the value to be 2 which means Good.
Change the IP Address in CUCM Admin Page
- Login to CUCM Publisher Admin Page GUI >
- Go to System > Server > Click on the IP Address for which you want to change into a New IP Address.
- Host Name/IP Address > Enter the IP Address of the Publisher/Subscriber and click on Save
- Login to CUCM CLI > Enter “run sql select name,nodeid from ProcessNode” and ensure that you see the New IP Address in the Output table for the Publisher/Subscriber IP you have changed. If you don’t see the changes reflected yet, wait for sometime and verify it again. On successful verification only, go to the next step.
Change the IP Address in the OS Admin CLI
- Login to the CLI of Publisher/Subscriber for which you have changed the IP Address in the above steps.
- Configure the Default Gateway > set default gateway x.x.x.x
- Change the IP Address of the Server > set network ip eth0 x.x.x.x x.x.x.x x.x.x.x (First set of x.x.x.x is IP address, Second set of x.x.x.x is Subnet Mask and third set of x.x.x.x is the Gateway IP Address)
- Enter “Y” to continue and restart and Publisher/Subscriber for which you have just changed the IP Address
Change the IP Address of Publisher Servers on Subscribers (**This is applicable only when you have changed the Publisher IP Address**)
- Login to Subscriber > Enter the command “set network cluster publisher ip x.x.x.x” (x.x.x.x represents Publisher IP Address)
- Reboot your subscribers
Once the above steps are performed, wait for some time and verify DBReplication on your Publisher Server.
Hope this helps!!
I am working in an IT company and having 10+ years of experience into Cisco IP Telephony and Contact Center. I have worked on products like CUCM, CUC, UCCX, CME/CUE, IM&P, Voice Gateways, VG224, Gatekeepers, Attendant Console, Expressway, Mediasense, Asterisk, Microsoft Teams, Zoom etc. I am not an expert but i keep exploring whenever and wherever i can and share whatever i know. You can visit my LinkedIn profile by clicking on the icon below.
“Everyone you will ever meet knows something you don’t.” ― Bill Nye
Very Informative. Thank you.
if changing ip address or changing hostname to ip address will it cause certificate issue. or license rehost issue.
Yes this will cause certificate issue in IP Phones ITL files. You should make a process using “rollback parameters”.
But you can adapt this process to handle and support the IP phones.
When migrating IP Phones from clusters from 8.X on wards to 9.X /10.X /11.X versions, you may encounter issue with security files i.e., ITL files (Initial Trust List). which is a new security feature by default. The ITL files needs to be deleted either manually or automatically in order to register to the target Cisco Unified Communications Manager version. If the ITL files are not deleted, the device may fail to register to the new cluster.
There is a feature which was introduced in 8.X version “Prepare Cluster for Rollback to Pre-8.0?. This feature is located in Enterprise Parameters. If you are doing a flash cut-over i.e., migrating all the cluster IP Phones at one go from Legacy Cluster to New Cluster, then this feature is most appropriate and useful. It will help you to register your IP Phones from legacy 8.X Cluster to New Clusters without issues. If you are migrating the IP Phones per site/location basis, this is not a recommended option.
How to deal with this feature if you are migrating all the IP Phones at one go from Legacy Cluster to New Cluster?
Login to legacy Cluster CUCM >
1- Go to Enterprise Parameters > Prepare Cluster for Rollback to pre 8.0 > Set the parameter to True
2- Now the IP Phones will be rebooted and the dependency of ITL files will be removed
3- IP Phones will re-register to the Old Cluster
Login to the New Cluster CUCM >
1- Go to Enterprise Parameters > Prepare Cluster for Rollback to pre 8.0 > Set the parameter to True
2- Change DHCP option 150 and ensure you put the new cluster TFTP IP Address.
3- Reset the IP Phones or Device Pool from the Legacy Cluster
4- The IP Phones should start registering to the New Cluster. Monitor and ensure that all the IP Phones are registered. You may use RTMT to monitor the IP Phones registration process.
5- On the New Cluster > Go to Enterprise Parameters > Prepare Cluster for Rollback to pre 8.0 > Set the parameter to False
6- The IP Phones should start re-registering to the New Cluster again. Monitor and ensure that all the IP Phones are registered.
@Daniel, thanks for replying back!
Here is the article written on “Prepare Cluster for Rollback to Pre-8.0”
https://www.uccollabing.com/prepare-cluster-for-rollback-to-pre-8-0/
https://www.uccollabing.com/migrating-itl-files-between-cucm-clusters/
There is no mention of DNS changes which is crucial in cluster stability during re-ip.
Thanks
Ived install publisher on my phone and it is asking me for publishername and ip address what shoild i write