r

Step 1 

Verify that your system meets the system requirements for upgrading Cisco Unified Communication Manager nodes in the cluster.

To find which servers support Cisco Communication Manager 5.x releases, refer to the Guide to Cisco Communication Manager Upgrades and Server Migrations at

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

.

r

Step 2 

Run Cisco Unified Communication Manager Upgrade Utility on the server to verify that the system is ready for upgrade.

Refer to Using Cisco Unified Communication Manager Upgrade Utility .

Note Review the document to install the utility and to understand what checks the utility performs.

r

Step 3 

Perform the recommended backup procedures on the publisher server. Back up every database that is associated with your Cisco Unified Communication Manager server.

Refer to Cisco IP Telephony Backup and Restore System (BARS) Administration Guide.

Note Review the document overview for information on the versions of applications that BARS supports and for instructions on installing BARS.

r

Step 4 

If you are using a third-party application to access Call Detail Records (CDR), perform a backup of the CDR data as recommended in the third-party vendor documentation.

Cisco IP Telephony Backup and Restore System (BARS) Administration Guide .

Note Review the document overview for information on the versions of applications that BARS supports and for instructions on installing BARS.

r

Step 5 

If you do not need to carry over your CDR data to Cisco Unified Communication Manager 5.1(1), Cisco recommends that you purge the CDR data before you run DMA.

Purging the CDR data speeds up the migration process and decreases the size of the DMA TAR file.

Purging CDR: Refer to "Using Manual Database Purge" in Cisco CallManager Serviceability Administration Guide, Release 4.1(3).

r

Step 6 

(If your systems are using centralized TFTP) Upgrade off-clusters in the centralized TFTP environment.

When upgraded to 5.x, the other clusters participating in Centralized TFTP must be running a supported version (see list below) of Cisco Unified CM.

Configuring Centralized TFTP: Refer to "Cisco TFTP" in the Cisco Unified CallManager System Guide 5.0(4)

Note The referenced procedure in the 5.0(4) System Guide applies to 5.1(1) as well.

Supported versions of Cisco Unified CM:

•3.3(5)sr2

•4.1(3)sr2

•4.2

•4.3

•5.0

•5.1

•6.0

These Cisco Unified CM versions are not supported:

•4.0(1)

•4.0(2)

•4.1(1)

•4.1(2)

r

Step 7 

Export the data on the current Cisco Unified Communication Manager Publisher server by running the Data Migration Assistant (DMA).

Ensure the configuration files and exported data files are located in one of the following locations:

•Hard drive (for DMABackupInfo.inf only)

•Floppy drive (for DMABackupInfo.inf only)

•Tape drive

•Remote drive

Note Running DMA is required for obtaining the license file (see Checklist for Upgrading the First Cisco Unified CM Node).

DMA generates two files:

•A tape archive (TAR) file that contains the database and directory information. The format of the filename follows: DMABackup<M>-<D>-<Y>#<H>-<mm>.tar where M specifies the month, D specifies the day, Y specifies the year, H specifies the hour in a 24-hour format, and mm specifies the minutes.

•A backup information file that contains Cisco Unified Communication Manager configuration data, named DMABackupInfo.inf. The system saves it in the D:\DMA folder as part of the TAR file.

Note Do not change the configuration data filename. The upgrade fails if it does not find a file with the exact filename and format.

For more information on data migration, refer to Data Migration Assistant Administration Guide . You will be choosing an installation option based on the location of the DMA output configuration file and TAR file.

Note Review the pre installation guidelines and installation procedures

r

Step 8 

Before the upgrade, obtain the necessary information for configuring the platform and Cisco Unified CM on the first and subsequent nodes.

See the "Installation Information Worksheet" section.

r

Step 9 

Record the Host Name/IP Address value that is configured on the Server Configuration Settings window of the Cisco Unified CallManager 4.x server.

To access the Host Name/IP Address field on the 4.x server, navigate to System > Server.

For more information, see Assigning the Host Name or IP Address to the Server

r

Step 10 

Match the server's NIC speed and duplex settings with the switch port's configuration. For servers or switch ports that can support GigE (1000BaseT), use auto-negotiation on both sides.

For more information, see "NIC and Switch port Speed and Duplex" in Installation Field Definitions.

r

Step 11 

Enable PortFast on all switch ports connected to Cisco Unified servers.

With PortFast enabled, [the switch] immediately brings a port from the blocking state into the forwarding state by eliminating the forwarding delay (the amount of time a port waits before changing from its Spanning-Tree Protocol (STP) learning and listening states to the forwarding state.

r

Step 12 

(If you are using NIC teaming) Be aware that the NIC teaming configuration will be lost during the upgrade. You will need to set it up on each server after the upgrade.

After the upgrade, be sure to complete Step 1 in the Post-Upgrade Checklist.

r

Step 13 

Familiarize yourself with the navigation options within the installation wizards.

See Navigating Within the Installation Wizard.