I am about to upgrade my existing setup (CUCM 8.0 and UCCE 8.0) to CUCM 9.0 and UCCE 9.0 on UCS servers. However due to several constraints i have decided to build new setup on UCS and then migrate existing setup to new one. For this scenario, i am going to use new IP address range for the new setup. So i have to change IP addresses at lot of places (mainly worried about end points, phones and CTI toolkit usage). To overcome this, i am planning to NAT the new IP addresses with old one. So after migration, end points will send their request normally to old IP address which will be changed to new IP address range and vise versa.
i am looking for some advice whether such setup is feasible and recomended by Cisco and whether Cisco will support such setup. Please also help me with Pros and Cons if anyone has used such setup earlier.
i am also open to any other feasible solution to overcome the IP address changes. Please advice.
For CUCM if you are using a different IP for the UCS cluster compared to the original cluster then you will not be able to restore the DRS backup and will lose the configuration. DRS backup can be restored on a new cluster only if you use the same IP / hostname / DNS / security password details.
Additionally, i am curious why you are migrating to version 9.0 when version 10.5 is already out. There is a wonderful tool called Prime Collaboration deployment which you can use to migrate your existing MCS cluster to UCS with minimum outage. It allows you to build your UCS cluster while the MCS cluster is still functional. Please check the following link for details
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.