- Upgrade Planning
- Upgrade and Migration Overview
- Upgrade Methods
- Take Record of Your Current System
- Supported Upgrade and Migration Paths with COP Files
- Choose Your Upgrade Tool
- Requirements and Limitations
- Hardware Requirements
- Virtual Machine Configuration
- Deprecated Phone Models
- Network Requirements
- IP Address Requirements
- DNS requirements
- Firewall Requirements
- SFTP Server Support
- Subnet Limitations
- Cluster Size
- IP Subnet Mask
- Software Requirements
- Device Name for Cisco Unified Mobile Communicator
- Export Restricted and Export Unrestricted Software
- Upgrades from Unified CM 9.x
- OS Admin Account Required for CLI-Initiated IM and Presence Upgrades
- Upgrades from 11.5(1)SU2 with Push Notifications Enabled
- Database Migration Required for Upgrades with Microsoft SQL Server
- Upgrades from Release 11.5(1)SU5
- Upgrade Considerations for Upgrades from 12.0(1) to 12.5(1)
- Upgrade Considerations for Upgrades from 10.5(1) to 14
- Upgrade Considerations with FIPS Mode
- IPSec Requirements
- Support for Intercluster Peers
- Spectre/Meltdown Vulnerabilities During Upgrade
- Duplicate ENUMS Break Upgrades and Migrations from 10.5(2)
- Blue Screen Appears for Unified CM Refresh Upgrades
- Licensing Requirements
- Unified Communications Manager License Requirements
- Specific License Reservation
- IM and Presence Service License Requirements
- Hardware Requirements
Upgrade and Migration Overview
The procedures in this book describe how to upgrade Cisco Unified Communications Manager (Unified Communications Manager) and Cisco Unified Communications Manager IM and Presence Service (IM and Presence Service) from an earlier version to the current version.
Use the procedures in this book as a starting point for all upgrades and migration paths.
Upgrade Methods
The following table explains the types of upgrades that you can complete with Cisco Unified Communications Manager and the IM and Presence Service and the upgrade tools that you can use to complete the upgrade.
Upgrade Type | Description | Upgrade Tools | ||
---|---|---|---|---|
Direct Standard Upgrade | A standard upgrade is a direct upgrade where you need to upgrade the application software, but not the underlying operating system. This is usually the simplest form of upgrade and would typically apply to upgrades from within the same major-minor release category, where the OS is the same for both releases. For release 12.5 or higher, direct standard upgrades have substantially improved durations, simpler procedures and reduced service impact. Example: Upgrades from 12.5(1) to 12.5(1)SU1.
| The following tools are used to complete standard upgrades:
| ||
Direct Refresh Upgrade | A direct refresh upgrade is a direct upgrade where you need to upgrade both the application software and the underlying operating system software. This would typically be used if you're upgrading from one major-minor release to another where the OS is different for the two releases. Example: Upgrades from 11.5(1) to 14 | The following tools are used to complete refresh upgrades:
| ||
Direct migration | A direct migration involves a 'repave' where multiple factors exist that can't address with just a direct upgrade. Direct Migration is used in the following cases:
| The following tool is used to complete migrations:
| ||
Install with Data Import | A fresh installation with data import is an alternative to direct upgrades and direct migrations, from releases 10.5 and above, migrating to release 14. It involves the following:
If you want to roll back to the previous release, install ciscocm.DataExport_rollback_v1.0.cop.sgn COP file. | CLI is used to complete installation with data import | ||
Migration from legacy releases | A legacy release is a source release that is so old that the desired upgrade has no direct upgrade path and no direct migration path available to destination release 14. The only option is a direct upgrade to a later release that supports either PCD migration or Install with Data Import, followed by either a PCD migration or Fresh Install with Data Import to release14. Example: Any desired upgrade to 14 from a pre-6.1(5) Unified CM or a pre-8.5(4) Cisco Unified Presence. | For details, see Upgrading from Legacy Releases. |
Take Record of Your Current System
Before you begin the upgrading, take a record of the versioning within your current system setup. After you know the versions that your current system uses, you can begin planning your upgrade. This includes:
-
Pre-upgrade versions for Unified Communications Manager and the IM and Presence Service
-
Current Hardware version
-
VMware Versioning
Note
VMware was introduced as an optional deployment in Unified CM 8.x and 9.x. From Release 10.x forward, VMware became mandatory.
You can obtain versioning by running the Pre-upgrade Upgrade Readiness COP File. For details, see Run Upgrade Readiness COP File (Pre-upgrade).
Supported Upgrade and Migration Paths with COP Files
The following table highlights supported upgrade paths to upgrade to Release 14 of Cisco Unified Communications Manager and the IM and Presence Service. It also lists the upgrade paths that require COP files. You must install COP files on each node before you begin an upgrade using the Cisco Unified OS Admin interface, or before you begin an upgrade or migration using the Prime Collaboration Deployment (PCD) tool. If you are using PCD, you can perform a bulk installation of the COP files before you begin the upgrade.
![]() Note | |
You can download COP files for Cisco Unified Communications Manager and the IM and Presence Service at https://software.cisco.com/download/home/268439621. After you select the destination version for the upgrade, choose Unified Communications Manager Utilities to see the list of COP files.
![]() Note | |
![]() Note | ciscocm.ciscossl7_upgrade_CSCwa48315_CSCwa77974_v1.0.k4.cop . This document details the pre-requisites required for direct upgrade or direct migration to the 14SU2 destination versions. |
![]() Note | If the source is Release 14 or above and the upgrade path is direct standard, see the Clusterwide Upgrade Task Flow (Direct Standard) procedure that details Cluster Upgrade via Unified CM publisher using Unified OS Admin upgrade or CLI upgrade that will upgrade all cluster nodes in the Unified CM publisher node. If you are planning to upgrade your source node-by-node or using a single-node only using the local Unified OS Admin upgrade or CLI upgrade, see the Upgrade Cluster Nodes (Direct Refresh or Direct Standard) section. |
Source | Destination | Mechanism | Pre-requisites | Version Switching* (Source to Destination and Vice Versa) | |
---|---|---|---|---|---|
10.0 | 14 | PCD 14 Migration Task (V2V) | Direct upgrade to 14SU2 is not supported. When the destination version is 14 SU2 and the source version is 10.0, then the Cisco Prime Collaboration Deployment (PCD) must be used for migration. If the destination version is 14 SU2 and the source version 10.0 is in FIPS mode, then the Cisco Prime Collaboration Deployment (PCD) must be in (or placed in) non-FIPS mode. | Not supported | |
10.5 | 14 | PCD 14 Migration Task (V2V) | Run pre-upgrade-check COP file. Direct upgrade to 14SU2 is not supported. When the destination version is 14 SU2 and the source version is 10.5, then the Cisco Prime Collaboration Deployment (PCD) must be used for migration. If the destination version is 14 SU2 and the source version 10.5 is in FIPS mode, then either:
| Not supported | |
Fresh Install with Data Import (V2V) |
| Not supported | |||
11.0 | 14 | PCD 14 Migration Task (V2V) | Run pre-upgrade-check COP file. If the destination version is 14 SU2 and the source version 11.0 is in FIPS mode, then either:
| Not supported | |
Fresh Install with Data Import (V2V) |
| Not supported | |||
11.5 | 14 | Direct Refresh Upgrade | Via OS Admin or CLI |
| Supported |
Direct Refresh Upgrade | Via PCD Upgrade Task |
| Supported | ||
PCD 14 Migration Task (V2V) | Run pre-upgrade-check COP file. If the destination version is 14 SU2 and the source version 11.5 is in FIPS mode, then either:
| Not supported | |||
Fresh Install with Data Import (V2V) |
| Not supported | |||
12.0 | 14 | Direct Refresh Upgrade | Via OS Admin or CLI |
| Supported |
Direct Refresh Upgrade | Via PCD Upgrade Task |
| Supported | ||
PCD 14 Migration Task (V2V) | Run pre-upgrade-check COP file. If the source version is Release 12.0(1) of Unified Communications Manager (12.0.1.10000-10), then you must install the following COP file: ciscocm-slm-migration.k3.cop.sgn. This is not required if the source version is higher, for example, Release 12.0(1)SU1. | Not supported | |||
Fresh Install with Data Import (V2V) |
| Not supported | |||
12.5 | 14 | Direct Standard Upgrade (simple upgrades) | Via OS Admin or CLI |
| Supported |
Direct Standard Upgrade | Via PCD Upgrade Task |
| Supported | ||
PCD 14 Migration Task (V2V) | Run pre-upgrade-check COP file. If the destination version is 14 SU2 and the source version 12.5 is in FIPS mode, then either:
| Not supported | |||
Fresh Install with Data Import (V2V) |
| Not supported | |||
14 or 14SU1 | 14SU2 | Direct Standard Upgrade (simple upgrades) | Via OS Admin or CLI | Run pre-upgrade-check COP file. | Supported |
Direct Standard Upgrade | Via PCD Upgrade Task | Run pre-upgrade-check COP file.
|
* Version switching refers to the ability to install the new version as an inactive version and switch to the new version, and revert to the old version, whenever you want. This capability is supported with most direct upgrades, but not with migrations.
![]() Note | |
If you are planning network migration of Unified Communications Manager from Release 12.0(1) to any higher release, perform any one of the following:
-
Task 1—Deregister the system from Cisco Smart Software Manager before network migration to higher versions.
-
Task 2—After successful migration of the cluster, re-register the Unified Communications Manager to Cisco Smart Software Manager smart account.
For detailed information on these procedures, see the System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1).
Choose Your Upgrade Tool
Refer to the table below for information that can help you to decide which upgrade tool to use when there are multiple mechanisms available to choose from.
![]() Note | |
Upgrade Method | Support | When to use this method... | How to complete the Upgrade or Migration | ||
---|---|---|---|---|---|
Unified OS Admin or CLI upgrades | Direct upgrades (standard or refresh) via the Cisco Unified OS Administration GUI or CLI. | Consider this tool for:
| Go to Upgrade Tasks | ||
PCD Upgrades | Handles direct upgrades (standard or refresh) via Cisco Prime Collaboration Deployment's upgrade task. | Consider this tool when:
| From Release is 10.x or later
| ||
PCD Migrations | Handles migrations via Cisco Prime Collaboration Deployment. | Consider this tool when:
| |||
Fresh Install with Data Import | Handles migrations through exporting source release data to SFTP, and touchless installing a new 14 cluster with import of that data. | Consider this tool when:
|
|
Requirements and Limitations
The following sections describe requirements and limitations for upgrades to this release.
Hardware Requirements
You can install Unified Communications Manager and IM and Presence Service on a virtual server hosted on the following types of hardware. If your current deployment does not use one of these servers, then you must migrate to a supported hardware platform:
-
Cisco Business Edition 6000 or 7000 appliance
-
Virtualized Cisco hardware (such as Cisco UCS or Cisco HyperFlex) with VMware vSphere ESXi
-
Virtualized Third-party hardware with VMware vSphere ESXi
The requirements and support policies are different for each of these options. Before you begin an upgrade, verify that your current hardware meets the requirements of the new release. You can find detailed information about the requirements by going to https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/cisco-collaboration-virtualization.html and following the links for the Unified Communications Manager and IM and Presence Service applications.
Virtual Machine Configuration
Before you begin an upgrade or migration, verify that your current virtual machine (VM) software meets the requirements of the new release.
Item | Description | ||
---|---|---|---|
OVA templates | OVA files provide a set of predefined templates for virtual machine configuration. They cover items such as supported capacity levels and any required OS/VM/SAN alignment. You must use a VM configuration from the OVA file provided for the Unified Communications Manager and IM and Presence Service applications. The correct VM configuration to use from the OVA file is based on the size of the deployment. For information about OVA files, search for the topic "Unified Communications Virtualization Sizing Guidelines" at https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/collaboration-virtualization-sizing.html. | ||
VMware vSphere ESXi | You must install a version of vSphere ESXi hypervisor that meets the compatibility and support requirements for the release. If you use Cisco Prime Collaboration Deployment (PCD) to perform an upgrade or migration, you must also ensure that you install vSphere ESXi with the correct license type. PCD is not compatible with all the license types of vSphere ESXi because some of these licenses do not enable required VMware APIs. | ||
VMware vCenter | VMware vCenter is optional when you deploy Unified Communications Manager or IM and Presence Service on Business Edition 6000/7000 appliances, or on UC on UCS tested reference configuration hardware. VMware vCenter is mandatory when you deploy on UC on UCS specs-based and third-party server specs-based hardware. | ||
VM configuration virtual hardware specifications | Verify whether you need to change the virtual hardware specifications on your VM in order to upgrade to a new release of Unified Communications Manager or IM and Presence Service. For example, verify the requirements for vCPU, vRAM, vNIC adaptor type, and vDisk size, as well as other specifications. Any changes to a VM must align with the OVA configuration. VM changes that result in an unsupported OVA configuration are not allowed. For information about VM requirements, see Readme file with the OVA template that supports your release.
|
VMware Upgrade Requirements
If the upgrade requires you to update your VMware, go to Virtual Machine Configuration Tasks.
Deprecated Phone Models
The following table lists all the phone models that are deprecated for this release of Cisco Unified Communications Manager, along with the Unified CM release where the phone model first became deprecated. For example, a phone model that was first deprecated in Release 11.5(1) is deprecated for all later releases, including all 12.x releases.
If you are upgrading to the current release of Cisco Unified Communications Manager and you have any of these phone models deployed, the phone will not work after the upgrade.
Deprecated Phone Models for this Release | First Deprecated as of... |
---|---|
No additional endpoints deprecated | Release 14 |
| 12.0(1) and later releases |
| 11.5(1) and later releases |
For additional information, refer to Field Notices.
Upgrades that Involve Deprecated Phones
If you are using any of these phones on an earlier release and you want to upgrade to this release, do the following:
-
Confirm whether the phones in your network will be supported in this release.
-
Identify any non-supported phones.
-
For any non-supported phones, power down the phone and disconnect the phone from the network.
-
Provision a supported phone for the phone user. You can use the Migration FX tool to migrate from older model to newer model phones. For details, go to: https://www.unifiedfx.com/products/unifiedfx-migrationfx#endpoint_refresh_tool.
-
Once all the phones in your network are supported by this release, upgrade your system.
![]() Note | Deprecated phones can also be removed after the upgrade. When the administrator logs in to Unified Communications Manager after completing the upgrade, the system displays a warning message notifying the administrator of the deprecated phones. |
Licensing
You do not need to purchase a new device license to replace a deprecated phone with a supported phone. The device license becomes available for a new phone when you either remove the deprecated phone from the system, or when you switch to the new Unified Communications Manager version, and the deprecated phone fails to register.
Network Requirements
This section lists the requirements that your network must meet before you can deploy Unified Communications Manager and the IM and Presence Service.
IP Address Requirements
A complete collaboration solution relies on DNS in order to function correctly for a number of services and thus requires a highly available DNS structure in place. If you have a basic IP telephony deployment and do not want to use DNS, you can configure Unified Communications Manager and IM and Presence Service to use IP addresses rather than hostnames to communicate with gateways and endpoint devices.
You must configure the server to use static IP addressing to ensure that the server obtains a fixed IP address. Using a static IP address also ensures that Cisco Unified IP Phones can register with the application when you plug the phones into the network.
DNS requirements
Note the following requirements:
-
Mixed-mode DNS deployments not supported—Cisco does not support mixed-mode deployments. Both Unified Communications Manager and IM and Presence Service must either use or not use DNS.
-
If your deployment uses DNS—Unified Communications Manager and IM and Presence Service should use the same DNS server. If you use different DNS servers between IM and Presence Service and Unified Communications Manager, it is likely to cause abnormal system behavior.
-
If your deployment does not use DNS, you will need to edit the following Host Name/IP Address fields:
-
Server—In the Cisco Unified CM Administration Server Configuration window, set IP addresses for your cluster nodes.
-
IM and Presence UC Service—In the Cisco Unified CM Administration UC Service Configuration window, create an IM and Presence UC service that points to the IP address of the IM and Presence database publisher node.
-
CCMCIP Profiles—In the Cisco Unified CM IM and Presence Administration CCMCIP Profile Configuration window, point any CCMCIP profiles to the IP address of the host.
-
-
Multinode considerations—If you are using the multinode feature in IM and Presence Service, see the section regarding multinode deployments in the Configuration and Administration of the IM and Presence Service Guide for DNS configuration options.
Firewall Requirements
Ensure that you configure your firewall so that connections to port 22 are open, and aren't throttled. During the installation of Unified Communications Manager and IM and Presence subscriber nodes, multiple connections to the Unified Communications Manager publisher node are opened in quick succession. Throttling these connections could lead to a failed installation. For general security considerations, see the Security Guide for Cisco Unified Communications Manager.
![]() Note | |
For more information on the port usage, see the chapter 'Cisco Unified Communications Manager TCP and UDP Port Usage' in the System Configuration Guide for Cisco Unified Communications Manager.
SFTP Server Support
Use the information in the following table to determine which SFTP server solution to use in your system.
SFTP Server | Information | ||
---|---|---|---|
SFTP Server on Cisco Prime Collaboration Deployment | This server is the only SFTP server that is provided and tested by Cisco, and fully supported by Cisco TAC. Version compatibility depends on your version of Unified Communications Manager and Cisco Prime Collaboration Deployment. See the Cisco Prime Collaboration Deployment Administration Guide before you upgrade its version (SFTP) or Unified Communications Manager to ensure that the versions are compatible. | ||
SFTP Server from a Technology Partner | These servers are third party provided and third party tested. Version compatibility depends on the third party test. See the Technology Partner page if you upgrade their SFTP product and/or upgrade Unified Communications Manager for which versions are compatible: https://marketplace.cisco.com | ||
SFTP Server from another Third Party | These servers are third party provided and are not officially supported by Cisco TAC. Version compatibility is on a best effort basis to establish compatible SFTP versions and Unified Communications Manager versions.
|
Subnet Limitations
Do not install Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. For more information, see Cisco Collaboration System 12.x Solution Reference Network Designs (SRND).
Cluster Size
The number of Unified Communications Manager subscriber nodes in a cluster cannot exceed 4 subscriber nodes and 4 standby nodes, for a total of 8 subscribers. The total number of servers in a cluster, including the Unified Communications Manager publisher node, TFTP server, and media servers, cannot exceed 21.
The maximum number of IM and Presence Service nodes in a cluster is 6.
For more information, see "Cisco Collaboration Solutions Design Guidance" at http://www.cisco.com/go/ucsrnd.
IP Subnet Mask
If you are using a 24-bit IP subnet mask, ensure that you use the following format:255.255.255.0 . Do not use the format 255.255.255.000 . Although 255.255.255.000 is a valid format, it may cause problems during the upgrade process. We recommend that you change the format before you begin an upgrade to avoid possible problems. You can change the subnet mask by executing the set network ip eth0 <server_IP_address> 255.255.255.0 command.
Other formats are supported for subnet masks and this limitation applies to 24-bit subnet masks only.
Software Requirements
This section refers to application software requirements for Cisco Unified Communications Manager and the IM and Presence Service upgrades and migrations.
Device Name for Cisco Unified Mobile Communicator
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.
Export Restricted and Export Unrestricted Software
This release of Unified Communications Manager and IM and Presence Service supports an export unrestricted (XU) version, in addition to the export restricted (K9) version.
![]() Note | |
Export unrestricted versions differs from restricted versions as follows:
-
Encryption of user payload (information exchange) is not supported.
-
External SIP interdomain federation with Microsoft OCS/Lync or AOL is not supported.
-
After you install an unrestricted release, you can never upgrade to a restricted version. A fresh install of a restricted version on a system that contains an unrestricted version is also not supported.
-
All nodes within a single cluster must be in the same mode. For example, Unified Communications Manager and IM and Presence Service in the same cluster must either all be in unrestricted mode or all be in restricted mode.
-
IP Phone security configurations are modified to disable signaling and media encryption (including encryption provided by the VPN phone feature).
![]() Note | |
For all Graphical User Interfaces (GUIs) and Command Line Interfaces (CLIs), the Administrator can view the product version (restricted or export unrestricted).
The following table describes the GUI items that are not available for the export unrestricted version ofUnified Communications Manager and IM and Presence Service.
GUI Item | Location | Description |
---|---|---|
Cisco Unified CM Administration | ||
VPN Configuration | Advanced Features > VPN | This menu and its options are not available. |
Phone Security Profile Configuration | System > Security > Phone Security Profile | The Device Security Mode is set to Non Secure and is not configurable. |
Cisco Unified CM IM and Presence Administration | ||
Security Settings | System > Security > Settings |
|
Service Parameter Configuration for Cisco SIP Proxy service | System > Service Parameters and choose Cisco SIP Proxy as the Service |
|
SIP Federated Domains | Presence > Inter-domain Federation > SIP Federation | When you configure interdomain federation to OCS/Lync, you will receive warning popup to indicate that it is only possible to directly federate with another OCS/Lync within the enterprise. Interdomain federation to OCS/Lync outside the enterprise is not supported in unrestricted mode. |
XMPP Federation Settings | Presence > Inter-domain Federation > XMPP Federation > Settings | You cannot configure the security mode. It is set to NO TLS. |
Proxy Configuration Settings | Presence > Routing > Settings | You cannot set any TLS or HTTPS listeners as the preferred proxy listener. |
Upgrades from Unified CM 9.x
Upgrades from Unified Communications Manager version 9.x to version 10.x or higher fail if you have a SIP Profile with any of the following names on version 9.x:
-
Standard SIP Profile
-
Standard SIP Profile For Cisco VCS
-
Standard SIP Profile For TelePresence Conferencing
-
Standard SIP Profile For TelePresence Endpoint
-
Standard SIP Profile for Mobile Device
If you have a SIP Profile with any of these names, you need to rename or delete it before proceeding with the upgrade.
OS Admin Account Required for CLI-Initiated IM and Presence Upgrades
If you are using the utils system upgrade CLI command to upgrade IM and Presence Service nodes, you must use the default OS admin account, as opposed to a user with administrator privileges. Otherwise, the upgrade will not have the required privilege level to install essential services, thereby causing the upgrade to fail. You can confirm the account’s privilege level by running the show myself CLI command. The account must have privilege level 4.
Note that this limitation exists for CLI-initiated upgrades of IM and Presence Service only and does not apply to Unified Communications Manager. Also note that this limitation may be fixed for newer ISO files. See your ISO Readme file for details on your specific ISO file. For-up-to date information on this limitation, see CSCvb14399.
Upgrades from 11.5(1)SU2 with Push Notifications Enabled
If you are upgrading from the 11.5(1)SU2 release and you had Push Notifications enabled in the old release, you must disable Push Notifications in the current release and then follow the onboarding process to enable Push Notifications once again. This is required due to API changes in this release that were not a part of the 11.5(1)SU2 release. Your upgraded system will not be able to send troubleshooting logs to the Cisco Cloud unless you disable Push Notifications and then follow the onboarding process for this release.
After you upgrade your system, do the following:
Procedure
Step1 | Disable Push Notifications Follow these steps:
|
Step2 | Add a Unified Communications Manager product instance into the Smart Licensing system. See the "Smart Software Licensing" chapter at System Configuration Guide for Cisco Unified Communications Manager. |
Step3 | Enable Push Notifications for this release. For the full onboarding process, see the "Configure Push Notifications for Cisco Jabber on iPhone and iPad" chapter at System Configuration Guide for Cisco Unified Communications Manager. |
Database Migration Required for Upgrades with Microsoft SQL Server
If you have Microsoft SQL Server deployed as an external database with the IM and Presence Service and you are upgrading from 11.5(1), 11.5(1)SU1, or 11.5(1)SU2, you must create a new SQL Server database and migrate to the new database. This is required due to enhanced data type support in this release. If you don't migrate your database, schema verification failure will occur on the existing SQL Server database and services that rely on the external database, such as persistent chat, will not start.
After you upgrade your IM and Presence Service, use this procedure to create a new SQL Server database and migrate data to the new database.
![]() Note | This migration is not required for Oracle or PostgreSQL external databases. |
Before You Begin
The database migration is dependent on the MSSQL_migrate_script.sql script. Contact Cisco TAC to obtain a copy.
Step | Task | ||
---|---|---|---|
Step 1 | Create a snapshot of your external Microsoft SQL Server database. | ||
Step 2 | Create a new (empty) SQL Server database. For details, see the following chapters in the Database Setup Guide for the IM and Presence Service:
| ||
Step 3 | Run the System Troubleshooter to confirm that there are no errors with the new database.
| ||
Step 4 | Restart the Cisco XCP Router on all IM and Presence Service cluster nodes:
| ||
Step 5 | Turn off services that depend on the external database:
| ||
Step 6 | Run the following script to migrate data from the old database to the new database MSSQL_migrate_script.sql.
| ||
Step 7 | Run the System Troubleshooter to confirm that there are no errors with the new database.
| ||
Step 8 | Start the services that you stopped previously.
| ||
Step 9 | Confirm that the external database is running and that all chat rooms are visible from a Cisco Jabber client. Delete the old database only after you're confident that the new database is working. |
Upgrades from Release 11.5(1)SU5
The following IM and Presence Service features are supported by Release 11.5(1)SU5, but are not supported by 12.0(1) or 12.0(1)SU1 releases:
-
Encrypted IM Compliance Database
-
Persistent Chat Rooms for Cisco Jabber mobile clients
If you have either of these features deployed with Release 11.5(1)SU5, and you upgrade to 12.0(1) or 12.0(1)SU1 you will lose these features.
Upgrade Considerations for Upgrades from 12.0(1) to 12.5(1)
The following section provide information about the upgrades from 12.0(1) to 12.5(1) that your system must meet, and limitations that apply when you install or upgrade IM and Presence Service.
![]() Note | Please select the Reboot Option as “Reboot to upgraded partition” (switch version “Yes”) instead of default Reboot option as "Do not reboot after upgrade" (switch-version as “No”). Hence, the IM and Presence Service 12.5 will be compatible with the Unified Communications Manager 12.5 version. |
Refresh upgrade from Unified Communications Manager 12.0.1. to 12.5 or from Unified Communications Manager previous release upgrade to 12.5 release:
![]() Note | |
Upgrade Considerations for Upgrades from 10.5(1) to 14
The following section provides information about the upgrades from 10.5(1) to 14 that your system must meet, and limitations that apply when you install or upgrade IM and Presence Service.
![]() Note | |
Upgrade Considerations with FIPS Mode
When you enable the FIPS mode in Unified Communications Manager Release 12.5 SU1, the lower key size IPsec DH groups 1, 2, or 5 are disabled. If you have already configured the IPsec policies with DH groups 1, 2 or 5 and enabled FIPS mode, the upgrade to Unified Communications Manager Release 12.5 SU1 is blocked.
Perform any one of the following procedures before you upgrade to Unified Communications Manager Release 12.5 SU1:
-
Delete the previously configured IPsec policies and perform the upgrade. After the upgrade is complete, reconfigure the IPsec policies with DH groups 14–18.
-
Install the COP file (
latest_version.xxxx.cop.sgn
) that supports DH groups 14–18, reconfigure the IPsec policies and then perform an upgrade.Note
If you disable the FIPS mode after installing the COP file, the IPsec configuration page does not appear.
For more information on configuring the IPsec policies, see Cisco Unified Operating System Administration Online Help.
IPSec Requirements
![]() Note | Before starting the migration, disable IPsec policy on all the nodes in the cluster. |
Support for Intercluster Peers
The IM and Presence Service supports intercluster peers to clusters that are running different software versions. To find the interdomain federations that are supported, see the "Supported Integrations" chapter in the Compatibility Matrix for Cisco Unified Communications Manager and IM and Presence Service .
Spectre/Meltdown Vulnerabilities During Upgrade
This release of Unified Communications Manager, Cisco IM and Presence Service, Cisco Emergency Responder, and Cisco Prime Collaboration Deployment contain software patches to address the Meltdown and Spectre microprocessor vulnerabilities.
Before you upgrade to Release 12.5(1) or above, we recommend that you work with your channel partner or account team to use the Cisco Collaboration Sizing Tool to compare your current deployment to an upgraded deployment. If required, change VM resources to ensure that your upgraded deployment provides the best performance.
Duplicate ENUMS Break Upgrades and Migrations from 10.5(2)
If you are Direct upgrading or Direct migrating from Release 10.5(2) or 11.0(1) to any later release, an issue exists with older locale installations that causes upgrade and migration failures. This issue exists if any of the following Unified CM combined network locales have been installed:
-
cm-locale-combined_network-9.1.2.1100-1
-
cm-locale-combined_network-10.5.2.2200-1
-
cm-locale-combined_network-11.0.1.1000-1
This issue can also occur if the following Unified CM locales are installed together in the same cluster:
-
cm-locale-en_GB-9.1.2.1100-1
-
cm-locale-pt_BR-9.1.2.1100-1
-
cm-locale-en_GB-10.5.2.2200-1
-
cm-locale-pt_BR-10.5.2.2200-1
-
cm-locale-en_GB-11.0.1.1000-1
-
cm-locale-pt_BR-11.0.1.1000-1
To ensure that your upgrade does not fail, update your Unified Communications Manager and phone locale installation to use a locale that is dated after August 31, 2017 as this issue does not exist for any locale file issued after that date. After you update your locale installation, you can begin the upgrade or migration. For details on the workaround, see https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz97687.
Blue Screen Appears for Unified CM Refresh Upgrades
An issue exists with refresh upgrades of Unified Communications Manager to specific destination releases. After the timezone data populates, you may see a blue transition screen appear for 30 minutes or more.
If you see this blue screen, DO NOT stop the upgrade, or a kernel panic occurs. The upgrade will continue to run even while the blue screen displays. The blue screen will clear itself after approximately 30 minutes
Affected 'To' Versions
This issue affects refresh upgrades of Unified Communications Manager where the destination version falls within the range in the below table. This range includes SU and ES versions that lay within the range. This issue does not occur for upgrades to older or newer versions that do not fall within the range, or for upgrades of the IM and Presence Service.
Release Category | Affected Upgrade Destination Range |
---|---|
10.5(x) | 10.5.2.21170-1—10.5.2.22188-1 (includes 10.5(2)SU9) |
11.5(x) | 11.5.1.16099—11.5.1.17118-1 (includes 11.5(1)SU6) |
12.0(x) | 12.0.1.23036-1 — 12.0.1.24053-1 (includes 12.0(1)SU3) |
12.5(x) | 12.5.1.11001-1 — 12.5.1.12018-1 (includes 12.5(1)SU1) |
For additional details, see CSCvs28202.
Licensing Requirements
The following sections provide information about the licensing requirements for Unified Communications Manager and the IM and Presence Service.
![]() Note | As of Unified Communications Manager Release 12.0(1), Smart Licensing replaces Prime License Manager. Smart Licensing requires you to have a Smart Account created and configured before you upgrade or migrate the Unified Communications Manager server. |
Several deployment options through which Unified Communications Manager can connect to Cisco Smart Software Manager or Cisco Smart Software Manager satellite are:
-
Direct—Unified Communications Manager sends usage information directly over the internet. No additional components are needed.
-
Cisco Smart Software Manager satellite—Unified Communications Manager sends usage information to an on-premise Smart Software Manager. Periodically, an exchange of information is performed to keep the databases in synchronization. For more information on installation or configuration of the Smart Software Manager satellite, go to this URL: https://www.cisco.com/c/en/us/buy/smart-accounts/software-manager.html.
Note
Cisco Smart Software Manager satellite is an on-premises collector similar to standalone Prime License Manager. -
Proxy Server—Unified Communications Manager sends usage information over the internet through a proxy server.
Unified Communications Manager License Requirements
Cisco Smart Software Licensing is a new way of thinking about licensing. It adds flexibility to your licensing and simplifies it across the enterprise. It also delivers visibility into your license ownership and consumption.
Cisco Smart Software Licensing helps you to procure, deploy, and manage licenses easily where devices self-register and report license consumption, removing the need for product activation keys (PAK). It pools license entitlements in a single account and allows you to move licenses freely through the network, wherever you need them. It is enabled across Cisco products and managed by a direct cloud-based or mediated deployment model.
The Cisco Smart Software Licensing service registers the product instance, reports license usage, and obtains the necessary authorization from Cisco Smart Software Manager or Cisco Smart Software Manager satellite.
Cisco Smart Software Manager replaces Prime License Manager in Unified Communications Manager Release 12.0(1) and later versions. Cisco Prime License Manager is no longer used as of Release 12.0(1) and no longer appears in the Installed Applications pre-login screen.
If you have enabled the mixed-mode before upgrade and have not registered to Cisco Smart Software Manager or Cisco Smart Software Manager satellite then,
-
You see the warning message in the Cisco Unified CM Administration page and Cisco Unified OS Administration page as stated below:
Caution
The system is currently running Mixed mode. To continue running Mixed mode, please ensure Smart Licensing registration is completed using the Registration Token received from the Smart/Virtual Account that has Allow export-controlled functionality checked.
-
An alert named SmartLicenseExportControlNotAllowed is sent, when the Unified Communications Manager is not registered with the Registration Token.
For details on how to configure Cisco Smart Software Licensing, see the "Smart Software Licensing" chapter, located within the "Configure Initial Parameters for the System" at System Configuration Guide for Cisco Unified Communications Manager.
For more details on Cisco Smart Software Manager satellite, including the Smart Software Manager satellite Installation Guide, see http://www.cisco.com/go/smartsatellite.
Migration of PLM Licenses to Smart Entitlement
If you are eligible to upgrade to the Smart Licensing version of the product, then you are able to initiate the migration through the License Registration Portal or Cisco Smart Software Manager. You can self-initiate this process by downloading and installing the Smart Licensing version of the software and registering the device to a Smart Account using a Registration Token. The migration of any entitlements tracked by Cisco automatically migrates to the Customers Smart Account. You will also be able to initiate the migration of unused classic PAKs to Smart Accounts for future consumption by products in Smart Mode. This process is available through the License Registration Portal or Cisco Smart Software Manager.
Unified Communications Manager 9.0x and later version of 12.0(1)
-
If you are holding an active Cisco Software Support Service (SWSS) contract, then you can convert the classic licenses to smart entitlements through the Cisco Smart Software Manager at https://software.cisco.com/#SmartLicensing-LicenseConversion.
-
Two types of Migration are supported:
-
PAK based—Supported for already fulfilled, partially fulfilled and unfilled PAKs
-
Device based
-
-
Partial Conversion supports mixed environment of older and Unified Communications Manager 12.0(1) clusters.
Upgrade to Smart Entitlement
Unified Communications Manager Pre 9.0x (Device based) to 12.0(1)
You may contact Cisco Global Licensing Operations (GLO) for helping with migrating Device-based licenses to Smart Entitlement.
Customer may establish equivalent user-based licensing required by running License Count Utility (LCU). For more details, see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/uct/CUCM_BK_UCT_Admin_Guide/CUCM_BK_UCT_Admin_Guide_chapter_01.html.
From the LCU report, Customer may order respective quantity of Upgrade Licenses through Cisco Commerce Workspace. Beyond this, they would have to buy additional new licenses. For more details, see the Ordering Guide at http://www.cisco.com/c/en/us/partners/tools/collaboration-ordering-guides.html.
Specific License Reservation
Specific License Reservation (SLR) allows the customer to reserve licenses from their virtual account, tie them to a devices UDI and use their device with these reserved licenses in a disconnected mode. The customer reserves specific licenses and counts for a UDI from their virtual account. The following options describe the new functionality and design elements for Specific Reservation.
Command | Description |
---|---|
license smart reservation enable | Use this command to enable the license reservation feature. |
license smart reservation disable | Use this command to disable the license reservation feature. |
license smart reservation request | Use this command to generate reservation request code. |
license smart reservation cancel | Use this command to cancel the reservation process before the authorization code is installed. |
license smart reservation install "<authorization-code>" | Use this command to install the license reservation authorization-code generated on the Cisco Smart Software Manager. |
license smart reservation return | Use this command to remove the license reservation authorization code that is installed and list of reserved entitlements. The device transitions back to an unregistered state. |
license smart reservation return-authorization "<authorization code>" | Use this command to remove the license reservation authorization code that is entered by the user. |
![]() Note | If you are upgrading from 12.0 to higher versions and enable license reservation feature on upgraded server, you should download ciscocm-ucm-resetudi.k3.cop.sgn from CCO and install on the upgraded CUCM before enabling reservation feature. |
![]() Note | If you are upgrading the 12.5 system which is license reservation enabled to 14, see System Configuration Guide for Cisco Unified Communications Manager. |
IM and Presence Service License Requirements
The IM and Presence Service does not require a server license or software version license. However, you must assign users and enable the IM and Presence Service for each assigned user.
![]() Note | With the Jabber for Everyone offer, no end user licenses are required to enable IM and Presence Service functionality. For more information, see "Jabber for Everyone Quick Start Guide". |
You can assign IM and Presence Service on a per user basis, regardless of the number of clients you associate with each user. When you assign IM and Presence Service to a user, this enables the user to send and receive IMs and availability updates. If users are not enabled for IM and Presence Service, they will not be able to log in to the IM and Presence Service server to view the availability of other users, send or receive IMs, and other users will not see their availability status.
You can enable a user for IM and Presence Service using any of the following options:
-
The End User Configuration window in Unified Communications Manager. For more information, see the Administration Guide for Cisco Unified Communications Manager.
-
The Bulk Administration Tool (BAT)
-
Assign IM and Presence Service to a feature group template which you can reference from the Quick User/Phone Add window in Unified Communications Manager.
For more information, see the System Configuration Guide for Cisco Unified Communications Manager.
IM and Presence Service capabilities are included within both User Connect Licensing (UCL) and Cisco Unified Workspace Licensing (CUWL). IM and Presence Service capabilities can also be acquired for users that are not Unified Communications Manager IP Telephony users through the Jabber for Everyone Offer. For more information, see Jabber for Everyone Quick Start Guide.
Supporting Documentation
The following documents contain additional supporting information that helps you to upgrade in specific cases.
Task | |
---|---|
Setup virtualized Cisco hardware. | Refer to Cisco Collaboration on Virtual Servers in order to set up your virtualized platform. For details, see https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-installation-guides-list.html. |
Setup Cisco Business Edition 6000/7000 appliances | Refer to:
|
Replace existing hardware while preserving the configuration | Replace a Single Server or Cluster for Cisco Unified Communications Manager at https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-installation-guides-list.html. |
Review VMware requirements | For VMware requirements and best practices, go to https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/cisco-collaboration-virtualization.html. For VMware vendor documentation, go to http://www.VMware.com. |
Additional Planning and Sizing Resources | These documents also contain information that may help you to plan and size your upgraded system:
|