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 |
Run the pre-upgrade COP. It runs a series of tests and detects issues that can cause upgrade failures. Install the pre-upgrade COP file to check the upgrade readiness from the current version to the version you are upgrading to, and if you find any issues in the report, fix them before upgrading. This reduces the chances of an upgrade failure. |
||||
Step 4 |
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 5 |
Export user records using the Bulk Administration Tool (BAT):
|
||||
Step 6 |
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:
|
||||
Step 7 |
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 8 |
Ensure that you have the necessary license files for the new release. |
||||
Step 9 |
Ensure that there are no expired certificates on the partition, including any trust certificates in the certificate chain. Perform this step for refresh upgrades on IM and Presence Service nodes only. Expired certificates are not imported during a refresh upgrade. As a result, a new certificate is generated during upgrade process and can cause errors. |
||||
Step 10 |
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 Administration Guide for Cisco Unified Communications Manager |
||||
Step 11 |
If you are upgrading from Release 9.x or earlier, you must disable extension mobility before you begin the upgrade process.
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. |
||||
Step 12 |
Perform these additional tasks when you upgrade Cisco Unified Communications Manager:
|
||||
Step 13 |
Perform these additional tasks when you upgrade the IM and Presence Service: |
||||
Step 14 |
Add a serial port to the virtual machine so that you can dump logs in the event of an upgrade failure.
After you successfully upgrade the system, follow the procedure to Remove the Serial Port. In the event of an upgrade failure, refer to Dump a Log File After an Upgrade Failure. |