The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You cannot upgrade directly to Unified Communications Manager Release 10.5(1) from Releases 4.1(3), 4.2(3), 4.3(2), 5.1(2), 5.1(3), 6.0(1), 6.1(1), 6.1(2), 6.1.(3), 7.0(1), 7.0(2), and 7.1(2) . For these releases, upgrade to the release listed in the table below and then perform the migration.
Current Release |
Upgrade to... |
---|---|
4.1(3), 4.2(3), 4.3(2) |
7.1(5) using DMA |
5.1(3), 6.1(3), 6.1(4) |
6.1(5) |
5.1(2), 6.1(1), 6.1(2) |
Upgrade to 6.1(3), then 6.1(5) (This is a multiple upgrade). |
6.0(1) |
Upgrade to 6.1(2), then 6.1(3), then 6.1(5) (This is a multiple upgrade). |
7.0(1) |
Upgrade to 7.0(2), then 7.1(5) (This is a multiple upgrade). |
7.0(2), 7.1(2) |
7.1(5) |
Complete the migration in the following stages:
Upgrade to Unified Communications Manager Release 6.1(5) or 7.1(5) as an intermediate release.
Deploy Prime Collaboration Deployment on a virtual machine.
Prepare Prime Collaboration Deployment for Cisco Unified Communications Manager cluster migration to Release 10.5(1).
Migrate to the current Unified Communications Manager release using Prime Collaboration Deployment.
Upgrading from Releases 6.1(5), 7.1(3), 7.1(5), 8.0(1-3), 8.5(1), 8.6(1-2), 9.0(1), 9.1(1-2)
Use the following procedure to upgrade to Unified Communications Manager Releases 6.1(5) or 7.1(5) from any of the following releases:
Step 1 | Stop all configuration tasks. Do not perform any configuration tasks during the upgrade. |
Step 2 | Disable extension mobility for the cluster. |
Step 3 | Perform a DRS backup of your current cluster. |
Step 4 | Upgrade the publisher node to Unified Communications Manager from the current release to the target release and choose No for automatic reboot. |
Step 5 | Upgrade the dedicated TFTP node, followed by the backup subscriber nodes and the primary subscriber nodes in the cluster. During these upgrades, choose No for automatic reboot. |
Step 6 | Switch the publisher node to the upgraded partition. |
Step 7 | Install the phone firmware that corresponds to the Unified Communications Manager Release 10.(1) in the publisher. If your publisher node is also the TFTP server, restart the TFTP service. |
Step 8 | Verify that the database replication for the cluster completed without errors. Use the Cisco Unified Reporting or Cisco Real Time Monitoring Tool (RTMT); for more information, see the Upgrade Tasks section of the Upgrade Guide for Cisco Unified Communications Manager, Release 9.1(1). |
Step 9 | Configure the phones and devices in the cluster to use the backup subscriber nodes for registration by changing the order in the Unified Communications Manager group. |
Step 10 | Switch all of the primary subscriber nodes to the upgraded partition. |
Step 11 | Verify that the primary subscriber nodes are upgraded and that the database replication completed with no errors. |
Step 12 | Configure the phones and devices in the cluster to use the primary subscriber nodes for registration by changing the order in the Unified Communications Manager group. Reset the devices using the device pool in an ordered manner, or restart the Unified Communications Manager service on the backup subscriber nodes to allow devices to register with the primary subscriber nodes. |
Step 13 | Perform a Disaster Recovery System (DRS) backup up of your entire cluster now that it is upgraded. |
Step 14 | Deploy Prime Collaboration on a virtual machine. For more information, see Deploy Prime Collaboration Deployment on a Virtual Machine. |
Cisco Prime Collaboration Deployment requires a separate virtual machine and is not supported on physical servers. Prime Collaboration Deployment can be deployed using vApp. vApp bundles OVA template and installation ISO into a single file.
Cisco Prime Collaboration Deployment is not compatible with all license types of VMware vSphere ESXi, because some of these licenses do not enable required VMware APIs. Be aware of the following ESXi licensing requirements for Cisco Prime Collaboration Deployment and virtual machines that are required for Unified CM Release 10.5(1), since it has impact to the migration functionality. Cisco Unified Communications Manager Business Edition 6000 customers are impacted due to the below license requirement.
The following licenses are compatible with Cisco Prime Collaboration Deployment:
Cisco UC Virtualization Foundation (appears as Foundation Edition in vSphere Client)
VMware vSphere Standard Edition, Enterprise Edition, or Enterprise Plus Edition
Evaluation mode license
Configure Prime Collaboration. For more information, see Configure Prime Collaboration Deployment to Migrate Current Unified Communications Manager Cluster to Release 10.5(1).
A migration task is used to simultaneously upgrade and migrate an existing Cisco Unified Communications Manager cluster to new Release 10.5(1) running virtual machines.
Step 1 | Deploy the virtual hardware infrastructure for the new cluster and install ESXi. | ||||
Step 2 | SFTP the recommended OVA and bootable .iso images for the Unified Communications Manager Release 10.5(1), to the Prime Collaboration Deployment server under /fresh_install directory. Use adminsftp and the password of the Platform (OS) admin to connect to the Prime Collaboration Deployment server using SFTP. | ||||
Step 3 | Deploy the Cisco-recommended OVA for Unified Communications Manager Release 10.5(1) to create the blank VMs for the destination cluster node installation. | ||||
Step 4 | Add the ESXi Hosts that contain your virtual machines to the Cisco Prime Collaboration Deployment inventory. You will need to provide the hostname or IP address of the ESXi host, and the root credentials. For details, follow the Add ESXi Host Server procedure. | ||||
Step 5 | Ensure that you have performed a cluster discovery for the existing Cisco Unified Communications Manager cluster (source cluster) so that it appears in the Cluster Inventory. For details, follow the procedure Discover Existing Cluster. | ||||
Step 6 | Create the
migration cluster (Inventory > Clusters) to define the mapping between MCS
source nodes and target virtual machines. For details, follow the
procedure Define Migration Cluster.
| ||||
Step 7 | (Optional) Navigate to When email notification is set up, the Prime Collaboration Deployment server emails error conditions that may occur during the migration task. and set up email notifications. | ||||
Step 8 | Create the Migration Task in Prime Collaboration Deployment. For details, follow the procedure Add a Migration Task. |
The Discover Cluster feature allows Cisco Prime Collaboration Deployment to contact servers that are already running Unified Communications Manager, and add that cluster information into the Cisco Prime Collaboration Deployment inventory.
Before you can create a migration task, you must create a migration cluster. By defining the migration cluster, you create the mapping from the current Cisco Unified Communications Manager cluster nodes that were discovered (see Discover a cluster) and the new VMs that will be used to host the migrated cluster.
Step 1 | Select from the Prime Collaboration Deployment menu. You will see the clusters that have been discovered (or defined) so far. | ||
Step 2 | Click Define Migration Destination Cluster to start the Define Migration Destination Cluster wizard. | ||
Step 3 | Complete step
1 of the Configure Destination Cluster wizard:
| ||
Step 4 | Click Next. | ||
Step 5 | Click the Assign Destination Cluster Nodes button to open the Configure Destination Cluster window. | ||
Step 6 | Configure the destination cluster by selecting a destination VM for each source node. The source node hostname listed is at the top of the page. | ||
Step 7 | When all nodes have been assigned a destination VM, click DONE to close the Configure Destination Cluster window. Prime Collaboration Deployment displays the source nodes in the cluster, listed next to the destination VM to be used for this node, and the IP address. | ||
Step 8 | If the information is accurate, click Next to move to Step 3 of the wizard. | ||
Step 9 | In the Configure NTP/SMTP settings window, enter the Network Time Protocol (NTP) server settings to be applied to the migration nodes when the migration task runs, and the SMTP server settings. | ||
Step 10 | Click Next. Step 4 of the Define Migration Destination wizard, Configure DNS Settings, opens. You have the option of configuring DNS for the migration cluster nodes. | ||
Step 11 | To change the DNS setting for a node, select the node(s) from the table and click the Assign DNS Settings button. Enter the primary and secondary DNS and the domain, then click OK to apply the changes. | ||
Step 12 | Click Finish to close the wizard and save your changes. The new cluster definition is added in the Cluster Inventory with a cluster type of “Migration.” |
Step 1 | Select from the main menu. | ||
Step 2 | Click Add Migration Task. The Add Migration Task wizard displays. | ||
Step 3 | From the Source UC Cluster drop-down list box, select the destination cluster or migration map. Migration maps are associated with the source cluster that you have selected. | ||
Step 4 | Click Next. | ||
Step 5 | In the Choose Migration Files section, browse and select the Cisco Unified Communications Manager ISO file to install on the destination cluster. The Choose a Migration File window opens. | ||
Step 6 | Select the ISO file from the list and click OK. | ||
Step 7 | Click Next. | ||
Step 8 | In the Set Start Time section, choose one of the following options and click Next: | ||
Step 9 | In the Specify
Migration Procedures section, set the sequence for the migration task.
Following is the recommended sequence:
When you create a migration task, Prime Collaboration Deployment presents the default sequence, which has one server in each install step. You can use the editing tools to place more than one server in a step. For best results, do not include more than six servers in any one step.
| ||
Step 10 | Click Next. | ||
Step 11 | Review your selections. In the Review section, you also have the option to add notes to your new migration task. | ||
Step 12 | Click Finish to add the new migration task. The task appears in the table on the Migrate screen. | ||
Step 13 | Perform a DRS backup of your Unified Communications Manager cluster. | ||
Step 14 | Proceed to Migrate Cisco Unified Communications Manager to Release 10.5(1). |
The configuration that has been completed so far as part of section 8 is non-service disruptive and was to get Prime Collaboration Deployment configured to support the migration of Unified Communications Manager Cluster to Release 10.5(1). Use the following procedure to migrate your current Unified Communications Manager Release to Release 10.5(1) using Prime Collaboration Deployment.
Step 1 | Stop all configuration tasks on your Cisco Unified Communications Manager cluster. Do not perform any configuration tasks during upgrade. | ||
Step 2 | Disable extension mobility for the cluster. | ||
Step 3 | Log in to Prime Collaboration Deployment and click on Monitoring to view the task status. The task will be listed in the task list, but will be waiting for manual start. | ||
Step 4 | To view the
details that each step of the migration task will perform, click on the black
triangle next to the task step.
| ||
Step 5 | Click the
Start button that is associated with this manual
task.
The first Unified Communications Manager publisher is migrated. Prime Collaboration Deployment shuts down the current Unified Communications Manager publisher automatically. The migration task pauses once the publisher is successfully migrated to Unified Communications Manager 10.5(1). | ||
Step 6 | Log in to the publisher that is running Unified Communications Manager 10.5(1) and verify that all services that were enabled on the pre-10.5(1) are still running. | ||
Step 7 | Click
Resume to continue the migration.
The migration task migrates your dedicated TFTP node, and all backup subscriber nodes, to Unified Communications Manager 10.5(1). Prime Collaboration Deployment shuts down corresponding nodes that are running on MCS servers. The migration task pauses once the dedicated TFTP node and backup subscriber nodes are migrated. | ||
Step 8 | Verify that
the database replication between Publisher and TFTP node, backup subscriber
nodes is setup and completed without errors.
| ||
Step 9 | Configure the phones and devices in the cluster to use the backup subscribers nodes for registration by changing the order in the Unified Communications Manager group, or by using device pools. | ||
Step 10 | Click
Resume to continue the migration.
The migration task migrates all the primary subscriber nodes to 10.5(1). Prime Collabarion Deployment shuts down corresponding nodes that are running on MCS servers. At this point, all the IP Phones and devices register with the backup subscriber nodes on Release 10.5(1), as the primary subscriber nodes that are running on MCS hardware are shut down. | ||
Step 11 | Once all primary subscriber nodes are successfully migrated to UCM 10.5(1), Verify that the database replication between Publisher and all nodes is set up and in good state. | ||
Step 12 | Configure the phones and devices in the cluster to use the primary subscriber nodes for registration by changing the order in the Unified Communications Manager group. You can reset the devices using the device pool in an ordered manner, or restart the Unified Communications Manager service on the backup subscriber nodes to allow devices to register with the primary subscriber nodes. | ||
Step 13 | Install Unified CM Release 10.5(1) dial plans and locales as recommended in the Post-upgrade tasks section of the Upgrade Guide for Cisco Unified Communications Manager. For details, see the Prime Collaboration Deployment Administration Guide. | ||
Step 14 | If you changed any database replication timeout values as per the general pre-upgrade procedures section, restore the timeout to the default value. Enable extension mobility that was turned off at the start of the upgrade. | ||
Step 15 | Verify that the virtualized Unified CM cluster services and device registration is operating. At this point, the entire virtual Unified CM cluster is on Release 10.5(1). | ||
Step 16 | Migrate your
current Unified CM licenses to the Unified CM Release 10.5(1) license.
| ||
Step 17 | Run your post-upgrade test plan. On the successful completion of the post-upgrade test plan, your migration to Cisco Unified Communications Manager 10.5(1) is complete. | ||
Step 18 | Perform a DRS backup of the cluster. |