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

Pre-Upgrade Tasks

Pre-Upgrade Tasks

Perform Pre-Upgrade Tasks

Before you begin the upgrade, perform the following tasks:

Procedure
    Step 1   Read the release notes for the new release and be sure that you understand the new features and how the upgrade interacts with the other products that are associated with your system.
    Step 2   Familiarize yourself with the requirements and limitations listed in this document. Ensure that your system meets all requirements, including network requirements, platform requirements, and software requirements.
    Step 3   Ensure that the software version you are upgrading from is running on a virtual machine. If your current deployment is running on MCS hardware, see the Cisco Prime Collaboration Deployment Administration Guide for information about how to migrate an existing cluster to a virtualized cluster.
    Step 4   Use the Real-Time Monitoring Tool (RTMT) to verify that you have enough common partition space for the upgrade. Typically, you need at least 25G of common partition space; however, your deployment may require more space if you have a lot of TFTP data (device firmware loads), music-on-hold (MOH) files, or if you have many locale files installed. If you do not have enough space, perform one or more of the following steps to create enough space:
    • Use the Cisco Log Partition Monitoring Tool to adjust the low and high watermarks to reduce the traces and remove unnecessary log files. Cisco recommends that you adjust the low watermark value to 30, and the high watermark value to 40. After the upgrade, you must restore the high and low watermarks to their original values in order to avoid premature purging of traces. The default value for the high watermark is 85. The default value for the low watermark is 80. For more information about using the Cisco Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.
    • Use the Disk Expansion COP file (ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn) to expand the vDisk size if your virtual environment has additional available disk space. Ensure that you review the Readme file that supports this COP file before you proceed.
    • Use the Free Common Space COP file (ciscocm.free_common_space_v<latest_version>.cop.sgn). This COP file removes the inactive side in the common partition to increase available disk space without requiring a system rebuild. Ensure that you review the Readme file that supports this COP file before you proceed.
    • Manually remove outdated or unused firmware files from the TFTP directory. You can remove these files using the TFTP File Management page in the OS Administration interface, or you can use the file list tftp and file delete tftp commands from the command line interface.
    You can download COP files and their Readme files from Cisco.com. Navigate to Support > Downloads > Cisco Unified Communications Manager Version 10.0 > Unified Communications Manager/CallManager/Cisco Unity Connection Utilities.
    Caution    Performing an upgrade without sufficient disk space can cause the system to fail.
    Step 5   Download any upgrade COP files that are required. COP files are required for refresh upgrades only. To determine which COP files you need, see the information about COP files and supported upgrade paths listed in the Related Topics section below.
    Step 6   Ensure that you have the necessary license files for the new release.
    Step 7   Back up your system, ensuring that you use a network device as the storage location for the backup files. Virtualized deployments of Unified Communications Manager do not support the use of tape drives to store backup files.

    For more information, see the Disaster Recovery System Administration Guide.

    Step 8   Perform these additional tasks when you upgrade Cisco Unified Communications Manager:
    1. If you have special characters in your Cisco Unified Communications Manager default administrative password, when you upgrade from releases 8.x or 9.x, the connection between IM and Presence Service and Cisco Unified Communications Manager fails. Before you upgrade from an 8.x or 9.x release, you must change your password so that all special characters are removed.
    2. Use the utils dbreplication setrepltimeout CLI command to increase the database replication timeout value when upgrading large clusters so that more Cisco Unified Communications Manager subscriber nodes have sufficient time to request replication. When the timer expires, the first Cisco Unified Communications Manager subscriber node, plus all other Cisco Unified Communications Manager subscriber nodes that requested replication within that time period, begin a batch data replication with the Cisco Unified Communications Manager database publisher node. The default database replication timeout value is 300 (5 minutes). Restore the timeout to the default value after the entire cluster upgrades and the Cisco Unified Communications Manager subscriber nodes have successfully set up replication. For more information, see the Command Line Interface Guide for Cisco Unified Communications Solutions.
    3. Disable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability > Tools > Service Activation. For more information, see the Cisco Unified Serviceability Administration Guide.

      Note that when you deactivate the Cisco Extension Mobility service, Cisco Extension Mobility users cannot log in and log out of phones that support Cisco Extension Mobility.

    4. Ensure that the device name for the Cisco Unified Mobile Communicator device contains 15 or fewer characters. If the device name contains more than 15 characters for the Cisco Unified Mobile Communicator, the device does not migrate during the upgrade.
    5. Ensure that the IP subnet mask of the device is set using the following format:255.255.255.0. You can change the subnet mask by executing the set network ip eth0 <server_IP_address> 255.255.255.0 command.
    6. Before you upgrade a Cisco Unified Communications Manager cluster, execute the utils network ipv6 ping CLI command to verify IPv6 networking on the first node (Cisco Unified Communications Manager database publisher node) and Cisco Unified Communications Manager subscriber nodes. If IPv6 is configured incorrectly on the Cisco Unified Communications Manager subscriber nodes, load detection may take 20 minutes.
    7. Apply all pre-9.0 licenses to Cisco Unified Communications Manager before you upgrade to Release 9.0 or later software. After you upgrade to Release 9.0 or later software, you cannot apply these licenses to Cisco Unified Communications Manager and you cannot apply them using the Cisco Prime License Manager. Ensure that you install all unused licenses or Product Authorization Keys (PAKs) before you upgrade the system. The Cisco Unified Communications Manager displays a warning to prompt you to install any unused licenses before proceeding.
    Step 9   Perform these additional tasks when you upgrade the IM and Presence Service:
    1. Disable High Availability on the IM and Presence presence redundancy group. Select Cisco Unified CM Administration > System > Presence Redundancy Group.

      For more information, see the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager.

    2. If you have to upgrade Cisco Unified Communications Manager as part of your IM and Presence upgrade, you must stop and restart the IM and Presence Sync Agent service. To restart the Sync Agent service, navigate to Cisco Unified IM and Presence Serviceability and select Tools > Control Center - Network Services.
    3. Check that the IM and Presence Service node has connectivity with Cisco Unified Communications Manager.

      You can use the Cisco Unified CM IM and Presence Administration System Troubleshooter to check node connectivity.


    Change Virtual Machine Configuration Specifications

    Use the following procedure when you need to change the configuration specifications on your virtual machine (VM) in order to upgrade to a new release of Unified Communications Manager or IM and Presence Service. Configuration specifications include the vCPU, vRAM, and vDisk size. For information about VM requirements, see the Readme file with the OVA template that supports your release. Details about OVA templates are available on the Virtualization Docwiki at http://docwiki.cisco.com/wiki/Implementing_Virtualization_Deployments.

    Procedure
      Step 1   Perform a Disaster Recovery System (DRS) backup.

      For more information about performing a backup, see the Cisco Unified Communications Manager Disaster Recovery Administration Guide.

      Step 2   (Optional.) If you need to increase the vDisk space to meet the space requirements of a refresh upgrade, install the following COP file:

      ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn

      Step 3   Shut down the virtual machine.
      Step 4   Change the configuration of the virtual machine as needed:
      1. Change the Guest OS version to match the requirements of the new release (Red Hat Enterprise Linux 6 (64-bit).
      2. To change the vCPU, make the change in vSphere Client. Ensure that you change the reservation value to match the specifications of the new release.
      3. To change the vRAM, make the change in vSphere Client. Ensure that you change the reservation value to match the specifications of the new release.
      4. To increase the vDisk space, edit the disk size using vDisk. If the virtual machine has two disks, expand the second one.

        The new space is automatically added to the common partition when you restart the virtual machine.

        Note   

        You need to change the disk size changes only if you need additional space to complete the upgrade. The disk space requirements are specified in the Readme file for the OVA template.

        Expanding the disk size to add space to the common partition will not increase the user capacity of your system. If you need to extend the user capacity of your system, you must migrate from a single-disk to a multi-disk virtual machine; seeReplace a Single Server or Cluster for Cisco Unified Communications Manager for more information.

      For more information about making configuration changes using vSphere Client, refer to the user manual for the product.

      Step 5   Upgrade the software to the latest version.
      Step 6   Modify the Network Adapter to use the VMXNET 3 Adapter type.

      For information about modifying the Network Adapter to meet the requirements of this release, see the Readme file for the OVA template.

      Step 7   Power on the virtual machine.

      Upgrade vSphere ESXi

      Use the following procedure when you need to update your vSphere ESXi hypervisor in order to upgrade to a new release of Unified Communications Manager.

      Procedure
        Step 1   Move the virtual machine that is running Unified Communications Manager off the host server using one of the following methods:
        • If you have a hot standby host, use vMotion to migrate the virtual machine from one physical server to another.
        • If you do not have a hot standby host, power down the virtual machine and copy it to a different location.
        Step 2   Upgrade the vSphere ESXi using the upgrade procedures provided by VMware.
        Step 3   Verify that the vSphere ESXi upgraded successfully.
        Step 4   Move the virtual machine that is running Unified Communications Manager back to the host server using one of the following methods:
        • If you have a hot standby host, use vMotion to migrate the virtual machine from one physical server to another.
        • If you do not have a hot standby host, power down the virtual machine and copy it the host server.

        What to Do Next

        If you need to update the virtual machine version or the VMware compatibility version in order to upgrade the vSphere ESXi, proceed to Change Virtual Machine Configuration Specifications

        Obtain Upgrade File

        Before you begin the upgrade process, you must obtain the appropriate upgrade file from Cisco.com.

        For more information, see the Cisco Unified Communications Manager Release Notes.

        You can access the upgrade file during the installation process from either a local 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.