Cisco Unified Communications Manager 9.1 Migration and Upgrade Guide
Migration and upgrade scenarios
Downloads: This chapterpdf (PDF - 311.0KB) The complete bookPDF (PDF - 765.0KB) | Feedback

Migration and upgrade scenarios

Migration and upgrade scenarios

Key upgrade tasks

When you upgrade from any release of Cisco Unified Communications Manager to Release 9.1 while virtualizing at the same time, there are five keys to making the upgrade successful. Following these important principles (while following the appropriate upgrade path) results in an efficient upgrade path:

  1. Apply all Product Authorization Key (PAK) codes before upgrading to Release 9.1 or later.
  2. Rehost licenses where indicated.
  3. Ensure that bootable Release 8.0(x) and/or Release 9.1(x) installation media are available.
  4. Upgrade all nodes of the cluster on the production network.

    Note


    Do not install subscribers as new.


  5. Install Release 8.0(x) or Release 9.1(x) VM nodes using the same IP address, hostname, and security passwords.

Direct-to-Release 9.x upgrade

1) Apply phone firmware that corresponds with Release 9.x

You can apply new firmware files to the cluster in a controlled manner prior to the upgrade to minimize phone downtime after an upgrade. Applying firmware ahead of the upgrade prevents phones from upgrading their firmware at the same time following completion of the upgrade. This step is not required because the phones download their new firmware after an upgrade. However, an administrator using this step may apply new firmware to phones in groups to eliminate the load on the TFTP server after the upgrade to accelerate the upgrade of the individual devices.

The document System Installation and Upgrade Manual for IP Telephony, Cisco Unified Communications System Release 9.1(1) summarizes the phone firmware version that ships with Cisco Unified Communications Manager Release 9.1(1).

2) Verify all licenses and all unapplied PAKs

Important:

Apply all unclaimed or uninstalled license files now.

Following an upgrade to Release 9.x, only the valid installed licenses are migrated into the Enterprise License Manager. If you have unclaimed PAK codes, you cannot upload or automatically migrate those licenses into Release 9.x after the upgrade is complete. You must contact the Cisco licensing team for assistance (licensing@cisco.com).

Also, ensure that all installed licenses are valid and that the system is not operating on “demo” licenses, as this could affect your ability to upgrade.

Check the licensing status in the Cisco Unified Communications Manager Administration interface by selecting System>Licensing> License Usage Report. If any of the following are listed as “invalid” or “demo,” they must be fixed prior to upgrading:

  • Phone Licensing Feature
  • CCM Node Licensing Feature
  • Software Licensing Version

3) Perform a DRS backup of the entire cluster

Cisco strongly recommends that you back up the current cluster immediately prior to upgrading. Although the steps that are detailed in this document will ensure a successful upgrade, a backup allows you to restore the entire cluster to the last known good configuration in the event the upgrade fails as a result of a network or power failure.

Follow the “Starting a Manual Backup” procedure of the appropriate release of the Disaster Recovery System Administration Guide. Include all nodes in the cluster and all features in the backup. Do not proceed until the manual backup process is complete on all the nodes in the cluster.

4) Install refresh upgrade Cisco Options Package (COP) file


Note


This step does not apply if you are upgrading from an Release 8.6(x) release.


Before you upgrade from a compatible release of Cisco Unified Communications Manager, install the COP file named ciscocm.refresh_upgrade_v1.1.cop.sgn that you can find in the Download Software Center for Cisco Unified Communications Manager Utilities and COP Files section on Cisco.com (login required).

You must install the COP file on every node in the cluster prior to upgrading to Release 9.1(1) or later.

5) Upgrade to Release 9.1(1)

Follow the upgrade steps in the Upgrade tasks section of Upgrade Guide for Cisco Unified Communications Manager Release 9.1(1) to complete the software upgrade. The publisher must be upgraded to completion first, followed by the subscribers.

Follow the upgrade steps in the Upgrade tasks section of Upgrade Guide for Cisco Unified Communications Manager Release 9.1(1) to complete the software upgrade. The publisher must be upgraded to completion first, followed by the subscribers.

6) Perform a DRS backup of the entire cluster

Follow the steps in the “Starting a Manual Backup” procedure in the appropriate release of the Disaster Recovery System Administration Guide. Back up all nodes in the cluster and all features. Do not proceed until the manual backup process is complete on all the nodes in the cluster.

After the DRS backup is complete, shut down the existing cluster to avoid any conflict with the virtual installation of the cluster.

7) Create new virtual machines with Release 9.0 OVAs

Choose the appropriate OVA for the deployment from the OVA Template Details for Unified CM Release 9.0 docwiki page:

http:/​/​docwiki.cisco.com/​wiki/​

While it is not required, Cisco recommends that you deploy the same OVA throughout your entire cluster.

There are two different releases of OVA files available on Cisco.com. Version 7 OVAs (vm7) are for installing in an ESXi 4.X environment, while version 8 OVAs (vm8) are for installing in ESXi 5.X environments. Choose the correct OVA release based on the vCenter environment in which the virtualized UC applications will be deployed.

8) Install Release 9.1(1) using the same hostnames and IP addresses as the physical cluster

When installing Cisco Unified Communications Manager Release 9.1(1) into the virtual machines, you must ensure that the IP address, hostname, and security password are exactly the same as the cluster you are replacing. Additionally, the virtual installation of Cisco Unified Communications Manager must be the exact same release as that of the cluster that you are replacing. If any of these components differ from the existing cluster, you will not be able to restore the cluster.

The Release 9.1(1) cluster is installed as a new cluster with all subscriber nodes completing installation prior to restoring the data. After you install the publisher, add each subscriber to the server list to allow the subscriber servers to install correctly. Add the subscriber servers under System > Server on the publisher server.

9) Restore DRS backup on the entire cluster

After you install the publisher and all subscriber/utility nodes with the exact same release, hostnames, IP addresses, and DNS configuration as the physical servers, you can restore the cluster.

Before you restore the cluster, re-create the Backup Device. You must use the same Backup Device settings that were used to back up the physical servers. After you add the Backup Device, follow the “Restore Entire Cluster” procedure in the Cisco Unified Communications Manager Disaster Recovery System.


Note


Pay close attention to the reboot order of the servers after the restore completes. All subscribers must be rebooted before the publisher is rebooted.


10) Verify database replication and consistency

Although the DRS restore process reestablishes database replication, the administrator should, following a reboot of the cluster, verify that replication has indeed been restored.

Use one of the procedures in the Database Replication Error in Cisco Unified Communications Manager to verify replication status. Using RTMT, CLI, or Cisco Unified Reporting tools provides the same cluster-wide database replication status. If a problem is detected, follow the CLI instructions in the “Solution” section of the same document.

11) Migrate previous licenses into Enterprise License Manager

After you verify the DRS restore process and database replication, the previously installed licenses are ready for migration.

  1. Log in to the Enterprise License Manager web interface.
  2. Add all product instances that need to have licensing migrated. Refer to “Add product instance” in the Enterprise License Manager User Guide.

    Note


    For the purpose of this procedure, the first Cisco Unified Communications Manager cluster upgraded to Release 9.0 will be migrated. Additional clusters can be migrated in a similar fashion, but that is not covered here.


  3. After you add all products, follow the “Migrate licenses using Upgrade Licenses Wizard” procedure the Enterprise License Manager User Guide to create the licensing request string that is used in the License Migration Portal on Cisco.com.
  4. Browse to the license migration portal at: http:/​/​www.cisco.com/​go/​license/​migration
  5. Expand Voice Products and select Cisco Unified Communications Release 9.0.
  6. Either use copy and paste or upload files to populate the content for the license migration.
  7. Check the Terms of the License box and fill in an email address to send the license.
  8. After you receive the license, follow the “Install license” procedure to complete the migration of DLU-based licenses into Enterprise License Manager.

Virtualize at Release 8.0 upgrade

1) Verify all licenses and all unapplied PAKs

Important:

Apply all unclaimed/uninstalled license files now.

After an upgrade to Release 9.0, only the valid installed licenses are migrated into the Enterprise License Manager. If you have unclaimed PAK codes, you cannot upload or automatically migrate those licenses into Release 9.0 after the upgrade is complete. Contact the Cisco licensing team for assistance (licensing@cisco.com).

Also, make sure that all installed licenses are valid and that the system is not operating on “demo” licenses, as this could affect your ability to upgrade.

Check the licensing status in the Cisco Unified Communications Manager Administration interface by selecting System>Licensing> License Usage Report. If any of the following are listed as “invalid” or “demo,” they must be fixed prior to upgrading:

  • Phone Licensing Feature
  • CCM Node Licensing Feature
  • Software Licensing Version

2) Perform a DRS backup of the entire cluster

Cisco strongly recommends that you back up the current cluster immeditately prior to upgrading. Although the steps detailed in this document will ensure a successful upgrade, in the event of a failed upgrade due to a network or power failure, a backup enables you to restore the entire cluster to the last known good configuration.

Follow the “Starting a Manual Backup” procedure in the appropriate release of the Disaster Recovery System Administration Guide. Include all nodes in the cluster and all features in the backup. Do not proceed until the manual backup process is complete on all the nodes in the cluster.

3) Upgrade the cluster to Release 8.0(3a)


Note


MCS servers running Release 7.1(4) or 7.1(5) cannot upgrade to Release 8.0(3) because both releases were released after Release 8.0(3). If the current installed release matches either of these releases, use Release 8.5(1)SU5 as the intermediate upgrade step. The rest of the instructions are still applicable, but a different release will be referenced.


For all releases of Cisco Unified Communications Manager, perform the upgrade steps found in the “Upgrading to Cisco Unified Communications Manager 8.0(3)” (8.0(3a)SU3) section in the Release Notes for Cisco Unified Communications Manager 8.0(3).

For Cisco Unified Communications Manager 7.1(4) and 7.1(5), perform the upgrade steps found in the “Upgrading to Cisco Unified Communications Manager 8.5(1)” (8.5(1)SU5) section in the Release Notes for Cisco Unified Communications Manager Release 8.5(1).

4) Perform a cluster-wide DRS

Cisco strongly recommends that you back up the current cluster immediately prior to upgrading. Although the steps that are detailed in this document will result in a successful upgrade, in case of a failed upgrade due to a network or power failure, a backup allows you to restore the cluster back to the last known good configuration.

Follow the “Starting a Manual Backup” procedure in the appropriate release of the Disaster Recovery System Administration Guide. Back up all nodes in the cluster and all features. Do not proceed until the manual backup process is complete on all the nodes in the cluster.

5) Power off all servers in the cluster

Now that there is a backup of the existing cluster in Release 8.X, shut it down to avoid any conflict with the new cluster that will be created. This will involve downtime.

6) Create new Virtual Machines with Release 9.0 OVAs

Even though the Cisco Unified Communications Manager that you will install in the next step is Release 8.0 or Release 8.5, you must use the OVA for the final Cisco Unified Communications Manager release. In this case, the target release is Cisco Unified Communications Manager is Release 9.0, so you must use the Release 9.0 OVA for the Release 8.0 or Release 8.5 virtual installation.

Choose the appropriate OVA for the deployment from the OVA Template Details for Unified CM Release 9.0 docwiki page:

http:/​/​docwiki.cisco.com/​wiki/​

There are two different releases of OVA files available on Cisco.com. Version 7 OVAs are for installing in an ESXi 4.X environment, while version 8 OVAs are for installing in ESXi 5.X environments. Choose the correct OVA release based on the environment in which you are deploying your virtualized UC applications.

While it is not required, Cisco recommends that you deploy the same OVA throughout your entire cluster. Also, do not attempt to update the VMtools on the VMs after installing Release 8.0 or 8.5.

7) Install Release 8.X Using the same hostnames and IP addresses as the physical cluster

When installing Cisco Unified Communications Manager Release 8.0(3a) or 8.5(1) into the Virtual Machines, you must ensure that the IP address, hostname, and security password are exactly the same as the cluster that you are replacing. Additionally, the virtual installation of Cisco Unified Communications Manager must be the exact same release as that of the cluster that you are replacing. If any of these components differ from the existing cluster, you will not be able to restore the cluster.

Install the Release 8.0 or 8.5 cluster as a new cluster and ensure that all subscriber nodes complete the installation prior to restoring the data. After you install the publisher, add each subscriber to the server list to allow the server to correctly install. Add the subscriber servers under System > Server on the publisher server.

You can find more detailed installation instructions in the release-specific Installing Cisco Unified Communications Manager document.

8) Restore DRS backup on the entire cluster

After you install the publisher and all subscriber nodes with the exact same release, hostnames, IP addresses, and DNS configuration as the physical servers, you can restore the cluster.

After the installation is complete, re-create the Backup Device. Use the same Backup Device settings that were used on the physical servers.

After you add the Backup Device, follow the “Restore Entire Cluster” section of the Cisco Unified Communications Manager Disaster Recovery System document.


Note


Pay close attention to the reboot order of the servers after the restore completes. All subscribers must be rebooted before the publisher is rebooted.


9) Verify database replication and consistency

Although the DRS restore process reestablishes database replication, after rebooting the cluster, the administrator should verify that replication has indeed been restored.

Use one of the procedures in the Database Replication Error in Cisco Unified Communications Manager document to verify replication status. Using RTMT, CLI, or Cisco Unified Reporting tools provides the same cluster-wide database replication status. If a problem is detected, follow the CLI instructions in the “Solution” section of the same document.

10) Rehost the license files for the new licensing MAC on the VM and verify licensing

After you restore the cluster, you must rehost the existing license files to the current virtual deployment. The Cisco Unified Communications Manager licenses rehosting process is on the Cisco Software Licensing Portal:

https:/​/​tools.cisco.com/​SWIFT/​LicensingUI/​Home

For step-by-step instructions on how to rehost license files for Cisco UC products, see the “Rehost and RMA” section of the Cisco Software Licensing Portal Changes Quick Reference Guide.

11) Perform a cluster-wide DRS backup

Cisco strongly recommends that you back up the current cluster immediately prior to upgrading. Although the steps that are detailed in this document will ensure a successful upgrade, a backup allows you to restore the cluster to the last known configuration in the event of a failed upgrade due to a network or power failure.

Follow the “Starting a Manual Backup” procedure in the appropriate release of the Disaster Recovery System Administration Guide. Back up all nodes in the cluster and all features. Do not proceed until the manual backup process is complete on all the nodes in the cluster.

12) Install Refresh Upgrade COP file

Before you upgrade from a compatible release of Cisco Unified Communications Manager, install the COP file named ciscocm.refresh_upgrade_v1.1.cop.sgn found in the Download Software Center for Cisco Unified Communications Manager Utilities and COP Files section on Cisco.com (login required).

You must install the COP file on every node in the cluster prior to upgrading to Release 9.1(1) or later.

13) Upgrade to Release 9.1(1)

Follow the upgrade steps in the “Upgrade tasks” section of the “Software Upgrades” chapter in Upgrade Guide for Cisco Unified Communications Manager Release 9.1(1) to complete the software upgrade. First upgrade the publisher to completion, followed by the subscribers.

If the installation occurs during a maintenance window, Cisco recommends disabling I/O throttling to accelerate the upgrade process.

For information on how to disable I/O throttling, follow the instructions in the “Reference” section of the Upgrade Guide for Cisco Unified Communications Manager Release 9.1(1). This option is not available in all releases; check your server CLI to verify. If it is not available, you can still continue the upgrade procedure.

14) Verify database replication and consistency

Although the DRS restore process reestablishes database replication, the administrator should verify that replication has indeed been restored following a reboot of the cluster.

To verify replication status, use one of the procedures in the Database Replication Error in Cisco Unified Communications Manager. Using RTMT, CLI, or Cisco Unified Reporting tools provides the same cluster-wide database replication status. If a problem is detected, follow the CLI instructions in the “Solution” section of the same document.

15) Migrate previous licenses into Enterprise License Manager

After you verify the DRS restore process and database replication, the previously installed licenses are ready for migration.

  1. Log in to the Enterprise License Manager web interface.
  2. Add all product instances that need to have licensing migrated. Refer to “Add product instance” in the Enterprise License Manager User Guide.

    Note


    For the purpose of this procedure, the first Cisco Unified Communications Manager cluster upgraded to Release 9.0 will be migrated. Additional clusters can be migrated in a similar fashion, but that is not covered here.


  3. After you add all products, follow the “Migrate licenses using Upgrade Licenses Wizard” procedure the Enterprise License Manager User Guide to create the licensing request string that is used in the License Migration Portal on Cisco.com.
  4. Browse to the license migration portal at: http:/​/​www.cisco.com/​go/​license/​migration
  5. Expand Voice Products and select Cisco Unified Communications Release 9.0.
  6. Either use copy and paste or upload files to populate the content for the license migration.
  7. Check the Terms of the License box and fill in an email address to send the license to.
  8. After you receive the license, follow the “Install license” direction to complete the migration of DLU-based licenses into Enterprise License Manager.

Release 8.0 to 8.5 MCS to Release 9.1(1) virtual upgrade

If the MCS servers are running a Cisco Unified Communications Manager release from 8.0(2) to 8.5(1), the cluster can continue to run the current release while migrating to a virtual environment on the same release. This migration path follows the “Virtualize at Release 8.0 Upgrade Path,” but instead of migrating all physical servers to virtual servers at one time, this path migrates one server at a time from physical to virtual. By migrating one server at a time, the cluster can provide call processing services during the migration process.

  1. Follow the instructions for “Replacing a Single Server or Cluster” in the Replacing a Single Server or Cluster for Cisco Unified Communications Manager Release 8.0(2) document to replace each node of the existing cluster. Replace one server at a time.
  2. After you migrate all physical servers to virtual servers, apply the correct firmware for the Release 9.x release as described in Step 1 of the “Direct to Release 9.0 Upgrade Path” section.
  3. After the firmware has been deployed, follow Steps 11 to 15 of the “Virtualize at Release 8.0 Upgrade Path” section.