Upgrade Guide for Cisco Unified Communications Manager, Release 10.0(1)
Upgrade Tasks
Downloads: This chapterpdf (PDF - 1.28MB) The complete bookPDF (PDF - 2.61MB) | The complete bookePub (ePub - 270.0KB) | Feedback

Upgrade Tasks

Upgrade Tasks

This section contains the procedures for performing an upgrade.

Before You Begin

  • Review the pre-installation tasks and ensure that you have performed all the steps.

  • Stop all configuration tasks. Do not make any configuration changes during an upgrade. Any configuration changes that you make during an upgrade may be lost, and some configuration changes can cause the upgrade to fail.

  • Do not rename the upgrade file before you install it because the system will not recognize it as a valid file.
  • Do not decompress the file. If you do, the system may not be able to read the upgrade file.
  • For upgrades to the IM and Presence Service software, check that the contact list size for users has not reached the maximum value. The System Troubleshooter in Cisco Unified CM IM and Presence Administration indicates if there are users who have reached the contact list limit.


Caution


During a refresh upgrade, traffic is no longer processed and several reboots are required, therefore, you must perform a refresh upgrade during a maintenance window.


Upgrade Procedures

You can access the upgrade file during the installation process from either a local CD or DVD or from a remote FTP or SFTP server. Be aware that directory names and filenames that you enter to access the upgrade file are case-sensitive.


Note


If you cancel an upgrade at any stage, or if an upgrade fails, you must reboot the server before you attempt another upgrade.


Upgrade From a Local Source

Follow this procedure to upgrade to a new release of Unified Communications Manager or theIM and Presence Service using a CD or DVD in a local disk drive.

Procedure
    Step 1   Ensure that you can access the upgrade file. Choose one of the following options:
    • Insert the CD or DVD into the disc drive on the local server that is to be upgraded.
    • Create a data store ISO file on the local ESXi host.
    • Create a data store ISO file on a storage area network (SAN) that is connected to the ESXi host.
    Step 2   Log in to the management software for the node that you are upgrading:
    • If you are upgrading an IM and Presence node, log in to Cisco Unified IM and Presence Operating System Administration.
    • If you are upgrading a Unified Communications Manager node, log in to Cisco Unified Communications Operating System Administration.
    Step 3   If you are performing a refresh upgrade that requires a COP file, install the required COP file.

    If you are unsure whether you need to install a COP file, review the information about supported upgrade paths. See the Related Topics section below for more information.

    Step 4   Select Software Upgrades > Install/Upgrade.
    Step 5   Select DVD/CD from the Source list, or edit the virtual machine to map to the ISO file.
    Step 6   In the Directory field, enter the path to the location of the patch file. If the file is in the root directory, enter a slash (/).
    Step 7   Enter your email address and IP address in the Email Notification and SMTP Server fields. This will enable you to receive an email notification upon successful completion of the upgrade.
    Note   

    These fields are only visible for refresh upgrades.

    Step 8   Select Next to continue the upgrade process.
    Step 9   Select the upgrade version that you want to install and select Next.
    Step 10   Monitor the progress of the download, which includes the filename and the number of megabytes that are being transferred.
    Step 11   When the download completes, verify the checksum value against the checksum for the file that you downloaded from Cisco.com.
    Step 12   Perform one of the following actions:

    For standard upgrades:

    • If this is a single-node deployment and you want to install the upgrade and automatically reboot to the upgraded software, select Reboot to upgraded partition.

    • If this is a multinode deployment, select Do not reboot after upgrade. This allows you to install the upgrade and then manually reboot to the upgraded software at a later time. For more information about how to manually reboot the system and activate the upgrade, see the Related Topics section below.

    For refresh upgrades:

    • Select Do not switch to new version after upgrade only if you are performing a staged upgrade.

    • Select Switch to new version after upgrade to remain on the new active software version.

    Note   

    See the the Related Topics section below for more information about the rules for switching during an upgrade.

    Step 13   Select Next and select Finish when the installation completes.

    Upgrade From a Remote Source

    Follow this procedure to upgrade to a new release of Cisco Unified Communications Manager or the IM and Presence Service using software from a network drive or remote node. The network drive or remote node must be running a SFTP/FTP server that can be accessed by each node that you want to upgrade.

    Procedure
      Step 1   Log in to the management software for the node that you are upgrading:
      • If you are upgrading an IM and Presence node, log in to Cisco Unified IM and Presence Operating System Administration.
      • If you are upgrading a Unified Communications Manager node, log in to Cisco Unified Communications Operating System Administration.
      Step 2   If you are performing a refresh upgrade that requires a COP file, install the required COP file.

      If you are unsure whether you need to install a COP file, review the information about supported upgrade paths. See the Related Topics section below for more information.

      Step 3   Select Software Upgrades > Install/Upgrade.
      Step 4   Select Remote Filesystem from the Source list.
      Step 5   In the Directory field, enter the path to the patch file on the remote system.
      Step 6   In the Server field, enter the FTP or SFTP server name.
      Step 7   In the User Name field, enter the user name for the remote node.
      Step 8   In the User Password field, enter the password for the remote node.
      Step 9   Enter your email address and IP address in the Email Notification and SMTP Server fields. This will enable you to receive an email notification upon successful completion of the upgrade.
      Note   

      These fields are only visible for refresh upgrades.

      Step 10   From the Transfer Protocol field, select the transfer protocol, for example, SFTP.
      Step 11   Select Next to continue the upgrade process.
      Step 12   Select the upgrade version that you want to install and select Next.
      Step 13   Monitor the progress of the download, which includes the filename and the number of megabytes that are being transferred.
      Step 14   When the download completes, verify the checksum value against the checksum for the file that you downloaded from Cisco.com.
      Step 15   Perform one of the following actions:

      For standard upgrades:

      • If this is a single-node deployment and you want to install the upgrade and automatically reboot to the upgraded software, select Reboot to upgraded partition.

      • If this is a multinode deployment, select Do not reboot after upgrade.This allows you to install the upgrade and then manually reboot to the upgraded software at a later time. For more information about how to manually reboot the system and activate the upgrade, see the Related Topics section below.

      For refresh upgrades:

      • Select Do not switch to new version after upgrade only if you are performing a staged upgrade.

      • Select Switch to new version after upgrade to remain on the new active software version.

      Note   

      See the topic called Version switching during upgrade rules for more information about the rules for switching during an upgrade.

      Step 16   Select Next and select Finish when the installation completes.

      Version Switching

      A number of rules apply when you are manually switching versions and when you switch versions during an upgrade. The table below outlines the version switching rules for activating the release 10.x software version and for switching back to a previous software version.


      Note


      You cannot switch the version of any node if doing so violates the version matching requirements. This rule applies whether you are switching forward to a new software version, or switching back to a previous software version.

      Product

      Node type

      Switch from

      Switch to

      Switching rule

      Activate the new software version

      Unified Communications Manager

      Publisher

      8.x or 9.x

      10.x

      You must switch the software version on the publisher node before you switch the software version on subscriber nodes.

      10.x

      10.y

      Unified Communications Manager

      Subscriber

      8.x or 9.x

      10.x

      Supported when the publisher node has been switched to the new version. The software version you are switching to must match the version number of the active partition on the Unified Communications Manager publisher node.

      10.x

      10.y

      IM and Presence Service

      Database publisher

      8.x or 9.x

      10.x

      Supported when the software version you are switching to matches the major and minor version number of active partition on the Unified Communications Manager publisher node.

      10.x

      10.y

      IM and Presence Service

      Subscriber

      8.x or 9.x

      10.x

      Supported when the software version of this node matches the five version numbers of the IM and Presence database publisher node.

      10.x

      10.y

      Switch back to a previous software version

      Unified Communications Manager

      Publisher

      10.x

      8.x or 9.x

      Supported. You must switch the software version on the publisher node before you switch the software version on subscriber nodes.

      10.y

      10.x

      Unified Communications Manager

      Subscriber

      10.x

      8.x or 9.x

      Supported when the CUCM publisher node has been switched to the previous version. The software version you are switching to must match the version number of the active partition on the Unified Communications Manager publisher node. You cannot switch a subscriber node to a previous version when the publisher node is running new version.

      10.y

      10.x

      IM and Presence Service

      Database publisher

      10.x

      8.x or 9.x

      Not supported when the Unified Communications Manager publisher node is running a software version that is newer than the one that you are switching back to. Switching the IM and Presence database publisher node to a previous release after the Unified Communications Manager has been upgraded to a newer release violates the version matching requirements.

      Switching back to a previous release is supported only when the software version you are switching to matches the major and minor version number of active partition on the Unified Communications Manager publisher node.

      10.y

      10.x

      IM and Presence Service

      Subscriber

      10.x

      8.x or 9.x

      Not supported when the IM and Presence database publisher node is running a software version that is newer than the one that you are switching back to.

      Switching back to a previous release is supported only when the software version of this node matches the five version numbers of the IM and Presence database publisher node.

      10.y

      10.x

      Switch Software Version

      When you perform a standard upgrade, the new software is installed as an inactive version. You can reboot to the new software during the upgrade process or you can switch to the new version later.

      When you switch versions, the system restarts, and the inactive software becomes active. The system restart may take up to 15 minutes. When you perform this procedure both the active and inactive software versions are indicated.


      Caution


      This procedure causes the system to restart and become temporarily out of service.


      Before You Begin

      The software versions on Cisco Unified Communications Manager and IM and Presence nodes must match according to the manual switching rules. Therefore, you must switch Unified Communications Manager before you switch IM and Presence.

      Procedure
        Step 1   If you switch versions in a multinode deployment, you must switch the publisher node first.
        Step 2   Log in to the management software for the node that you are upgrading:
        • If you are upgrading an IM and Presence node, log in to Cisco Unified IM and Presence Operating System Administration.
        • If you are upgrading a Unified Communications Manager node, log in to Cisco Unified Communications Operating System Administration.
        Step 3   Select Settings > Version.

        It may take some time for all the services on the IM and Presence nodes to move to the Started state. Select Cisco Unified CM IM and Presence Administration > System > Cluster Topology and select a node from the tree view to monitor the status of the services on the node.

        Step 4   Verify the version of the active software and the inactive software.
        Step 5   Select Switch Versions to switch versions and restart the system.

        After you perform a switch version when you upgrade Unified Communications Manager, IP phones request a new configuration file. This request results in an automatic upgrade to the device firmware.

        Switch to Previous Version

        If you need to revert to the software version that was running before the upgrade, you can do so by using the Switch Version option to switch the system to the software version on the inactive partition.

        Switch Cluster to Previous Version

        To switch a cluster back to a previous version, complete these high-level tasks:

        Procedure
          Step 1   Switch back the publisher node.
          Step 2   Switch back all backup subscriber nodes.
          Step 3   Switch back all primary subscriber nodes.
          Step 4   If you are reverting to an older product release, reset database replication within the cluster.

          Switch Node to Previous Version

          Procedure
            Step 1   Log in to the management software for the node that you are upgrading:
            • If you are upgrading an IM and Presence node, log in to Cisco Unified IM and Presence Operating System Administration.
            • If you are upgrading a Unified Communications Manager node, log in to Cisco Unified Communications Operating System Administration.
            Step 2   Choose Settings > Version.

            The Version Settings window displays.

            Step 3   Click the Switch Versions button.

            After you verify that you want to restart the system, the system restarts, which might take up to 15 minutes.

            Step 4   To verify that the version switch was successful, follow these steps:
            1. Log in again to the management software for the node that you are upgrading.
            2. Choose Settings > Version.

              The Version Settings window displays.

            3. Verify that the correct product version is now running on the active partition.
            4. Verify that all activated services are running.
            5. For the publisher node, log in to Cisco Unified CM Administration.
            6. Verify that you can log in and that your configuration data exists.

            Reset Database Replication

            If you switch back the servers in a cluster to run an older product release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the older product release, enter the CLI command utils dbreplication reset all on the publisher server.

            When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message that reminds you about the requirement to reset database replication if you are reverting to an older product release.

            Switch version back to Cisco Unified Presence 8.6(3) or earlier

            Cisco Unified Presence releases 8.6(4) and later do not support the Cisco Presence Engine database. If you upgrade from Release 8.6(3) or earlier and you subsequently want to revert to the previous release, you must install a COP file that will reinstall the Cisco Presence Engine database. The COP filename is ciscocm.cup.pe_db_install.cop and you can download it from Cisco.com.


            Note


            In a multinode environment, you must install the COP file on every node in the cluster after you switch versions from Cisco Unified Presence Release 8.6(4) or later.


            In this release, you cannot downgrade to a version earlier than Release 8.6(3).


            Note


            You must restart the system after you install the COP file.


            Before you begin

            Switch versions on Cisco Unified Communications Manager.

            Procedure
              Step 1   Download the following COP file from Cisco.com: ciscocm.cup.pe_db_install.cop.
              Step 2   Sign in to Cisco Unified IM and Presence Operating System Administration.
              Step 3   Select Settings > Version.
              Step 4   Verify the version of the active and inactive software.
              Note   

              This procedure only applies if you want to switch from Release 9.0 or later back to a release earlier than 8.6(4).

              Step 5   Select Switch Versions to switch back to the earlier release and restart the system.
              Step 6   After the system has restarted, install the COP file.
              Note   

              In a multinode environment, you must install the COP file on every node in the cluster.

              Step 7   After you have installed the COP file, manually restart the system. To do this, select Settings > Version and select Restart.
              Step 8   Run the following CLI command (on the publisher or subscriber node) to check if the database replication is active on the node: utils dbreplication runtimestate

              If database replication is active on all nodes, the output lists all the nodes and the replication setup value for each node is 2. If database replication is not complete (a value other than 2 is returned), core services will not start on the subscriber node until replication is complete.

              Step 9   Select Cisco Unified CM IM and Presence Administration > System > Notifications to determine whether database replication is complete.
              Step 10   If database replication cannot be established, use the following CLI command on the publisher node to reset replication: utils dbreplication reset all