CUCM 11.5 move to another VMWare host (different location)

[shivani.sharma]

Hello,

We need to move a CUCM 11.5 VM to a different VMWare host at a different location. I am trying to figure out the best way to do this. The public IP address of the host will change. And also we need to move the phone endpoints in batches since this CUCM supports multiple customers. I would like to create a copy of existing VM on the new host and then have both the instances running at the same time so that we can migrate the endpoints in batches. If I create a copy will that change the MAC address of the new instance? And if it does can I associate the existing phone licenses from the Cisco Prime License Manager to the new instance? Please advise what would be the best way to do this.

Thank you.

[MarceloHernandez1284]

Hello Daniel,

Could you share the additional steps needed for moving IM&P servers as well (I'm in the process of moving and re-IP-ing the PUB IM&P).

Thank you.

[DanielDragosz]

Disable High Availability (HA) on all presence redundancy groups.For information on Presence Redundancy Groups configuration, see the "Configure Presence Redundancy Groups" chapter in theSystem Configuration Guide for Cisco Unified Communications Manager. Note Before you disable HA, take a record of the number of users in each node and subcluster. You can find this information in theSystem>Presence Topology window of Cisco Unified CM IM and Presence Administration. After you disable HA, wait at least 2 minutes for the settings to sync across the cluster before completing any further changes.

Compile a list of all services that are currently activated. Retain these lists for future reference.

Stop all feature services using Cisco Unified Serviceability, selectTools>Control Center - Feature Services. The order in which you stop feature services is not important. Tip You do not need to complete this step if you are changing the IP address, hostname, or both the IP address and hostname. Feature services are automatically stopped for these name changes.

Stop the following network services that are listed under theIM and Presence Serviceservices group using Cisco Unified Serviceability when you selectTools>Control Center - Network Services. Cisco Config Agent Cisco Intercluster Sync Agent Cisco Client Profile Agent Cisco OAM Agent Cisco XCP Config Manager Cisco XCP Router Cisco Presence Datastore Cisco SIP Registration Datastore Cisco Login Datastore Cisco Route Datastore Cisco Server Recovery Manager CiscoIM and PresenceData Monitor

Verify that the Cisco AXL Web Service is started on theCisco Unified Communications Managerpublisher node using Cisco Unified Serviceability,Tools>Control Center - Feature Services.

Verify that the IM and Presence Cisco Sync Agent service has started and that synchronization is complete. Note Perform this step only if you are changing the domain name or node name.To verify using Cisco Unified Serviceability, perform the following steps: SelectTools>Control Center - Network Services. Select the IM and Presence database publisher node. SelectIM and Presence Service Services. Verify that the Cisco Sync Agent service has started. From the Cisco Unified CM IM and Presence Administration GUI, selectDiagnostics>System Dashboard>Sync Status. Verify that synchronization is complete and that no errors display in the synchronization status area. To verify using the Cisco Unified CM IM and Presence Administration GUI on the IM and Presence database publisher node, selectDiagnostics>System Dashboard.

[DaviRocK!]

Migrating a Cisco Unified Communications Manager (CUCM) 11.5 virtual machine (VM) to a different VMware host at a new location, especially when it involves changing the public IP address and moving phone endpoints in batches for multiple customers, requires careful planning and consideration. Here are the key steps and considerations for this process:

1. Assess Licensing Implications:

• MAC Address Dependency: CUCM licensing, especially for versions like 11.5, is often tied to the MAC address of the VM. If the MAC address changes (which typically happens when cloning or moving VMs), it can affect the licensing.
• Cisco Prime License Manager: You'll need to check whether the licenses can be migrated or re-hosted to the new MAC address. Cisco Prime License Manager should allow you to re-host licenses, but this process can vary based on the specific license type and Cisco's policies at the time of migration.

2. Clone and Move the VM:

• Creating a Clone: When you clone the CUCM VM, the new instance will indeed have a different MAC address. This is standard behavior in VM environments to avoid network conflicts.
• Preserving Settings: Ensure that all configurations, including network settings (apart from the IP address), are preserved in the clone.

3. Update Network Settings:

• IP Address Change: Update the public IP address in the new VM instance. This will also involve updating your DNS settings, DHCP scopes (if used), and any network configurations that rely on the IP address of the CUCM.

4. Batch Migration of Phone Endpoints:

• Phased Approach: Migrate phone endpoints in batches. Update the endpoints to point to the new CUCM instance. This can often be done through the DHCP option or manually on each phone, depending on your setup.
• Testing: After migrating each batch, thoroughly test to ensure that phones register correctly with the new CUCM instance and that all functionalities are working.

5. Licensing and Activation:

• Re-host Licenses: Work with Cisco or your Cisco partner to re-host the licenses to the new MAC address. This might involve providing the new MAC address to Cisco and receiving new license files.
• License Activation: Upload and activate the new licenses on the cloned CUCM instance.

6. Ensure Redundancy and Backups:

• Backup: Before starting the migration, ensure you have a complete backup of the CUCM.
• Redundancy: If possible, maintain the old CUCM instance running until you are confident that the new instance is fully operational and stable.

7. Monitor and Support:

• Monitoring: Closely monitor the new CUCM instance for any issues.
• Support: Prepare to address any issues reported by customers during and after the migration.

Additional Considerations:

• Downtime: Plan for potential downtime and communicate this to the affected customers.
• Documentation: Keep detailed documentation of all changes and settings.
• Cisco Support: Engage Cisco Support if you encounter issues with licensing or functionalities.

This process can be complex and requires detailed planning. It’s advisable to consult with a Cisco-certified professional or reach out to Cisco Support for guidance specific to your environment and licensing arrangement.