CUCM CUC CER IM&P to move on new Hardware

[n.shuja]

The existing cluster(s) are configured across 2 DC's. DC 1 is being decommissioned. All the applications instances to move on a new location DC 3.

The versions are NOT going to change nor the setup at DC 2 will be touched. IP addresses will be from different subnet and new HW will be utilized.

Whats the best way to achieve it? I can do PCD for some applications but i am not sure if that can have an impact on DC 2 instances of applications. 

Since DC 1 will run parallel till the cutover is planned what should be the best way to achieve pre-cutover tasks.

Applications to be moved are

1. CUCM (Only 2 Sub and 1 TFTP)
2. CUC (Only Primary)
3. IM&P (Only Primary)
4. CER (Only Primary)
5. PLM

Thanks

[Ratheesh Kumar]

Hi there

You can actually do this, more a manual method. I still prefer this

• Spin up the servers at DC 3
• Connect to an Isolated network
• Install the applications with existing IP Address
• Restore the backups on Primary servers
• Once you successfully restored, change your ip address to the new schema and keep all Applications shutdown.
• During the cutover period, connect the servers to the new Live network and start all the applications (Make sure your routing works with new ip across the sites, consider DNS, NTP, b/w etc)
• Make sure all the services are getting up and running, Initiate a Database replication and make sure the replications are Good

For CUCM,

• You can install a dummy PUB in DC3 in your standalone network with existing ip address
• Restore the backup
• Install the SUB the new SUB and TFTP.
• Make sure all the services are getting up and running, Initiate a Database replication and make sure the replications are Good
• Change the IP Address of SUB and TFTP (You need to create another instance of isolated network here)
• Make sure all the services are getting up and running, Initiate a Database replication and make sure the replications are Good
• Shutdown the applications
• During cutover, make sure the DC 3 PUB is Shut down (later you can delete that instance)
• Connect the servers to the new Live network and start all the applications (Make sure your routing works with new ip across the sites, consider DNS, NTP, b/w etc)
• Make sure all the services are getting up and running, Initiate a Database replication and make sure the replications are Good

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***

[n.shuja]

Thanks for reply Rath.
for Non CUCM Apps. the last steps you mentioned
"Make sure all the services are getting up and running, Initiate a Database replication and make sure the replications are Good"
Once the IP address is changed and new publisher is online. How the sub will sync with new server instead of old server? Looking for some detail if i have to do anything on the Sub for CUC / CER / IM&P to point to new Pub.
thanks

[Ratheesh Kumar]

Hi there

Once you change the PUB to the new ip address you have to change the publisher references in all your secondary nodes. Make sure you run a DRS backup prior to this change, all required changes in DNS and in your network, Schedule an after business hours for this. Post change you have to run thru the post config changes and the followed by a DB replication reset.

Below are the docs for changing the ip address 

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/install_upgrade/guide/b_11xcuciumg/b_11xcuciumg_chapter_0100.html#ID-2164-000001b8

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/11_5_1/english/administration/guide/CER_BK_R00ED2C0_00_cisco-emergency-responder-administration-guide-1151/CER_BK_R00ED2C0_00_cisco-emergency-responder-administration-guide-1151_appendix_01110.h...

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/ipchange/cucm_b_change-ip-address-and-hostname_1151.pdf

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***