Upgrades

Version Requirements

For 11.x Versions up to 11.5(1)SU1

If you are installing IM and Presence nodes, the software version of the first IM and Presence node (the IM and Presence database publisher node) must match the first three numbers of the software version installed on the Unified Communications Manager publisher node. For example, IM and Presence Service software version 11.0.1.10000-1 is compatible with Unified Communications Manager software version 11.0.1.30000-2. Refer to the following table for sample Unified Communications Manager versions and IM and Presence Service versions that are compatible.. The bolded numbers must match.

Table 1. Examples of Compatible Unified Communications Manager and IM and Presence Service Versions

Sample Unified Communications Manager Version

Example of Compatible IM and Presence Service Version

11.0.1.30000-2

11.0.1.10000-1

11.5.1.10000-6

11.5.1.10000-4

After you install the first IM and Presence node, the software version of any IM and Presence subscriber nodes that you install must match all five version numbers of the first IM and Presence node. For example, if the IM and Presence database publisher node is at version 11.5.1.10000-1, then all IM and Presence subscriber nodes must also be 11.5.1.10000-1.

Release 11.5(1)SU2

For Release 11.5(1)SU2, both Unified Communications Manager and IM and Presence Service must be running official 11.5(1)SU2 versions. Running an 11.5(1)SU2 version of Unified Communications Manager with an earlier version of IM and Presence Service is not supported. Similarly, running an 11.5(1)SU2 version of IM and Presence Service with an earlier version of Unified Communications Manager is not supported.

The following software versions are supported with Release 11.5(1)SU2:

  • Unified Communications Manager 11.5.1.12900-21

  • IM and Presence Service 11.5.1.12900-25

Release 11.5(1)SU3

For Release 11.5(1)SU3, both Unified Communications Manager and IM and Presence Service must be running official 11.5(1)SU3 versions. Running an 11.5(1)SU3 version of Unified Communications Manager with an earlier version of IM and Presence Service is not supported. Similarly, running an 11.5(1)SU3 version of IM and Presence Service with an earlier version of Unified Communications Manager is not supported.

The following software versions are supported with Release 11.5(1)SU3:

  • Unified Communications Manager 11.5.1.13900-52

  • Unified Communications Manager 11.5.1.13901-3

  • Unified Communications Manager 11.5.1.13902-2

  • IM and Presence Service 11.5.1.13900-57

  • IM and Presence Service 11.5.1.13901-1

Release 11.5(1)SU4

The following versions are supported:

  • Cisco Unified Communications Manager 11.5.1.14900-11

  • IM and Presence Service 11.5.1.14900-32

This release offers two main deployment options for the IM and Presence Service:

  • Standard Deployments (Decentralized)—In this deployment, both Cisco Unified Communications Manager and the IM and Presence Service must be running an 11.5(1)SU4 version for your deployment to be supported. A version mismatch is not supported.

  • Centralized Deployments of the IM and Presence Service—Within the IM and Presence central cluster, both the IM and Presence Service and the Cisco Unified Communications Manager instance (this is primarily a database and provisioning instance, and does not handle telephony) must be running an 11.5(1)SU4 version. However, the remote telephony clusters to which the IM and Presence Service connects do not have to be running an 11.5(1)SU4 version.

Release 11.5(1)SU5

The following versions are supported:

  • Cisco Unified Communications Manager 11.5.1.15900-18

  • IM and Presence Service 11.5.1.15900-33

This release offers two main deployment options for the IM and Presence Service:

  • Standard Deployments (Decentralized)—In this deployment, both Cisco Unified Communications Manager and the IM and Presence Service must be running an 11.5(1)SU5 version for your deployment to be supported. A version mismatch is not supported.

  • Centralized Deployments of the IM and Presence Service—Within the IM and Presence central cluster, both the IM and Presence Service and the Cisco Unified Communications Manager instance (this is primarily a database and provisioning instance, and does not handle telephony) must be running an 11.5(1)SU5 version. However, the remote telephony clusters to which the IM and Presence Service connects do not have to be running an 11.5(1)SU5 version.

Release 11.5(1)SU6

The following versions are supported:

  • Cisco Unified Communications Manager 11.5.1.16900-16

  • IM and Presence Service 11.5.1.16910-12

This release offers two main deployment options for the IM and Presence Service:

  • Standard Deployments (Decentralized)—In this deployment, both Cisco Unified Communications Manager and the IM and Presence Service must be running an 11.5(1)SU6 version for your deployment to be supported. A version mismatch is not supported.

  • Centralized Deployments of the IM and Presence Service—Within the IM and Presence central cluster, both the IM and Presence Service and the Cisco Unified Communications Manager instance (this is primarily a database and provisioning instance, and does not handle telephony) must be running an 11.5(1)SU6 version. However, the remote telephony clusters to which the IM and Presence Service connects do not have to be running an 11.5(1)SU6 version.

Release 11.5(1)SU7

The following versions are supported:

  • Cisco Unified Communications Manager 11.5.1.17900-52

  • IM and Presence Service 11.5.1.17900-8

This release offers two main deployment options for the IM and Presence Service:

  • Standard Deployments (Decentralized)—In this deployment, both Cisco Unified Communications Manager and the IM and Presence Service must be running an 11.5(1)SU7 version for your deployment to be supported. A version mismatch is not supported.

  • Centralized Deployments of the IM and Presence Service—Within the IM and Presence central cluster, both the IM and Presence Service and the Cisco Unified Communications Manager instance (this is primarily a database and provisioning instance, and does not handle telephony) must be running an 11.5(1)SU7 version. However, the remote telephony clusters to which the IM and Presence Service connects do not have to be running an 11.5(1)SU7 version.

Release 11.5(1)SU8

The following versions are supported:

  • Cisco Unified Communications Manager 11.5.1.18900-97

  • IM and Presence Service 11.5.1.18900-15

This release offers two main deployment options for the IM and Presence Service:

  • Standard Deployments (Decentralized)—In this deployment, both Cisco Unified Communications Manager and the IM and Presence Service must be running an 11.5(1)SU8 version for your deployment to be supported. A version mismatch is not supported.

  • Centralized Deployments of the IM and Presence Service—Within the IM and Presence central cluster, both the IM and Presence Service and the Cisco Unified Communications Manager instance (this is primarily a database and provisioning instance, and does not handle telephony) must be running an 11.5(1)SU8 version. However, the remote telephony clusters to which the IM and Presence Service connects do not have to be running an 11.5(1)SU8 version.

Upgrade Paths for Cisco Unified Communications Manager

The following table lists the range of upgrade paths that are supported for Unified Communications Manager. For more detailed information about supported upgrade paths, see the Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-device-support-tables-list.html.

Table 2. Unified Communications Manager Upgrade Paths, Release 11.5(1)
From To Upgrade Type

Releases prior to and including 8.5(x)

11.5(1)SU1

Refresh upgrade. Required COP files:

  • ciscocm.refresh_upgrade_<latest_version>.cop.sgn

  • ciscocm.version3-keys.cop.sgn

Optional COP files:

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

  • ciscocm.free_common_space_v<latest_version>.cop.sgn

8.6(x)

11.5(1)SU1

Refresh upgrade. Required COP files:

  • ciscocm.version3-keys.cop.sgn

Optional COP files:

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

  • ciscocm.free_common_space_v<latest_version>.cop.sgn

9.1(x)

11.5(1)SU1

Refresh upgrade. Required COP files:

  • ciscocm.version3-keys.cop.sgn

Optional COP files:

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

  • ciscocm.free_common_space_v<latest_version>.cop.sgn

10.5(x)

11.5(1)SU1

Standard upgrade; no COP file required.

11.0(x)

11.5(1)SU1

Standard upgrade; no COP file required.

11.5(1)

11.5(1)SU1

Standard upgrade; no COP file required.

If you are upgrading from a release that is not listed here or that is installed on MCS hardware, you must perform the upgrade using Prime Collaboration Deployment. For more information, see http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-maintenance-guides-list.html.

Upgrade Paths for IM and Presence Service

The following table lists the range of upgrade paths that are supported for the IM and Presence Service. For more detailed information about supported upgrade paths, see the Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-device-support-tables-list.html.

Table 3. Upgrade Paths from Cisco Unified Presence Releases
From Cisco Unified Presence Release To IM and Presence Release Upgrade Type

8.5(4) through 8.6(1)

11.5(1)SU1

Refresh upgrade. Requires the following COP files:

  • cisco.com.cup.refresh_upgrade_v<latest_version>.cop

  • ciscocm.version3-keys.cop.sgn
Table 4. Upgrade Paths from IM and Presence Service Releases

From IM and Presence Release

To IM and Presence Release

Upgrade Type

9.1(x)

11.5(1)SU1

Refresh upgrade. Requires the following COP file:

  • ciscocm.version3-keys.cop.sgn

10.5(x)

11.5(1)SU1

Standard upgrade; no COP file required.

11.0(x)

11.5(1)SU1

Standard upgrade; no COP file required.

11.5(1)

11.5(1)SU1

Standard upgrade; no COP file required.

If you are upgrading from a release that is not listed here or that is installed on MCS hardware, you must perform the upgrade using Prime Collaboration Deployment. For more information, see http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-maintenance-guides-list.html.

Upgrading with FIPS Mode Enabled

For Release 11.5(x), Cisco Unified Communications Manager and IM and Presence Service do not support RSA certificates with key-sizes that are less than 2048 bits when FIPS mode is enabled. This affects server certificates and LSCs.

If you are upgrading to Release 11.5(x) with FIPS mode enabled and you are using RSA key-sizes that are less than 2048 bits on your current version, then you can carry out one of the following items to resolve the problem.

You can either:

  • Regenerate the effected certificates before you upgrade if your current version supports key-sizes of 2048 bits, or

  • Regenerate the effected certificates after you upgrade to Release 11.5(x).


    Note

    If you choose this option, then secure connections are not allowed to use the effected certificates until they have an RSA key-size of 2048 bits or greater.

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.

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.

Table 5. Deprecated Phone Models for this Release

Deprecated Phone Models for this Release

First Deprecated as of Unified CM...

  • Cisco IP Phone 12 S

  • Cisco IP Phone 12 SP

  • Cisco IP Phone 12 SP+

  • Cisco IP Phone 30 SP+

  • Cisco IP Phone 30 VIP

  • Cisco Unified IP Phone 7902G

  • Cisco Unified IP Phone 7905G

  • Cisco Unified IP Phone 7910

  • Cisco Unified IP Phone 7910G

  • Cisco Unified IP Phone 7910+SW

  • Cisco Unified IP Phone 7910G+SW

  • Cisco Unified IP Phone 7912G

  • Cisco Unified Wireless IP Phone 7920

  • Cisco Unified IP Conference Station 7935

11.5(1) and later releases

For additional information, refer to Field Notice: Cisco Unified Communications Manager Release 11.5(x) does not support some deprecated phone models at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/fieldNotice/cucm_b_fn-deprecated-phone-models-1151.html.

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:

  1. Confirm whether the phones in your network will be supported in this release.

  2. Identify any non-supported phones.

  3. For any non-supported phones, power down the phone and disconnect the phone from the network.

  4. 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.

  5. 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.

Cisco Jabber During Upgrade

It is not essential requirement that all users must log out from Cisco Jabber, when upgrading the IM and Presence Service. However, it is always a best practice that users are log out from Cisco Jabber during the upgrade.