The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter discusses information to be aware of before the actual upgrade process, such as the general upgrade approach for the different contact center components, upgrade release versions of components involved in the upgrade, and upgrade dependencies and considerations.
Note |
The following upgrade strategies are recommendations only, as no formal upgrade testing was done for the UC 9.0 system release. |
The general approach is to upgrade each Unified Communications Manager cluster and its associated contact center components at one time, before upgrading the next cluster.
For each cluster, upgrade the components in the Cisco Unified Communications family of contact center components in the following order:
Note |
These components are upgraded first to ensure that the infrastructure is able to support the services required by Cisco Unified Communications components. |
After all the Unified Communications Manager clusters in the network have been upgraded, install any new components included in the target release set and remove obsolete or end-of-life components.
Note |
Ensure that you have a comprehensive "backout" plan in the event of an upgrade failure. |
The upgrade sequence of the contact center components should also be dictated by the following considerations:
Cisco Unified Communications System Release 9.0(1) offers support for new hardware for several components and has removed support for other hardware platforms. The bridge upgrade provides a migration path for customers who use discontinued server models. A bridge upgrade works on unsupported or discontinued hardware for the purpose of creating a DRS backup. The DRS backup can be restored on new hardware after a fresh installation completes. When preparing for an upgrade to Release 9.0(1), read all product upgrade documentation if you plan to migrate to the new hardware offerings.
Note |
You can set up a virtualized environment by running Unified Communications applications on a virtual machine on a Unified Computing System (UCS). For additional details, including UCS hardware information and third-party requirements, see: http://www.cisco.com/go/uc-virtualized |
Components within each release set should be compatible with each other and interoperate correctly. For example, components in a specific base release set are compatible with each other and interoperate, as also the components in the target release set.
The order of operations also needs to take into account the impact of backward compatibility or incompatibility as described later in this section, especially for multistage system and multisite migration upgrades, where each stage (or maintenance window) only upgrades some of the components in the release set.
However, as you upgrade individual components of the integrated system, the overall system may operate in a state of degraded service where one or more components have been upgraded to the next release level and may not interoperate with components that are still at the previous release level.
Components that are upgraded first should interoperate with other components that are still at the previous release level. For example, gateways are upgraded before Unified Communications Manager. Therefore, gateways, which are now at the next release level, must interoperate with Unified Communications Manager that has not been upgraded and is still at the previous release level.
Because some components have to be upgraded prior to Unified Communications Manager, there are certain upgrade issues and considerations to be aware of. For upgrade and migration on Unified Communications Manager hardware, see New and Changed Information for Cisco Unified Communications Manager Release 9.0(1) at: www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/9_0_1/delta/CUCM_BK_N38FD301_00_cucm-new-and-changed-90.pdf
You can migrate Cisco Unified Communications System applications (such as Cisco Unified Contact Center Enterprise (Unified CCE)) before upgrading Unified Communications Manager, if:
You should migrate Cisco Unified Communications System applications after upgrading Unified Communications Manager, if:
For compatibility and interoperability information about Unified Communications Manager, Unified Contact Center Enterprise, Unified IP IVR and other Cisco Unified Communications contact center products, see the following sites:
Refresh Upgrade is a new feature that allows upgrades between incompatible OS.
When you install 9.0 upgrade software, there is a temporary server outage while the Cisco Unified Communications Manager software is installed. Once you start the upgrade using either the command line or graphical user interface, the data is exported, and the system automatically reboots, at which point the server outage begins. The duration of this outage depends on your configuration and amount of data.
Caution |
If you are upgrading your software on HP 7825H3 or HP7828H3 hardware, there is no option to revert to the previous version of Unified Communications Manager. To perform an upgrade on one of these machines, you must use a 16GB USB key to migrate the data from the old system to the new installation. |
When the upgrade is complete, you can choose to activate the partition with the new upgrade software or return to using the partition with the previous version of the software. With the exception of HP 7825H3 and HP7828H3 hardware upgrades, the previous software remains in the inactive partition until the next upgrade. Your configuration information migrates automatically to the upgraded version in the active partition.
Note |
All upgrade paths prior to 8.5(2) require the installation of a Cisco Option Package (COP) file. The COP file delivers functionality to allow the upgrade path to be supported and to provide user experience enhancements. |
For more information and detailed procedures, see Software Upgrades in Cisco Unified Communications Operating System Administration Guide.
Be aware of the following constraints regarding Cisco Unified Communications Manager when upgrading from Cisco Unified Communications System Release 8.5(1) to Release 9.0(1):
To back up data to a remote device on the network, you must have an SFTP server that is configured. Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners certify their products with specified versions of Unified Communications Manager. Information on the vendors who have certified their products with Unified Communications Manager is available at: http://www.cisco.com/pcgi-bin/ctdp/Search.pl
Note |
The preceding SFTP server information also applies to Unified Presence and Unified Contact Center Express. |
Note |
If you are also changing hardware, the following information may not apply. The bridge upgrade provides a migration path for customers who use discontinued server models. Refer to bridge upgrade procedures in Upgrading to Cisco Unified Communications Manager Release 9.0(1) at: http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/upgrade/9_0_1/CUCM_BK_U8D523AB_00_upgrade-guide-cucm-90.html |
After all the nodes in the cluster are upgraded, make sure that you do the following in the listed order:
Unified CCX versions prior to 8.5(1) are not supported with Unified Communications Manager 9.0. You must upgrade Unified CCX to 8.5(1)SU3 or 9.0(1) before upgrading Unified Communications Manager to 9.0(1). For more information, see CSCts67056.
Cisco Aggregation Services Routers on an IOS of 15.1(3)S do not exchange routes with Cisco Adaptive Security Appliance 8.4(2). You must downgrade the IOS on Aggregation Services Routers to 15.1(2).
Be aware of the following considerations when upgrading Unified IP Phones:
For more detailed information about SIP Unified IP Phones and the differences between features on the SCCP and SIP phones, see the documentation at:
In multistage system upgrade scenarios, you may have to consider additional issues such as backward compatibility across components.
A version of one component is backward compatible with a previous version of another component when service functionality and behavior are maintained between the two component versions. Backward compatibility between two components or applications may limit the component upgrade order and cause service outage during upgrades.
If two components are upgraded during separate maintenance windows, as in the multistage system or multisite migration upgrade scenarios, the whole system exists in a partially upgraded state in the interval between the two maintenance windows.
The service capability during the period between maintenance windows depends on backward compatibility between the two components as discussed in this section. If the two components are not backward compatible, then a service outage occurs in the interval between the two maintenance windows.
This section describes some backward compatibility situations that may occur during the upgrade process.
Both new versions of two components are backward compatible with the previous version of the other component.
In this case, there is no restriction in the upgrade order relating to backward compatibility. Either component may be upgraded first and be able to interoperate with the other component as shown in the figure below. An example of this is Unified CCE and Unified Communications Manager.
You can perform the upgrade for these components across multiple maintenance windows. This type of upgrade is described in the multistage system and multisite migration upgrade approaches in System upgrade planning.
Only one of the new versions is backward compatible with the previous version of the other component.
In this case, the component that is backward compatible should be upgraded first to avoid a service outage during the upgrade as shown in the figure below.
You should perform the upgrade for these components across two separate maintenance windows. This type of upgrade is described in the Multistage System and Multisite Migration upgrade approaches in System upgrade planning
Neither of the new versions is backward compatible with the previous version of the other component.
A service outage exists from the time the first product is upgraded until the second component has completed its upgrade as shown in the figure below.
Because neither component is backward compatible with the other, both components have to be upgraded in the same maintenance window to avoid service outage.
The tables in this section list the component release versions of the base and target release sets and has the following elements:
The table below lists the software versions for the contact center components in the Cisco Unified Communications System Release 9.0(1) and Release 8.5(1) release sets.
Note |
Table cells with "—" indicate products that are not part of the base release sets. |
Cisco Unified Intelligent Contact Management Enterprise and Cisco Unified Contact Center Enterprise |
||
Cisco Unified Intelligent Contact Management Enterprise and Cisco Unified Contact Center Enterprise Operating System |
||
8.5(1) 1 |
||
Cisco Unified Contact Center Express/Unified IP IVR Operating System |
||
9.0(1)2 |
||
Cisco Unified Communications Manager IM and Presence Service (formerly Cisco Unified Presence) 3 |
||
Cisco TelePresence MCU MSE Series |
4.3 |
-- |
Cisco TelePresence Content Server |
5.2 Build 3222 |
-- |
Cisco Voice and Video Conferencing for ISR G2 Routers |
15.2(3)T1 |
-- |
8.6(1) 4 |
||
Cisco Unified IP Phones 7900 Series (7921G (Wireless), 7940, 7962, and 7970) |
||
Cisco Unified IP Phones 6900 Series (6911, 6921, 6941, 6945, and 6961) |
||
Cisco IP Video Phone E20 |
TE 6.0.0 |
— |
Cisco TelePresence System EX60 |
TE 6.0.0 |
— |
Cisco TelePresence System EX90 |
TE 6.0.0 |
— |
Cisco Virtualization Experience Clients |
Firmware 9.2(1) |
— |
Cisco Adaptive Security Appliance (5520, 5540, 5580) Services 5 |
||
Cisco Adaptive Security Appliance 5500 AIP Security Services Module (IPS) |
||
15.2(3)T1 6 |
||
Cisco 3825, 3845 (Unified CVP VXML, voice/data, H.323, SIP, MGCP, IOS-based Transcoders and Conference Bridges, and Cisco Unified Border Element gateways) |
||
Cisco AS5400XM (Unified CVP VXML, voice, H.323, SIP and PSTN gateways) |
||
Cisco Unified Border Element Enterprise Edition for Cisco ISR Series |
||
Cisco Unified Border Element Enterprise Edition for Cisco ASR 1000 Series |
||
Cisco Catalyst 3750 (WS-3750E-24PD) |
12.2(55)SE1 |
-- |
Cisco Catalyst 6503 (WS-SUP720-3BXL) |
12.2(18)SXF10 |
-- |
Cisco Catalyst 6506 (WS-SUP720-3BXL) |
12.2(33)SXH2a |
-- |
Cisco ASR1002 |
IOS XE 15.1(1)s |
-- |
Cisco UCS Express |
2.0.1 |
2.0.1 |
Cisco Integrated Services Router (ISR) 2901, 2911, 2921, 2951, 3925, 3945, 3925E, 3945E |
15.2(3)T1 |
— |
Cisco Unified Computing System B200 M2 Blade Server, Cisco Unified Computing System C200 M2 General-Purpose Rack-Mount Server, Cisco Unified Computing System C210 M2 General-Purpose Rack-Mount Server (Unified Communications Virtualization): Release 9.0(1) Version: Cisco UCS B-Series 2.0(1q),Cisco UCS C-Series 1.4(3c)2 |
VMWare ESXi 4.1 |
-- |
Cisco SRE 910 Service Module |
15.2(3)T1 |
— |