Planning Your System Upgrade

Table Of Contents

Planning Your System Upgrade

Introduction to System Upgrade

Targeted Software Releases

Upgrade Overview

Upgrade Roadmap

Cisco Unified Communications System Components

Adding New Components in Cisco Unified Communications System Release 5.0(2)

System Upgrade Paths

System Upgrade Strategy

Single-Stage Upgrade Using Existing Hardware

Single-Stage Upgrade Using New Hardware

Multistage System Upgrade Using Existing Hardware (Hybrid System)

Multisite Migration

Planning Your System Upgrade

---

This topic provides an overview of the upgrade process, the software releases that are involved in the upgrade process, and the different upgrade strategies that can be used based on the size of the customer network.

This topic contains the following sections:

•Introduction to System Upgrade

•Targeted Software Releases

•Upgrade Overview

•System Upgrade Strategy

Introduction to System Upgrade

Cisco Unified Communications System is defined around commonly deployed enterprise topology models in North America and European & Emerging Markets (EUEM) with the goal of growing and evolving over the next 12 to 18 months.

This system is built upon individual IP telephony and contact center products including, but not limited, to the Cisco Unified CallManager (Unified CallManager), Cisco Unified CallManager Express, Cisco Unified Intelligent Contact Management (Unified ICM), Cisco Unified Customer Voice Portal (Unified CVP), Cisco Unity, Cisco Unity Express, Cisco Unified Contact Center Enterprise (Unified CCE), Cisco Customer Response Solutions (CRS), and voice-capable gateways and routers.

Cisco Systems provides an integrated system to meet customer needs. Cisco Unified Communications System testing is a process for specifying (designing) and validating the interoperability of enterprise voice products working together as an integrated system. Cisco Unified Communications System Release 5.0 and Release 5.0(2) define a set of software releases for each of the system components.

Targeted Software Releases

A "Release Set" is defined as the combination of products, components, and software versions that were tested to work together as an integrated system. A particular system release is also referred to as a Release Set.

The system that is targeted for the upgrade process and discussed in this document include:

•Cisco Unified Communications System Release 5.0—The currently deployed software release set that is being upgraded. For detailed information on the deployment models and topologies developed to test the Release 5.0 release set, see Review Tested Site Models for IP telephony or Review Tested Deployment Models for contact center.

•Cisco Unified Communications System Release 5.0(2)—The new software release set that is the goal of the upgrade process. The deployment models and topologies are the same as the ones referenced above. For detailed information on the deployment models and topologies developed to test the Release 5.0(2) release set, see Review Tested Site Models for IP telephony or Review Tested Deployment Models for contact center.

Upgrade Overview

The upgrade process as discussed in this document addresses different upgrade strategies, preparation for the upgrade operation, order of operations such as the sequence in which the system components should be upgraded, and other dependencies such as backward compatibility of software.

---

Note This document only provides information related to upgrading components that are present in both of the targeted release sets (previous and next). It does not provide installation information about components that are not part of the existing production network and are being newly added to the network as a part of the next release. This information is available in the individual component installation documents.

---

Upgrade Roadmap

Perform the system-level upgrade of Cisco Unified Communications System components using the following high-level roadmap:

---

Step 1 Review your hardware requirements and perform all required hardware equipment checks. For instance, verify that the deployed hardware and operating system support the new Cisco Unified Communications System releases. Also verify that the DVD ROM drive in the server where you plan to perform the upgrade tasks is operational before you start the upgrade process.

For a list of supported MCS servers for Unified CallManager 5.0(4), see the Cisco Unified CallManager Server Upgrade Program at:

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure09186a0080174928.html

---

Note Unified CallManager 5.0(4) only supports MCS servers with a "-EVV" or "-IPC" suffix. It does not support servers with "ECS" appended to the end of the model number.

---

Step 2 Upgrade the existing network components from the Cisco Unified Communications System 5.0 release set to the Release 5.0(2) release set versions using one of the upgrade strategies described in the System Upgrade Strategy section. Be aware that the strategy you select should depend on a number of factors, including your size, topology, and the presence or absence of shared components among sites (such an Unified ICM system that spans multiple clusters).

---

Note The assumption for this roadmap is that the current test bed deployment includes components that are already supported by the Cisco Unified Communications System Release 5.0 release set. Verify that your hardware configurations are ready for an upgrade to the Cisco Unified Communications System Release 5.0(2) release set.

---

Step 3 Add any new components supported by the Cisco Unified Communications System Release 5.0(2) release set to the network by installing and configuring them. See the individual components' installation and configuration documents listed in the Adding New Components in Cisco Unified Communications System Release 5.0(2) section.

Be aware that this document does not provide upgrade and backup procedures for:

•Individual stand-alone components such as Unified CallManager, Unified CCE, and Cisco Unity. It only addresses the upgrade procedures of Cisco Unified Communications System components at the system-level.

•Third-party co-resident applications (although they can be used during the upgrade and backup process) such as:

–Antivirus

–Security

–Server management

–Remote access

•Additional third-party off-board applications such as:

–Operator console

–VoIP recording

–Billing and accounting

•Server replacement (hardware upgrade) for components. See individual components' installation documents for this information.

Step 4 Remove any components from your network that are not part of the Cisco Unified Communications System Release 5.0(2) release set or have reached EOL (end-of-life)/EOS (end-of-sale). Follow proper procedures to uninstall these components.

---

Cisco Unified Communications System Components

The following Cisco Systems enterprise voice products are considered part of the Release 5.0 release set:

•Cisco 6000 gatekeepers and gateways

•Cisco ATA 186/188

•Cisco Agent Desktop (CAD) and CAD Server

•Cisco Analog Phone Gateways (VG244 and VG248)

•Cisco Catalyst Switches

•Cisco Emergency Responder

•Cisco IP Communicator

•Cisco Security Agent

•Cisco Supervisor Desktop

•Cisco Unified CallManager

•Cisco Unified CallManager Express

•Cisco Unified Contact Center Enterprise

•Cisco Unified Contact Center Gateway Enterprise

•Cisco Unified Customer Voice Portal (Application Server and Voice Browser)

•Cisco Unified Intelligent Contact Management

•Cisco Unified IP Phones 7900 Series (SCCP and SIP)

•Cisco Unified MeetingPlace

•Cisco Unified MeetingPlace Express

•Cisco Unified MobilityManager

•Cisco Unified Operations Manager and Cisco Unified Service Monitor

•Cisco Unified Outbound Dialer

•Cisco Unified Personal Communicator

•Cisco Unified Presence Server

•Cisco Unified System Contact Center Gateway

•Cisco Unified System Contact Center

•Cisco Unity

•Cisco Unity Bridge

•Cisco Unity Connection

•Cisco Unity Express

•Cisco Unified Video Advantage

•Cisco Unified Videoconferencing Multipoint Control Unit (MCU) 3511 and 3540

•CiscoWorks Management Center for Cisco Security Agent

•Cisco Remote Monitoring Suite

•CTI OS Agent and Supervisor Desktop

•Customer Response Solutions (CRS) (Cisco Unified IP IVR & Cisco Unified Contact Center Express)

•Enterprise Gateway 2200

•IOS devices (including SRST and Voice/VXML gateways)

•IOS Gatekeepers

•IP Video Gateway 3521 and 3526

•Music On Hold

•TDM Gateway

•Video Endpoint Tandberg 550 and 1000

•VoIP Monitor

•Wireless IP Phone 7920

•Wireless Access Point 1100 and 1200

Adding New Components in Cisco Unified Communications System Release 5.0(2)

In addition to the above list of components, the following new components have been added to the Cisco Unified Communications System Release 5.0(2) deployment:

•Cisco Unified Presence Server

•Cisco Unified Personal Communicator (formerly known as Unified Client)

You must install the new components into the network and configure them (rather than upgrade them). See the individual component's installation and configuration documents at the following URLs:

•Cisco Unified Presence Server:
http://www.cisco.com/en/US/products/ps6837/prod_installation_guide09186a00805ab7d2.html 

•Cisco Unified Personal Communicator:
http://www.cisco.com/en/US/products/ps6844/products_installation_guide_book09186a008063484e.html 

System Upgrade Paths

This section provides the general information required to migrate from a common starting point leading up to the latest Cisco Unified Communications System releases.

Upgrading from IPC Systems Test Release Sets

If you want to upgrade from an IPC Systems Test release set to the Cisco Unified Communications System release set, be aware of the possible upgrade paths as listed below. You can access a complete listing of all the IPC Systems Test releases at:

http://www.cisco.com/univercd/cc/td/doc/product/voice/ip_tele/gblink/ipcmtrix.htm

•Major IPC System Test to Minor IPC System Test. For example, System Test release 4.0 to 4.1.

•Minor IPC System Test to IPC Minor System Test. For example, System Test 4.1 to 4.2.

•Minor IPC System Test to Major IPC System Test. For example, System Test 3.1 to 4.0.

•Minor IPC Systems Test to Major Cisco Unified Communications System.

---

Note Currently. the only supported path to upgrade from an IPC Systems Test to a Cisco Unified Communications System is from IPC Systems Test Release 4.1 to Cisco Unified Communications System Release 5.0.

---

Upgrading from Cisco Unified Communications System Release Sets

If you want to upgrade from an Cisco Unified Communications System release set, be aware of the possible upgrade paths as listed below:

•Major Cisco Unified Communications System to minor Cisco Unified Communications System

•Major Cisco Unified Communications System or minor Cisco Unified Communications System to Cisco Unified Communications System maintenance release

Figure 1-1 illustrates the recommended upgrade path from:

•Major IPC Systems Test release set to major IPC Systems Test release set

•Minor IPC Systems Test Release 4.1 to major Cisco Unified Communications System Release 5.0

•Major Cisco Unified Communications System Release 5.0 to maintenance release Cisco Unified Communications System Release 5.0(2)

Figure 1-1 Upgrade Paths for IPC Systems Test and Cisco Unified Communications System Releases

System Upgrade Strategy

This section discusses the upgrade strategies for all components in the Cisco Unified Communications System Release 5.0(2) deployment scenarios. Details of individual components upgrades are not described unless additional information or clarification is required.

The following upgrade strategies are available with Cisco Unified Communications System Release 5.0(2):

•Single-Stage Upgrade using Existing Hardware (Flash-cut)—All components in the network start at the Release 5.0 release set and all components can be upgraded to the Release 5.0(2) release set within a single maintenance window.

•Single-Stage Upgrade using New Hardware (either Flash-cut or Shrink-and-Grow)—A parallel Cisco Unified Communications System Release 5.0(2) network should be built using new hardware and pre-staged with configuration to support the existing production network.

All users can then be moved from the existing production network to the new network in one of two ways:

–In a single maintenance window using a Flash-Cut upgrade process

- or -

–In several maintenance windows using a Shrink-and-Grow upgrade process (where a single maintenance window is used to implement the new release versions on the new hardware, but multiple windows are used to migrate the users)

---

Note Be aware that it is not possible to build a parallel network and perform a flash-cut upgrade to the Release 5.0(2) release set without reconfiguring some components entirely. For instance, two Unified CallManager systems cannot exist on the same network with an identical hostname and IP address. Remember that you must use the same hostname and IP address when backing up and restoring a Unified CallManager system.

---

The above upgrade strategies involving the Single-Stage upgrade approach are appropriate for small sites (less than 300 seats) with a smaller number of components in the network.

•Multistage System Upgrade using Existing Hardware (Hybrid System)—The components in individual sites can be upgraded from the Cisco Unified Communications System Release 5.0 release set software to the Release 5.0(2) release set in stages during separate maintenance windows.

At the completion of each intermediate stage, the network exists as a hybrid system with a mix of the following:

–Some components are operating on the Release 5.0 release set

–Other upgraded components are operating on the Release 5.0(2) release set

---

Note Hybrid system refers only to inter-product versions, not to intra-product versions. For instance, all Unified CallManager servers in the same cluster, or all servers that are part of the same Unified ICM system, will remain at the same software release version.

---

The Multistage System upgrade approach is recommended for medium-to-large sites (ranging from 301-1499 seats for medium and 1500-4999 seats for large) with a greater number of components in the network.

•Multisite Migration (via Hybrid Network with Release Set inter-working)—Components are upgraded from the Release 5.0 release set to the Release 5.0(2) release set on a site-by-site basis during separate maintenance windows.

At the completion of each maintenance window, a hybrid network exists with a mix of the following:

–Sites whose components are operating on the Release 5.0 release set

–Sites whose components are operating on the Release 5.0(2) release set

Sites whose components are a hybrid system as described in Multistage System Upgrade Using Existing Hardware (Hybrid System)

This model assumes that sites may be upgraded independently. However, with the Multisite Migration strategy, you must account for distributed applications with shared components among sites. For example, if you have deployed a distributed Unified ICM system, a Cisco Emergency Responder supporting multiple Unified CallManager clusters, or a Unified CallManager cluster using Clustering-over-WAN (CoW), then these sites must be upgraded concurrently.

Users can be moved in stages from the existing production network to the new network operating on the Release 5.0(2) release set software.

The Multisite Migration strategy is recommended for large multisite environments (more than 5000 seats) with a large number of components in the network.

Single-Stage Upgrade Using Existing Hardware

All components in the network start at the Cisco Unified Communications System Release 5.0 release set and all components are upgraded to the Release 5.0(2) release set software within a single maintenance window (MW). Since all components are upgraded within a single maintenance window, interoperability is not required between the Release 5.0 release set and Release 5.0(2) release set.

The Single-Stage upgrade on existing hardware approach is typically not recommended for large customer sites/networks, since it has to be performed within a single maintenance window.

Figure 1-2 shows the single maintenance window that is involved in the Single-Stage upgrade on existing hardware approach:

Figure 1-2 Single-Stage Upgrade Using Existing Hardware

Single-Stage Upgrade Using New Hardware

A parallel Cisco Unified Communications System network should be built using new hardware and pre-staged with configuration to support the existing production network. All users can be then moved from the existing production network to the new network operating with the latest Cisco Unified Communications System release software either in a single maintenance window (using Flash-Cut) or in several maintenance windows (using Shrink-and-Grow).

The Single-Stage upgrade on new hardware approach is not recommended for large customer sites/networks for the following reasons:

•The upgrade cannot be performed within a single maintenance window.

•The expense of a complete new parallel network is significant.

Figure 1-3 shows the maintenance windows that are involved in the Single-Stage upgrade on new hardware approach:

Figure 1-3 Single-Stage Upgrade Using New Hardware

Multistage System Upgrade Using Existing Hardware (Hybrid System)

Individual components and/or sites can be upgraded in stages, from the Cisco Unified Communications System Release 5.0 release set software to the Release 5.0(2) release set software, during separate maintenance windows. At the completion of each intermediate stage, the site exists as a hybrid system with a mix of the following:

•Some components operating on the Cisco Unified Communications System Release 5.0 release set

•Other upgraded components operating on the Cisco Unified Communications System Release 5.0(2) release set software

The Multistage System upgrade on existing hardware is the recommended approach for medium-to-large networks. In this case, individual components within a single-site and/or individual sites in a multisite environment are progressively upgraded over the span of several days or weekends.

This type of staging is required because:

•Sufficient time may not be available (maintenance window) to take the system out of service for the complete upgrade of all the components involved.

•You must test existing functionality following the upgrade.

•You must test new functionality following the upgrade.

You can view a staged upgrade as a series of maintenance windows separated by inter-maintenance window intervals. During each maintenance window, one or more components of the system or a subset of the components is upgraded.

Customers typically have a maintenance window during which service disruptions are likely to have minimal impact and affect only a limited number of users, for example, during the night or during a weekend.

Before the staged upgrade is completed, the whole network exists in a partially upgraded state where some components have been upgraded to Release 5.0(2) release set software and the remaining components are operating with the Release 5.0 release set software.

Backward compatibility of the components is critical during the staged upgrade, so that Release 5.0(2) release set components are able to interoperate with the Release 5.0 release set components. If any component is not backward compatible, this can potentially result in prolonged periods of service outage spanning several maintenance windows (possibly several weeks).

Therefore, during multi-stage upgrades, it is mandatory to have interoperability between the Release 5.0 release set software and the Release 5.0(2) release set software versions. For more information on software and backward compatibility considerations, see Chapter 2, "Preparing for System Upgrade."

Figure 1-4 shows the maintenance windows that are involved in the Multistage System upgrade on existing hardware approach:

Figure 1-4 Multistage System Upgrade Using Existing Hardware (Hybrid System)

Multisite Migration

Components are upgraded from the Cisco Unified Communications System Release 5.0 release set to the Release 5.0(2) release set on a site-by-site basis during separate maintenance windows.

At the completion of each maintenance window, a hybrid network will exist across multiple sites. Within each site, either a Single-Stage or Multi-Stage System Upgrade strategy can be used to upgrade that particular site's components from the Release 5.0 release set to the Release 5.0(2) release set.

Interworking can be expected among sites on pure Release 5.0 release set versions and sites on pure Release 5.0(2) release set versions as shown in Figure 1-5. However, interworking will not be possible between these pure sites and hybrid system sites.

---

Note If you have a component that is common to multiple sites, such as a shared Cisco Emergency Responder or Unified ICM system, this may impact the interoperability itself, the order in which sites may be upgraded, and/or which sites must be upgraded concurrently.

---

Users can be moved in stages from the existing production network to the new network operating with the latest Cisco Unified Communications System release software. The number of users on the existing Release 5.0 network will shrink while the number on the Release 5.0(2) network will grow correspondingly.

This migration process can span several weeks and, sometime months, if necessary. During this upgrade approach, it is essential that the two networks, existing and new, should be able to communicate with each other.

Figure 1-5 shows the maintenance windows that are involved in the Multisite Migration approach:

Figure 1-5 Multisite Migration

Table 1-1 provides a summary of the preceding upgrade strategies.

Table 1-1 Summary of Upgrade Strategies 

Features	Single-Stage Upgrade	Multistage System Upgrade	Multisite Migration Upgrade
Recommended for Installations	Small single-site Small multisite (less than 300 seats)	Medium single-site Medium multisite (between 301 and 1499 seats) Large single-site (between 1500 and 4999 seats)	Large multisite (more than 5000 seats)
Maintenance Window (MW)	One (1)	Multiple	Multiple
Interoperability between Releases at Component Level	Not Required	Required	Required
Interoperability between Releases at Site Level	Not Required	Not Required	Required
User Migration	Complete in one stage	Partial until final stage	Partial until final stage
Upgrade Time Period	One time slot, for example, during a weekend maintenance window	Several days to weeks	Several weeks to months