upgrd611-pdf by vverge

VIEWS: 28 PAGES: 42

									Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases
This document describes how to upgrade to Cisco Unified Communications Manager 6.1(1) from a Cisco Unified Communications Manager 4.x release. For information about upgrading your Cisco Unified Communications Manager software after you have upgraded to release 5.0(1) or later, refer to Cisco Unified Communications Operating System Administration Guide. For information about performing a fresh installation of Cisco Unified Communications Manager (rather then upgrading from an earlier release) or configuring Cisco Unified Communications Manager when it is preinstalled on your server, refer to Installing Cisco Unified Communications Manager. The 6.1(1) release of Cisco Unified Communications Manager uses a different installation framework than releases of Cisco Unified Communications Manager prior to 5.0. Before upgrading to Cisco Unified Communications Manager 6.1(1), review all upgrade instructions carefully.

Contents
This document contains the following topics:
• • • • • • • • •

Installation Overview Related Documentation Important Considerations Preparing To Upgrade Upgrading Cisco Unified Communications Manager Post-Upgrade Tasks Using the Disaster Recovery Disc Examining Log Files Obtaining Documentation, Obtaining Support, and Security Guidelines

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

© 2007 Cisco Systems, Inc. All rights reserved.

Installation Overview

Installation Overview
Cisco Unified Communications Manager uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified Communications Manager 4.x to Cisco Unified Communications Manager 6.1(1), and upgrade to a newer service release during the installation. For a more detailed description of the different installation types, see Table 1.
Table 1 Installation Options

Installation Types Basic Install

Description This option represents the basic Cisco Unified Communications Manager 6.1(1) installation, which installs the software from the installation disc and does not use any imported data. This option allows you to upgrade the software version that the installation disc contains with the latest service release. You can also choose to apply a patch and then do a Windows upgrade and perform both during the installation process. This option allows you to import database information from a Cisco Unified Communications Manager 4.x system by using a file that the Data Migration Assistant (DMA) tool produces.

Applying a Patch

Import Windows Data

Note

The document describes the procedure for performing a Windows Upgrade. For basic installation instructions, see Installing Cisco Unified Communications Manager.

Related Documentation
Refer to the Cisco Unified Communications Manager Documentation Guide for further information about related Cisco IP telephony applications and products. Table 2 lists URLs for software and additional documentation.
Table 2 Quick Reference for URLs

Related Information and Software Software-only servers (IBM, HP, Compaq, Aquarius) Cisco Unified Communications Manager service releases

URL http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_li st.html http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

Cisco MCS data sheets http://www.cisco.com/en/US/products/hw/voiceapp/ps378/index.html

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

2

OL-12536-01

Important Considerations

Important Considerations
Before you proceed with the Cisco Unified Communications Manager upgrade, consider the following requirements and recommendations:
•

Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.

Caution

Failure to connect the Cisco Unified Communication Manager nodes to a UPS may result in damage to physical media and require a new installation of Cisco Unified Communications Manager.
• • •

Be aware that when you install Cisco Unified Communications Manager 6.1(1) on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten. Be aware that all secure phones will remain down during the upgrade process. Install the Cisco Unified Communications Manager software on the first node, or publisher, server first and then on the subsequent nodes. You must configure the subsequent nodes on the first node before you can install the subsequent node. Enter the same security password on all servers in the cluster. Before you can install subsequent, or subscriber, nodes, you must first configure them on the first, or publisher, node. Install the Cisco Unified Communications Manager software during off-peak hours or a maintenance window to avoid impact from call-processing interruptions. Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address and that the Cisco Unified IP Phones can register with the application when you plug the phones into the network. Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table is full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.

• • • •

•

• • • •

You must have access to an SFTP server to back up Cisco Unified Communications Manager over a network. Do not attempt to perform any configuration tasks during the installation. Do not install any Cisco-verified applications until you complete installing Cisco Unified Communications Manager on every server in the cluster. Be aware that customer background images, custom TFTP files, custom MoH files, and customer ring tones do not get migrated during the upgrade process. You must reinstall these files after the upgrade completes. See the “Post-Upgrade Tasks” section on page 34 for more information. Be aware that end-user settings such as ring tones and background images do not get migrated during the upgrade process. The end user must reconfigure these items after the upgrade completes. Be aware that the demo license feature is not available when you upgrade from a previous product version. Be aware that directory names and filenames that you enter while running the installation program are case-sensitive.

• • •

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

3

Preparing To Upgrade

•

Administrators can connect third party voicemail systems to Cisco Unified Communications Manager. The voice-messaging system must have a simplified message desk interface (SMDI) that is accessible with a null-modem EIA/TIA-232 cable (and an available serial port). To connect the EIA/TIA-232 cable to Cisco Unified Communications Manager Release 5.0 or later, use a Cisco certified serial-to-USB adapter with the part number USB-SERIAL-CA=. Carefully read the instructions that follow before you proceed with the installation.

•

Preparing To Upgrade
This section describes how to prepare to upgrade from Cisco Unified Communications Manager 4.x to release 6.1(1).

Frequently Asked Questions About the Cisco Unified Communications Manager Installation
The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified Communications Manager installation.

From What Version Can I Upgrade to Cisco Unified Communications Manager 6.1(1)?
For information on supported upgrades, refer to the Cisco Unified Communications Manager Software Compatibility Matrix.

What User Names Passwords do I Need to Specify?
Note

The system checks your passwords for strength. For guidelines on creating a strong passwords, see the “What is a Strong Password?” section on page 5. During the Cisco Unified Communications Manager upgrade, you must specify the following user names and passwords:
• • • •

Administrator user name and password Application user name and password Security password End user password and PIN

Administrator User Name and Password

You use the Administrator user name and password to log in to the following areas:
• • •

Cisco Unified Communications Operating System Administration Disaster Recovery System Command Line Interface

To specify the Administrator user name and password, follow these guidelines:

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

4

OL-12536-01

Preparing To Upgrade

• •

Administrator Account user name—The Administrator Account user name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores. Administrator Account password—The Administrator Account password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.

You can change the Administrator Account password or add a new Administrator account by using the command line interface. For more information, see the Cisco Unified Communications Operating System Administration Guide.
Application User Name and Password

You use the Application user name and password to access applications that are installed on the system, including the following areas:
• • • •

Cisco Unified Communications Manager Administration Cisco Unified Serviceability Cisco Real-Time Monitoring Tool Cisco Unified Reporting Application User name—The Application User name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores. Application User password—The Application User password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.

To specify the Application user name and password, follow these guidelines:
• •

You can change the Application User name and password by using the command line interface. For more information, see the Cisco Unified Communications Operating System Administration Guide.
Security Password

The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster. The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
End User Password and PIN

The system uses this password and PIN to reset the password and PIN for all end users that were configured on the Windows-based Cisco Unified Communications Manager.

Note

After you upgrade the system, you must inform all end users about this new default password and PIN, which they can then change to a password and PIN of their choosing.

What is a Strong Password?
The installation wizard checks to ensure that you enter a strong password. To create a strong password, follow these recommendations:
• • • •

Mix uppercase and lowercase letters. Mix letters and numbers. Include hyphens and underscores. Remember that longer passwords are stronger and more secure than shorter ones.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

5

Preparing To Upgrade

Avoid the following types of passwords:
• • • • •

Do not use recognizable words, such as proper names and dictionary words, even when combined with numbers. Do not invert recognizable words. Do not use word or number patterns, like aaabbb, qwerty, zyxwvuts, 123321, and so on. Do not use recognizable words from other languages. Do not use personal information of any kind, including birthdays, postal codes, names of children or pets, and so on.

Which servers does Cisco support for this installation?
To find which servers support Cisco Unified Communications Manager 6.1(1), refer to the Cisco Unified Communications Manager Server Support Matrix at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html

May I install other software besides Cisco Unified Communications Manager on the server?
You must do all software installations and upgrades by using Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified Communications Manager with Cisco Unified Communications Manager 6.1(1).

Browser Requirements
You can access Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, Cisco Unified Reporting, Cisco Unified Communications Operating System Administration, and Disaster Recovery System by using the following browsers:
• •

Microsoft Internet Explorer version 6.x Netscape Navigator version 7.1 or later

Note

Cisco does not support or test other browsers, such as Mozilla Firefox.

Configuring the Hardware
As a part of software installation, the system installer configures the system BIOS and RAID settings for the new operating system and Cisco Unified Communications Manager application. See Table 3 for the BIOS settings and Table 4 for the RAID settings that are set up during installation.

Note

If the hardware configuration process fails during installation, you can use boot-time utilities on both the IBM and HP servers to manually configure the RAID and BIOS settings, as shown in Table 3 and Table 4.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

6

OL-12536-01

Preparing To Upgrade

Table 3

BIOS Configuration Settings for HP and IBM Servers

HP Servers OS Selection: Linux (not applicable on newer models) Boot order: CD, C:, Floppy Post F1 prompt: Delayed Hyperthreading: Enabled

IBM Servers OS Selection: Not applicable Boot order: CD, C:, Floppy Post F1 prompt: Delayed Hyperthreading: Enabled

Table 4

RAID Settings

MCS 7825 Servers (HP and IBM) Software RAID Software RAID
Note

MCS 7835 Servers (HP and IBM) Logical drives: 1 RAID type: 1(1+0)

MCS 7845 Servers (HP and IBM) Logical drives: 2 RAID type: 1(1+0)

For the HP 7825H1 and the IBM 7825I1, SATA RAID gets enabled, and the RAID type specifies 1(1+0), with one logical drive.

Performing Pre-Upgrade Tasks
Perform the following tasks before you begin the upgrade: Pre-Upgrade Task
Step 1

Important Notes Refer to the following documentation for information about the capacity of server models:
• •

Verify that you meet the system requirements for upgrading Cisco Unified Communications Manager nodes in the cluster.

Release notes for your product release http://www.cisco.com/en/US/products/hw/voiceapp/ps 378/prod_brochure_list.html

Make sure to account for any growth that has occurred since initial system configuration.
Step 1

Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible Caution power supply (UPS) to provide backup power and protect your system.

Failure to connect the Cisco Unified Communication Manager nodes to a UPS may result in damage to physical media and require a new installation of Cisco Unified Communications Manager.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

7

Preparing To Upgrade

Pre-Upgrade Task
Step 2

Important Notes

Verify the integrity of any new server hardware (such as hard drives and memory) by running any manufacturer-provided utilities. Make sure that you have a copy of all custom ring files, phone backgrounds, and music on hold sources. Consider this as precautionary because the restore is designed to restore these items.

Step 3 Step 4 Step 5 Step 6

Obtain and store files for any locales that are installed on You might need to reinstall locales after doing the the server. upgrade. Do not change computer names or IP addresses, or add more nodes to the cluster. Verify the integrity of your software downloads and DVDs. Perform the following tasks:
•

Check the MD5 checksum of downloaded software against the published value to verify that it downloaded properly. Verify that the DVD is readable by a DVD drive.

• Step 7

Perform any system tests that you intend to perform after Document these tests, so you can perform them identically the replacement before the replacement also, to verify that after doing the replacement. the tests pass before you do the replacement. If you use DNS, verify that all servers to be replaced are See the “Verifying DNS Registration” section on page 10. configured in DNS properly. All nodes in the cluster must either use DNS or not use it. If you are getting the system time from an NTP server, verify that the first node can synchronize with the NTP server before you install a subsequent node. To verify the NTP status of the first node, log into the Command Line Interface on the first node and enter the following command: utils ntp status For more information, see the Cisco Unified Communications Operating System Administration Guide.

Step 8

Step 9

Caution

If the first node fails to synchronize with an NTP server, installation of a subsequent node can also fail.

Step 10 Do not run Network Address Translation (NAT) or Port

Address Translation (PAT) between Cisco Unified Communications Manager nodes.
Step 11 Record all the registration information by using the Cisco

See the “Determining Registration Counts by Using Unified Communications Manager Real-Time Monitoring RTMT” section on page 10. Tool (RTMT). by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT). See the “Recording Critical Service Status” section on page 11.

Step 12 Record all the critical services and their activation status

Step 13 Using the Syslog viewer in the Cisco Unified

Perform this task to ensure that no system-affecting errors Communications Manager Real-Time Monitoring Tool exist on your system. (RTMT), locate any events that have a severity of Error or See the “Locating System Errors by Using Syslog Viewer” higher. section on page 11. See the “Recording Trace and Log Central Job Details” section on page 12. See the “Accessing CDR Management Configuration” section on page 12.

Step 14 Record the details of all Trace and Log Central jobs. Step 15 Record CDR Management configuration and

destinations, if applicable.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

8

OL-12536-01

Preparing To Upgrade

Pre-Upgrade Task
Step 16 From Cisco Unified Communications Manager

Important Notes See the “Determining System Configuration Counts” section on page 13. See the “Firmware Information” section on page 14. If you have custom device types that do not ship with Cisco Unified Communications Manager, make sure that you have the appropriate files. You might need to reinstall the devices types after performing the replacement. For information about performing these tasks and about Cisco Unified Communications Manager security, refer to the “Installing the CTL Client” procedures in the Cisco Unified Communications Manager Security Guide. Refer to Using Cisco Unified CallManager Upgrade Utility.

Administration, determine the number of specific items that are configured on the server.
Step 17 From Cisco Unified Communications Manager

Administration, record all the phone loads and device types that display on the Firmware Load Information window.
Step 18 If your cluster is running in secure mode, make sure that

you have USB eToken devices and CTL Client plug-in utility installed on a computer that is running the Windows operating system.
Step 19 Run Cisco Unified CallManager Upgrade Utility on the

server to verify that the system is ready for upgrade.
Step 20 Perform the recommended backup procedures on the

Refer to Cisco IP Telephony Backup and Restore System publisher server. Back up every database that is associated (BARS) Administration Guide. with your Cisco Unified Communications Manager server. For more information on CAR, refer to the Cisco Unified Detail Records (CDR), perform a backup of the CDR data Communications Manager CDR Analysis and Reporting as recommended in the third-party vendor documentation. Administration Guide. Purging the CDR data speeds up the migration process and Unified Communications Manager 6.1(1), Cisco decreases the size of the DMA TAR file. recommends that you purge the CDR data before you run DMA. DMA generates two files:
•

Step 21 If you are using a third-party application to access Call

Step 22 If you do not need to carry over your CDR data to Cisco

Step 23 Export the data on the current Cisco Unified

Communications 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
•

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 Communications Manager configuration data, named DMABackupInfo.inf. The system saves it in the D:\DMA folder as part of the TAR file. Do not change the configuration data filename. The upgrade fails if it does not find a file with the exact filename and format.

Note

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

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

9

Preparing To Upgrade

Pre-Upgrade Task
Step 24 Before the upgrade, obtain the necessary information for

Important Notes See the “Gathering Information for an Installation” section on page 15.

configuring the platform and Cisco Unified Communications Manager on the first and subsequent nodes.
Step 25 Record the Host Name/IP Address value that is

To access the Host Name/IP Address field on the 4.x configured on the Server Configuration Settings window server, navigate to System > Server. of the Cisco Unified Communications Manager 4.x For more information, see the “Assigning the Host server. Name/IP Address (Servername) to the 6.1(1) Server” section on page 20 the installation wizards. See “Navigating Within the Installation Wizard” section on page 21. See the “Applying a Patch” section on page 25 for more information.

Step 26 Familiarize yourself with the navigation options within Step 27 Make sure that you have the 6.1(1) installation DVD. Also

if you plan to install a patch during the upgrade, ensure you have the patch file available on a DVD or SFTP or FTP server that the Cisco Unified Communications Manager nodes can access.

Verifying DNS Registration
If you use DNS, verify that all servers to be replaced are registered in DNS properly.
Procedure
Step 1 Step 2 Step 3

Open a command prompt. To ping each server by its DNS name, enter ping <DNS name>. To look up each server by IP address, enter nslookup <IP address>.

Related Topics

Performing Pre-Upgrade Tasks, page 7

Determining Registration Counts by Using RTMT
Record the number of registered devices, including the numbers of registered phones and gateways, by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT).
Procedure
Step 1

Download and install the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT) by choosing Application > Plugins from Cisco Unified Communications Manager Administration, clicking Find, and clicking the Download link next to the appropriate RTMT installer.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

10

OL-12536-01

Preparing To Upgrade

If you are planning to install the RTMT tool on a computer that is running the Microsoft Windows operating system, click the Download link for the Cisco Unified Communications Manager Real-Time Monitoring Tool-Windows. If you are planning to install the RTMT tool on a computer that is running the Linux operating system, click the Download link for the Cisco Unified Communications Manager Real-Time Monitoring Tool-Linux.
Step 2 Step 3

Open RTMT. Perform one of the following tasks:
• •

In the Quick Launch Channel, click the View tab, click the Device category, and click the Device icon. Choose Monitor > Device Summary.

Step 4

For each node, record the number for each device type that is displayed, including the numbers of registered phones, FXS, FXO, T1Cas, PRI, MOH, MTP, CFB, XCODE, and H323 Gateways.

Related Topics
• • •

Performing Pre-Upgrade Tasks, page 7 Post-Upgrade Tasks, page 34 Cisco Unified Serviceability Administration Guide

Recording Critical Service Status
Record all the critical services and their status by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT).
Procedure
Step 1

Perform one of the following tasks:
• •

In the Quick Launch Channel, click the View tab, click the Server category, and click the Critical Services icon. Choose Monitor > Server > Critical Services.

Step 2

Record the status of all critical services for each node in the cluster.

Related Topics
• • •

Performing Pre-Upgrade Tasks, page 7 Post-Upgrade Tasks, page 34 Cisco Unified Serviceability Administration Guide

Locating System Errors by Using Syslog Viewer
Using the Syslog viewer in the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT), locate any events that have a severity of Error or higher.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

11

Preparing To Upgrade

Procedure
Step 1

Open RTMT and perform one of the following tasks:
• •

In the Quick Launch Channel, click the Tools tab; then, click SysLog Viewer and the SysLog Viewer icon. Choose Tools > SysLog Viewer > Open SysLog Viewer.

Step 2 Step 3 Step 4 Step 5

From the Select a Node drop-down list box, choose the server where the logs that you want to view are stored. Double-click the Application Logs folder. Locate events with a severity of Error or higher. Review each log to locate system-affecting errors.

Related Topics
• • •

Performing Pre-Upgrade Tasks, page 7 Post-Upgrade Tasks, page 34 Cisco Unified Serviceability Administration Guide

Recording Trace and Log Central Job Details
Record the details of all Trace and Log Central jobs.
Procedure
Step 1

Open RTMT and perform one of the following tasks:
• •

In the Quick Launch Channel, click the Tools tab; then, click Trace and the Job Status icon. Choose Tools > Trace > Job Status.

Step 2

Double click each scheduled job and record the details that display for each job in the Show Detail dialog box.

.

Related Topics
• •

Performing Pre-Upgrade Tasks, page 7 Cisco Unified Serviceability Administration Guide

Accessing CDR Management Configuration
Record CDR Management configuration and destinations, if applicable. You use the CDR Management Configuration window to set the amount of disk space to allocate to call detail record (CDR) and call management record (CMR) files, configure the number of days to preserve files before deletion, and configure up to three billing application server destinations for CDRs. The CDR repository manager service repeatedly attempts to deliver CDR and CMR files to the billing servers

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

12

OL-12536-01

Preparing To Upgrade

that you configure on the CDR Management Configuration window until it delivers the files successfully, until you change or delete the billing application server on the CDR Management Configuration window, or until the files fall outside the preservation window and are deleted.
Procedure
Step 1

From Cisco Unified Serviceability, choose Tools > CDR Management. The CDR Management Configuration window displays. Record the General Parameters and the Billing Application Server Parameters.

Step 2

Related Topics
• •

Performing Pre-Upgrade Tasks, page 7 Cisco Unified Serviceability Administration Guide

Determining System Configuration Counts
From Cisco Unified Communications Manager Administration, obtain counts of each of the items that are configured on the system that you want to verify after the replacement. Some examples of items to count follow:
• • • • • • •

Phones Gateways Trunks Users Route Patterns CTI ports CTI route points

Procedure
Step 1

In Cisco Unified Communications Manager Administration, access the windows for each item that you want to count and click Find without entering any search parameters. Some examples follow:
• • • • •

Find and List Phones (Device > Phone) Find and List Gateway (Device > Gateway) Find and List Trunks (Device > Trunk) Find and List Route Patterns (Call Routing > Route/Hunt > Route Pattern) Find and List Users (User Management > End Users)

Note •

Before the upgrade, locate users by choosing User > Global Directory. Find and List Application Users (User Management > Application Users)

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

13

Preparing To Upgrade

Note Step 2

Before the upgrade, locate users by choosing User > Global Directory.

Record the number of each of the items (devices, route patterns, and users).

Related Topics
• • •

Performing Pre-Upgrade Tasks, page 7 Post-Upgrade Tasks, page 34 Cisco Unified Communications Manager Administration Guide

Firmware Information
Record all of the phone loads and device types that display on the Firmware Load Information window.
Procedure
Step 1

In Cisco Unified Communications Manager Administration, choose Device > Device Settings > Firmware Load Information. The Firmware Load Information window displays.

Step 2

Record all the phone loads and device types that display.

Note

If you have custom device types that do not ship with Cisco Unified Communications Manager, make sure that you have the appropriate files, so you can reinsert them, if needed.

Related Topics
• • •

Performing Pre-Upgrade Tasks, page 7 Post-Upgrade Tasks, page 34 Cisco Unified Communications Manager Administration Guide

Obtaining System Version Information
Compare the system version on each node in your cluster by using Cisco Unified Communications Operating System Administration. Verify that you have DVDs with that version. If you have a service release, you need media for base image and the service release.
Procedure
Step 1 Step 2

From Cisco Unified Communications Manager Administration, choose Help > About. Make a note of the system version.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

14

OL-12536-01

Preparing To Upgrade

Note

After the upgrade, you can also view the system version by choosing Show > System from Cisco Unified Communications Operating System Administration. Make a note of the value that displays in the Product Version field on the System Status window.

Related Topics
• • •

Performing Pre-Upgrade Tasks, page 7 Post-Upgrade Tasks, page 34 Cisco Unified Communications Operating System Administration Guide

Gathering Information for an Installation
Use Table 5 to record the information about your Cisco Unified Communications Manager server. Gather this information for each Cisco Unified Communications Manager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You can make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system.

Note

Because some of the fields are optional, they may not apply to your configuration. For example, you choose not to set up an SMTP host.

Caution

You cannot change some of the fields after installation without reinstalling the software, so be sure to enter the values that you want. The last column in the table shows whether a field can be changed after installation and, if so, whether you can change it through Cisco Unified Communications Operating System Administration or through the Command Line Interface (CLI).

Table 5

Node Configuration Data

Parameter Administrator ID Your entry:

Description

Can Entry Be Changed After Installation?

This field specifies the administrator No, you cannot change the entry after account user ID that you use for secure shell installation. access to the CLI, for logging into Cisco Note After installation, you can create Unified Communications Operating System additional administrator accounts, Administration and for logging into the but you cannot change the original Disaster Recovery System. administrator account user ID.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

15

Preparing To Upgrade

Table 5

Node Configuration Data (continued)

Parameter Administrator Password Your entry:

Description

Can Entry Be Changed After Installation?

This field specifies the password for the Yes, you can change the entry after installaAdministrator account, which you use for tion by using the following CLI command: secure shell access to the CLI, for logging CLI > set password admin into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System. Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.

Application User Name Your entry:

You use the Application User name as the default password for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability. You use the Application User password as the default password for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified CallManager Serviceability. Choose the appropriate country for your installation.

Yes, you can change the entry after installation by using the following CLI command: CLI > utils reset_ui_administrator_name

Application User Password Your entry:

Yes, you can change the entry after installation by using the following CLI command: CLI > utils reset_ui_administrator_password Yes, you can change the entry after installation by using the following CLI command:

Country Your entry:

The system uses this information to generate CLI > set web-security certificate signing requests (CSRs), which are used to obtain third-party certificates. DHCP Your entry: If you want to use DHCP to automatically configure the network settings on your server, choose Yes. Yes, you can change the entry after installation by using the following CLI command:

If you choose Yes, you do not get prompted CLI > set network dhcp for DNS or static configuration settings. If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway. DNS Enable Your entry: A DNS server resolves a hostname into an Yes, you can change the entry after installaIP address or an IP address into a hostname. tion by using the following CLI command: If you do not have a DNS server, enter No. CLI > set network dns If you have a DNS server, Cisco recommends that you enter Yes to enable DNS.
Note

When DNS is not enabled, you should only enter IP addresses (not host names) for all network devices in your Cisco Unified Communications Manager network.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

16

OL-12536-01

Preparing To Upgrade

Table 5

Node Configuration Data (continued)

Parameter DNS Primary Your entry:

Description Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd. Consider this field mandatory if DNS is set to yes.

Can Entry Be Changed After Installation? Yes, you can change the entry after installation by using the following CLI command: CLI > set network dns

DNS Secondary (optional) Your entry:

Enter the IP address of the DNS server that Yes, you can change the entry after you want to specify as the optional installation by using the following CLI secondary DNS server. command: CLI > set network dns

Domain Your entry:

This field represents the name of the domain Yes, you can change the entry after in which this machine is located. installation by using the following CLI command: Consider this field mandatory if DNS is set to yes. CLI > set network domain The system uses this password to reset the password for all end users that were configured on the Windows-based Cisco Unified CallManager. The system uses this PIN to reset the PIN for all end users that were configured on the Windows-based Cisco Unified CallManager. Yes, after you upgrade the system, you must inform all end users about this new password, which they can then change to a password of their choice. Yes, after you upgrade the system, you must inform all end users about this new PIN, which they can then change to a PIN of their choice.

End User Password Your entry:

End User PIN Your entry:

Gateway Address Your entry:

Enter the IP address of the network gateway. Yes, you can change the entry after installation by using the following CLI If you do not have a gateway, you must still command: set this field to 255.255.255.255. Not having a gateway may limit you to only being able CLI > set network gateway to communicate with devices on your subnet. If DHCP is set to No, consider this field mandatory.

Hostname Your entry:

Enter a host name that is unique to your server. The host name can comprise up to 64 characters and can contain alphanumeric characters and hyphens. If DHCP is set to No, consider this field mandatory.

No, you cannot change the entry after installation.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

17

Preparing To Upgrade

Table 5

Node Configuration Data (continued)

Parameter IP Address Your entry:

Description Enter the IP address of your server. If DHCP is set to No, consider this field mandatory.

Can Entry Be Changed After Installation? Yes, you can change the entry after installation by using the following CLI command: CLI > set network IP
Note

If IP addresses (not host names) are configured in Cisco Unified Communications Manager Administration under System > Servers, you must change the IP address there before changing it here, or call processing will fail.

IP Mask Your entry:

Enter the IP subnet mask of this machine. If DHCP is set to No, consider this field mandatory.

Yes, you can change the entry after installation by using the following CLI command: CLI > set network ip eth0

Location Your entry:

Enter the location of the server.

The system uses this information to generate certificate signing requests (CSRs), which CLI > set web-security are used to obtain third-party certificates. The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. Enter the MTU size in bytes for your network. If you are unsure of the MTU setting for your network, use the default value. Default: 1500 bytes

Yes, you can change the entry after installation by using the following CLI command:

MTU Size Your entry:

Yes, you can change the entry after installation by using the following CLI command: CLI > set network mtu

NIC Duplex Your entry:

Choose the duplex mode for the network interface card (NIC), either Full or Half.
Note

This parameter only displays when you choose not to use Automatic Negotiation.

Yes, you can change the entry after installation by using the following CLI command: CLI > set network nic Yes, you can change the entry after installation by using the following CLI command: CLI > set network nic

NIC Speed Your entry:

Choose the speed for the NIC, either 10 Megabits per second or 100 Megabits per second.
Note

This parameter only displays when you choose not to use Automatic Negotiation.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

18

OL-12536-01

Preparing To Upgrade

Table 5

Node Configuration Data (continued)

Parameter NTP Server Your entry:

Description Enter the hostname or IP address of one or more network time protocol (NTP) servers with which you want to synchronize.
Note

Can Entry Be Changed After Installation? Yes, you can change the entry after installation by using the following CLI command: CLI > utils ntp config

You can enter up to five NTP servers.

Organization Your entry:

Enter the name of your organization.

Yes, you can change the entry after installaThe system uses this information to generate tion by using the following CLI command: certificate signing requests (CSRs), which CLI > set web-security are used to obtain third-party certificates. Servers in the cluster use the security Yes, you can change the entry after password to communicate with one another. installation by using the following CLI command: The password must contain at least six alphanumeric characters. It can contain CLI > set password security hyphens and underscores, but it must start with an alphanumeric character. Caution To avoid losing communications Note Save this password. You will be between nodes, you must change asked to enter the same security the Security password on all password for each subsequent node nodes in a cluster. in the cluster. Enter the hostname or IP address for the SMTP server that is used for outbound e-mail. The hostname can contain alphanumeric characters, hyphens, or periods, but it must start with an alphanumeric character.
Note

Security Password Your entry:

SMTP Location Your entry:

Yes, you can change the entry after installation by using the following CLI command: CLI > set smtp

You must fill in this field if you plan to use electronic notification. You can enter a full name or abbreviation. The value you enter gets used to generate a Certificate Signing Request (CSR). Yes, you can change the entry after installation by using the following CLI command: CLI > set web-security Yes, you can change the entry after installation by using the following CLI command: CLI > set timezone

State Your entry:

Enter the state where the server is located.
Note

Time Zone Your entry:

This field specifies the local time zone and offset from Greenwich Mean Time (GMT). Choose the time zone that most closely matches the location of your machine.

Unit Your entry:

Enter your unit.
Note

The value you enter gets used to generate a Certificate Signing Request (CSR).

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

19

Preparing To Upgrade

Handling Network Errors During Upgrade
During the upgrade process, the installation program verifies that the server can successfully connect to the network by using the network configuration that you enter. If it cannot, a message displays, and you are prompted to select one of the following options:
• •

RETRY —The installation program tries to validate networking again. If validation fails again, the error dialog box displays again. REVIEW (Check Install)—Allows you to review and modify the networking configuration. The installation program returns to the network configuration windows. Becauss networking is validated after you complete each networking window, the message might display multiple times. If the message displays while you are reviewing the network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window appears again.

• •

HALT— The installation halts. You can copy the installation log files to a USB disk to aid troubleshooting of your network configuration. IGNORE —The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times.

Assigning the Host Name/IP Address (Servername) to the 6.1(1) Server
In 4.x releases, the Host Name/IP Address field (also known as Servername) on the publisher server Server Configuration Settings window contains one of the following types of values:
• •

If DNS is enabled, it identifies the host name. If DNS is not enabled, it contains the IP address of the server.

To access Server Configuration Settings, navigate to System > Server. The Data Migration Assistant (DMA) file that is used to migrate data from 4.x to 6.1(1) releases includes the Host Name/IP Address value. When you migrate data by using DMA, the Host Name/IP Address (Servername) for the publisher server gets imported into the 6.1(1) database as follows:
•

If the Host Name/IP Address (Servername) was a Host Name, the installation program compares this Servername to the provisioned Hostname for the 6.1(1) server (either through static provisioning or DNS/DHCP). If a mismatch exists, the installation program does the following actions:
– Uses the provisioned Hostname as the Host Name/IP address for the 6.x server, overriding the

servername in the DMA file.
– Notifies you about the mismatch and its resolution. – Prompts you to proceed or cancel the installation. •

If the Host Name/IP Address (Servername) was an IP address, the installation program compares this Servername to the provisioned IP Address for the 6.x server (either through static provisioning or DNS/DHCP). If a mismatch exists, the installation program does the following actions:
– Uses the provisioned IP Address as the Servername for the 6.x server, overriding the servername

in the DMA file.
– Notifies you about the mismatch and its resolution. – Prompts you to proceed or cancel the installation.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

20

OL-12536-01

Upgrading Cisco Unified Communications Manager

This feature allows you to import your 4.x data to a 6.1(1) server without having to preserve the IP Address or Host Name. The IP Address and/or Host name of the 6.1(1) server can differ from the 4.x servername.

Caution

Do not assign a hostname or IP address to the upgraded server that is already assigned to another node in the cluster. Doing so causes the cluster upgrade to fail.

Upgrading Cisco Unified Communications Manager
This section describes how to upgrade Cisco Unified Communications Manager from a Windows-based version (4.x) to version 6.1(1). You upgrade the operating system and application by running one installation program.

Caution

Before beginning this procedure, ensure that you have backed up the data on your current Windows-based version of Cisco Unified Communications Manager. For more information, see the documentation for your version of Backup and Restore Utility.

Navigating Within the Installation Wizard
For instructions on how to navigate within the installation wizard, see Table 6.
Table 6 Installation Wizard Navigation

To Do This Move to the next field Move to the previous field Choose an option Scroll up or down in a list Go to the previous window Get help information on a window

Press This Tab Alt-Tab Spacebar Up or down arrow Space bar to choose Back (when available) Space bar to choose Help (when available)

Starting the Installation
You use this procedure to install the operating system on first and subsequent nodes. Before you begin to upgrade the first node, make sure that you have reviewed and completed the tasks described in the “Performing Pre-Upgrade Tasks” section on page 7 To upgrade a subsequent node in the cluster, you must first install the new operating system and the new Cisco Unified Communications Manager application on the first node and then configure the subsequent node on the first node by using Cisco Unified Communications Manager Administration. On a subsequent node, you can either install the software version on the disc or retrieve a more recent service release from a remote server. The subsequent nodes will retrieve data from the first node at the end of the installation.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

21

Upgrading Cisco Unified Communications Manager

To upgrade a subsequent node in the cluster from Cisco Unified Communications Manager 4.x to Cisco Unified Communications Manager Release 6.1(1) or later, perform the following steps:
1. 2. 3. 4. 5. 6.

Upgrade the first node, the Cisco Unified Communications Manager 4.x publisher server, to Cisco Unified Communications Manager 6.1(1) or later. Using Cisco Unified Communications Manager Administration on the first node, configure the subsequent nodes. Ensure that the subsequent nodes have network connectivity to the first node. Install the new operating system and Cisco Unified Communications Manager application from a DVD. If required, upgrade the software to a later service release. Configure the Cisco Unified Communications Operating System and Cisco Unified Communications Manager.

Note

You must complete a successful migration of data on the first node prior to upgrading the subsequent nodes in the cluster.

Caution

Before beginning this procedure, ensure you have already upgraded the Cisco Unified Communications Manager 4.x publisher server, configured the subsequent node on the Cisco Unified Communications Manager 6.1(1) first node, and have network connectivity to the first node. Failure to meet these conditions can cause the installation to fail.

Caution

If you configured Network Time Protocol on the first node, ensure that the first node is synchronized with an NTP server before you upgrade a subsequent node. From the Command Line Interface on the first node, enter utils ntp status. Ensure that the printout indicates that the node is synchronized with an NTP server. If the first node is not synchronized with an NTP server, installation of the subsequent node will fail. Insert the installation DVD into the tray and restart the server, so it boots from the DVD. After the server completes the boot sequence, the DVD Found window displays. To perform the media check, choose Yes; or to skip the media check, choose No. The media check checks the integrity of the DVD. If your DVD has passed the media check previously, you might choose to skip the media check.

Step 1 Step 2

Note

If you have a new server with Cisco Unified Communications Manager preinstalled, you do not need to install from a DVD. Go directly to the “Entering Preexisting Configuration Information” procedure on page 24.

If you choose No, continue with Step 5.
Step 3

If you choose Yes to perform the media check, the system installer performs the media check and displays the Media Check Result window. Perform these tasks:
a.

If the Media Check Result displays Pass, choose OK to continue the installation.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

22

OL-12536-01

Upgrading Cisco Unified Communications Manager

b. Step 4

If the media fails the Media Check, either download another copy from Cisco.com or obtain another disc directly from Cisco Systems.

The system installer performs the following hardware checks to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will get prompted to restart your system. Leave the DVD in the drive during the reboot:
•

First, the installation process checks for the correct drivers, and you may see the following warning:
No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?

To continue the installation, choose Yes.
•

The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support. The installation process next verifies RAID configuration and BIOS settings.

•

Note

If this step repeats, choose Yes again.

After the hardware checks complete, the Product Deployment Selection window displays.
Step 5

In the Product Deployment Selection window, choose Cisco Unified Communications Manager; then, choose OK.

Note

The window indicates which products are and or not supported by your hardware.

Note

The system supports migrating data from a Windows-based release only if you choose to install Cisco Unified Communications Manager.

Step 6

If software is currently installed on the server, the Overwrite Hard Drive window opens and displays the current software version on your hard drive and the version on the DVD. The window displays a reminder to run the Data Migration Assistant and store the TAR file in a remote location. Choose Yes to continue with the installation or No to cancel.

Caution

If you choose Yes on the Overwrite Hard Drive window, all existing data on your hard drive gets overwritten and destroyed. The Platform Installation Wizard window displays.

Step 7

Choose one of the following options:
• •

To enter software configuration information manually, then have the installation program install the configured software on the server, choose Proceed and continue with this procedure. To do either of the following tasks, choose Skip and continue with the “Entering Preexisting Configuration Information” section on page 24.
– To configure manually software that is preinstalled on your server. In this case you do not need

to install the software, but you must configure the preinstalled software.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

23

Upgrading Cisco Unified Communications Manager

– To install the software before manually configuring it. In this case the installation program

installs the software, then prompts you to configure it manually. This method might cause you to spend more time performing the installation than the other methods.

Note

You can choose Skip if you want to preinstall the application on all your servers first and then enter the configuration information at a later time.

Step 8

Choose the type of installation to perform by doing the following steps. See Table 1 for more information on installation options:
a.

In the Apply Patch window, choose one of the options:
• • •

To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the “Applying a Patch” section on page 25. To skip this step, choose No. To return to the previous window, choose Back.

b.

If you are upgrading the first node in a Cisco Unified Communications Manager cluster, in the Import Windows Data window, choose Yes. Continue with the “Upgrading the First Cisco Unified Communications Manager Node” section on page 29. If you are upgrading a subsequent node in a Cisco Unified Communications Manager cluster, in the Import Windows Data window, choose No.

c. Step 9

In the Basic Install window, choose Continue. Continue with the “Upgrading Subsequent Nodes in the Cluster” section on page 32.

Note

To perform a basic installation, that is, to install the application without importing Windows data, see Installing Cisco Unified Communications Manager.

Entering Preexisting Configuration Information
Start here if you have a server that has Cisco Unified Communications Manager preinstalled or if you chose Skip in the Platform Installation Wizard window.
Step 1 Step 2

After the system restarts, the Preexisting Installation Configuration window displays. If you have preexisting configuration information that is stored on a floppy disc or a USB key, insert the disc or the USB key now and choose Continue. The installation wizard will read the configuration information during the installation process.

Note

If a popup window states that the system detected new hardware, press any key and then choose Install from the next window.

The Platform Installation Wizard window displays.
Step 3

To continue with the Platform Installation Wizard, choose Proceed.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

24

OL-12536-01

Upgrading Cisco Unified Communications Manager

Step 4

Choose the type of installation to perform by doing the following steps. See Table 1 for more information on installation options:
a.

In the Apply Additional Release window, choose one of the options:
• • •

To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the “Applying a Patch” section on page 25. To skip this step, choose No. To return to the previous window, choose Back.

b.

In the Import Windows Data window, choose Yes. Continue with the “Upgrading the First Cisco Unified Communications Manager Node” section on page 29.

Note

To perform a basic installation, that is, to install the application without importing Windows data, see Installing Cisco Unified Communications Manager.

Applying a Patch
If you choose Yes in the Apply Patch window, the installation wizard installs the software version on the DVD first and then restarts the system. You must obtain the appropriate upgrade file from Cisco.com before you can upgrade during installation.

Note

You can upgrade to any higher release, as long as you have a full patch, not an ES or an SR in which case you can only upgrade to a later service release of the same number. If you are upgrading from Cisco Unified Communications Manager Release 5.x, the upgrade file name has the following format:
cisco-ipt-k9-patchX.X.X.X-X.tar.gz.sgn

Where X.X.X.X-X represents the release and build number.

Note

Do not rename the patch file before you install it because the system will not recognize it as a valid file.

Note

Do not unzip or untar the file. If you do, the system may not be able to read the upgrade files. If you are upgrading from Cisco Unified Communications Manager Release 6.x, the upgrade file has the extension sgn.iso. You can access the upgrade file during the installation process from either a local disk (CD or DVD) or from a remote FTP or TFTP server.

Note

You can only apply one patch during the installation process.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

25

Upgrading Cisco Unified Communications Manager

Procedure
Step 1

After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed. The Upgrade During Install window displays.

Note

If the installer pops up a window that states that it detected new hardware, press any key and then choose Install from the next window.

Step 2

Choose Yes. The Install Upgrade Retrieval Mechanism Configuration window displays.

Step 3

Choose the upgrade retrieval mechanism to use to retrieve the upgrade file:
• • •

SFTP—Retrieves the upgrade file from a remote server by using the Secure File Transfer Protocol (SFTP). Skip to the “Upgrading From a Remote Server” section on page 27. FTP—Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the “Upgrading From a Remote Server” section on page 27. LOCAL—Retrieves the upgrade file from a local CD or DVD. Continue with the “Upgrading from a Local Disk” section on page 26.

Upgrading from a Local Disk
Before you can upgrade from a local disk, you must download the appropriate patch file from Cisco.com and copy the file to a CD or DVD. Because of the size of the patch files, you will need to copy it to a DVD in most cases.
• •

If you are using an upgrade file with the tar.gz.sgn extension, copy the upgrade file to a writeable CD or DVD. If you are using an upgrade file with the sgn.iso extension, you must create an ISO image on the DVD from the upgrade file.

Step 1

When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and choose OK.

Note

You only need to enter the patch directory when the patch is not stored in the root directory of the CD or DVD. If the patch is stored in the root directory, enter a slash (/) in the directory field.

Note

This step does not apply if you are using an upgrade file with the sgn.iso extension.

The Install Upgrade Patch Selection Validation window displays.
Step 2 Step 3

The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue. Choose the upgrade patch to install. The system installs the patch, then restarts the system by running the upgraded software version.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

26

OL-12536-01

Upgrading Cisco Unified Communications Manager

After the system restarts, the Preexisting Configuration Information window displays.
Step 4

To continue the installation, choose Proceed. The Platform Installation Wizard window displays. To continue the installation, choose Proceed or choose Cancel to stop the installation. If you choose Proceed, the Apply Patch window displays. Continue with Step 11. If you choose Cancel, the system halts, and you can safely power down the server. When the Apply Patch window displays, choose No.

Step 5

Step 6

Note Step 7 Step 8

You can only apply one patch during the upgrade process. The Windows Upgrade window displays. Choose No and continue with the upgrade procedure for the type of node that you are installing.
• •

“Upgrading the First Cisco Unified Communications Manager Node” section on page 29 “Upgrading Subsequent Nodes in the Cluster” section on page 32

Upgrading From a Remote Server
If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure the network settings.
Step 1 Step 2

The Auto Negotiation Configuration window displays. The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.

Note •

To use this option, your hub or Ethernet switch must support automatic negotiation. To enable automatic negotiation, choose Yes. The MTU Configuration window displays. Continue with Step 4. To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays. Continue with Step 3.

• Step 3

If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue. The MTU Configuration window displays. In the MTU Configuration window, you can change the MTU size from the operating system default. The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value.

Step 4

Caution

If you configure the MTU size incorrectly, be aware that your network performance can be affected.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

27

Upgrading Cisco Unified Communications Manager

• •

To accept the default value (1500 bytes), choose No. To change the MTU size from the operating system default, choose Yes, enter the new MTU size, and choose OK.

The DHCP Configuration window displays.
Step 5

For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP).
• •

If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The system restarts and checks for network connectivity. Skip to Step 8. If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.

Step 6

If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 5 for field descriptions. The DNS Client Configuration window displays. To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 5 for field descriptions. After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.

Step 7

Step 8

Enter the location and login information for the remote file server. See Table 5 for field descriptions. After the network restarts, the system connects to the remote server and retrieves a list of available upgrade patches. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax. The following are examples:
• •

Begin the pathname with a forward slash (/), and use forward slashes throughout the pathname. The pathname must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute pathname, which starts with a drive letter (for example, C:).

If you encounter problems, check with your system administrator for the correct directory path. The Install Upgrade Patch Selection window displays.
Step 9

Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system by running the upgraded software version. After the system restarts, the Preexisting Configuration Information window displays. To continue the installation, choose Proceed. The Platform Installation Wizard window displays.

Step 10

Step 11

To continue the installation, choose Proceed or choose Cancel to stop the installation. If you choose Proceed, the Apply Patch window displays. Continue with Step 11. If you choose Cancel, the system halts, and you can safely power down the server.

Step 12

When the Apply Patch window displays, choose No.

Note

You can only apply one patch during the upgrade process.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

28

OL-12536-01

Upgrading Cisco Unified Communications Manager

Step 13 Step 14

The Windows Upgrade window displays. Choose No and continue with the procedure for the type of node that you are installing.
• •

“Upgrading the First Cisco Unified Communications Manager Node” section on page 29 “Upgrading Subsequent Nodes in the Cluster” section on page 32

Upgrading the First Cisco Unified Communications Manager Node
When you choose Windows Upgrade, the installation wizard prompts you for the location of the preexisting Windows configuration information that the Data Migration Assistant (DMA) tool created. See the Data Migration Assistant User Guide for more information on the DMA tool.
Step 1

In the Windows Upgrade window, import data from a Windows version of Cisco Unified Communications Manager by choosing Yes. The Timezone Configuration window displays.

Step 2

Choose the appropriate time zone for the server and then choose OK. The Auto Negotiation Configuration window displays. The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.
•

Step 3

To enable automatic negotiation, choose Yes. The MTU Configuration window displays. Continue with Step 5.

Note • Step 4

To use this option, your hub or Ethernet switch must support automatic negotiation.

To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.

If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue. The MTU Configuration window displays. In the MTU configuration window, you can change the MTU size from the operating system default. The maximum transmission unity (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value, which is 1500 bytes.

Step 5

Caution

If you configure the MTU size incorrectly, be aware that your network performance can be affected.
• •

To accept the default value (1500 bytes), choose No. To change the MTU size from the operating system default, choose Yes, enter the new MTU size, and choose OK.

The DHCP Configuration window displays.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

29

Upgrading Cisco Unified Communications Manager

Step 6

For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP).
• •

If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The Administrator Login Configuration window displays. Continue with Step 9. If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.

Step 7

If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 5 for field descriptions. The DNS Client Configuration window displays.

Step 8

To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 5 for field descriptions. The Administrator Login Configuration window displays. Enter your administrator login and password from Table 5.

Step 9

Note

The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System.

The Certificate Signing Request Information window displays.
Step 10

Enter your certificate signing request information from Table 5 and choose OK. The First Node Configuration window displays.

Step 11

You must configure this node as the first node in the cluster. To continue, choose Yes. The Network Time Protocol Client Configuration window displays. Choose whether you want to configure an external NTP server or manually configure the system time.

Step 12

Note

Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure that the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node. To set up an external NTP server, choose Yes and enter the IP address, NTP server name, or NTP server pool name for at least one NTP server. You can configure up to five NTP servers, and Cisco recommends that you use at least three. To continue with the installation, choose Proceed. The system contacts an NTP server and automatically sets the time on the hardware clock.

•

Note

If have already entered the network configuration information and the system has rebooted (a Skip installation), the Test button displays. You can choose Test to check whether the NTP servers are accessible.

•

To manually configure the system time, choose No and enter the appropriate date and time to set the hardware clock. Choose OK to continue with the installation.

The Database Access Security Configuration window displays.
Step 13

Enter the Database Access Security password from Table 5.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

30

OL-12536-01

Upgrading Cisco Unified Communications Manager

Note

The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. Be sure that you save the Database Access security passowrd. You must enter the same password on all nodes in the cluster.

The SMTP Host Configuration window displays.
Step 14

If you want to configure an SMTP server, choose Yes and enter the SMTP server name.

Note

You must configure an SMTP server to use certain operating system features; however, you can also configure an SMTP server later by using the operating system GUI or the command line interface.

Step 15

Choose OK. The DMA Retrieval Mechanism Configuration window displays. Choose the mechanism that will be used to retrieve the DMA file:
– SFTP—Retrieves the DMA file from a remote server by using Secure File Transfer Protocol

Step 16

(SFTP). The SFTP server must support the following commands: cd, ls, get.
– FTP—Retrieves the DMA file from a remote server by using File Transfer Protocol (FTP). The

FTP server must support the following commands: cd, bin, dir and get.
– TAPE—Retrieves the DMA file from a locally attached tape drive.

Note

To support retrieval of the DMA file, an FTP server should support the cd, bin, dir, and get commands, and an SFTP server should support cd, ls, and get commands.

To continue with the installation wizard, choose OK.

Note

If you choose SFTP or FTP, the DMA Backup Configuration window displays, and you must enter the location of the DMA file and the login information for the remote server. If you choose TAPE, the system reads the DMA file from the locally attached tape.

Note

The system does not verify filename, path, or credentials until after the installation begins. If the system detects that you provided incorrect data, a prompt displays that allows you to reenter the information. This prompt may display up to 45 minutes after installation begins.

Step 17

If you chose SFTP or FTP, enter the DMA Backup Configuration information and choose OK. If the DMA file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax. The following are examples:
• •

Begin the pathname with a forward slash (/), and use forward slashes throughout the pathname. The pathname must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute pathname, which starts with a drive letter (for example, C:).

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

31

Upgrading Cisco Unified Communications Manager

If you encounter problems, check with your system administrator for the correct directory path. The Platform Configuration Confirmation window displays.
Step 18

To continue with the installation, choose OK or choose Back to modify the platform configuration. When you choose OK, the Application User Password Configuration window displays. Enter the Application User Name and Application User Password from Table 5 and confirm the password by entering it again. Choose OK. The End User Password/PIN Configuration window displays. Enter and confirm the End User Password and PIN and choose OK. The end user password must comprise five or more alphanumeric or special characters. The end user PIN must comprise five or more numeric characters. The system installs the software, restarts the network, and reads the DMA file that you specified. The DMA Retrieval Mechanism Configuration window displays. To continue, choose OK, or to choose a different DMA file, choose Back. The installation begins. The installation program assigns a Host Name/ IP Address (Servername) to the 6.1(1) server by comparing the value in the DMA file to the value that is configured on the 6.1(1) system. For more information, refer to the “Assigning the Host Name/IP Address (Servername) to the 6.1(1) Server” section on page 20.

Step 19 Step 20

Step 21

Step 22 Step 23

Step 24

After the installation has proceeded for approximately 30 minutes, the system compares host name/IP address (Server name) in the DMA file to the value that is configured on the 6.1(1) system. If a mismatch exists between these values, you are prompted to Proceed or Cancel. Select Proceed to proceed with the installation by using the Host Name/ IP Address (Servername) that the installation program assigned, or choose Cancel to cancel the installation.

Step 25

If no mismatch exists, or you select Proceed, the Product Licensing window displays with information regarding how to obtain a license. The installation continues automatically. The DVD drive ejects, and the server reboots. Do not reinsert the DVD. When the installation process completes, you get prompted to log in by using the Administrator account and password. Complete the post-upgrade tasks that are listed in the “Post-Upgrade Tasks” section on page 34.

Step 26 Step 27

Upgrading Subsequent Nodes in the Cluster
Use this procedure to continue installing Cisco Unified Communications Manager on a subsequent node in your cluster. Before you complete this section, you must have installed the operating system, as described in the “Starting the Installation” section on page 21.
Step 1

When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK. The Auto Negotiation Configuration window displays.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

32

OL-12536-01

Upgrading Cisco Unified Communications Manager

Step 2

The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.
•

To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.

Note • Step 3

To use this option, your hub or Ethernet switch must support automatic negotiation.

To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.

If you chose to disable automatic negotiation, manually choose the appropriate NIC Speed and Duplex settings now and choose OK to continue. The DHCP Configuration window displays. For network configuration, you can choose to either set up static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP).
• •

Step 4

If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The network restarts, and the Administrator Login Configuration window displays. If you want to configure static IP address for the node, choose No. The Static Network Configuration window displays.

Step 5

If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 5 for field descriptions. The DNS Client Configuration window displays. To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 5 for field descriptions. The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.

Step 6

Step 7

Enter your Administrator login and password from Table 5.

Note

The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System.

The Certificate Signing Request Information window displays.
Step 8

Enter your certificate signing request information from Table 5 and choose OK. The First Node Configuration window displays.

Step 9

To configure this server as a subsequent node in the cluster, choose No. The First Node Access Configuration window displays. Enter the First Node Access Configuration information from Table 5. The SMTP Host Configuration window displays. If you want to configure an SMTP server, choose Yes and enter the SMTP server name.

Step 10

Step 11

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

33

Post-Upgrade Tasks

Note

You must configure an SMTP server to use certain platform features; however, you can also configure an SMTP server later by using the platform GUI or the command line interface.

The Platform Configuration Confirmation window displays.
Step 12

To start installing the software, choose OK, or if you want to change the configuration, choose Back. When the installation process completes, you get prompted to log in by using the administrator account and password.

Step 13 Step 14

To log in, enter the administrator account name and password that you entered during installation. Complete the post-upgrade tasks that are listed in the “Post-Upgrade Tasks” section on page 34.

Post-Upgrade Tasks
When you complete your upgrade of Cisco Unified Communications Manager, you must perform all appropriate tasks as described in the following table:
Table 7 Post-Upgrade Tasks

Post-Upgrade Tasks Upgrade your product licenses. Verify that all appropriate Cisco Unified Communications Manager services started. Verify that you can make internal calls. Verify that you can place and receive a call across gateways.

Important Notes See the “Upgrading Product Licenses” section on page 39. Refer to the Cisco Unified Serviceability Administration Guide See the “Verifying Cisco Unified Communications Manager Services” section on page 40.

If security is enabled on the cluster, you must To configure CTL on the upgraded cluster, configure CTL. 1. Uninstall the existing CTL client.
2. 3. 4. 5.

Install the new CTL client. Run the CTL client by using at least one of the previously used USB keys. Update the new CTL file on all nodes. Restart all nodes.

For information about performing these tasks and about Cisco Unified Communications Manager security, refer to the Cisco Unified Communications Manager Security Guide. Using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT), make sure that all the registration information values match the values that you recorded before the server replacement. See the “Determining Registration Counts by Using RTMT” section on page 10.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

34

OL-12536-01

Post-Upgrade Tasks

Table 7

Post-Upgrade Tasks (continued)

Post-Upgrade Tasks

Important Notes

Using the Cisco Unified Communications See the “Recording Critical Service Status” section on Manager Real-Time Monitoring Tool page 11. (RTMT), make sure that all the critical services and their status match those that you recorded before the server upgrade. Using the Syslog viewer in the Cisco Unified Perform this task to ensure that no system-affecting Communications Manager Real-Time errors exist on your system. Monitoring Tool (RTMT), locate any events See the “Locating System Errors by Using Syslog that have a severity of Error or higher. Viewer” section on page 11. Using the Syslog viewer in the Cisco Unified To access the appropriate object and counter, use the Communications Manager Real-Time following procedure: Monitoring Tool (RTMT), check the 1. Perform one of the following tasks: Replicate_State counter for the Number of • In the Quick Launch Channel, click System, click Replicates Created and State of Replication Performance; and then, click the Performance object on all nodes. The value on each node icon. should equal 2. This counter represents the state of replication, which includes the following possible values: This counter represents the state of replication. The following list provides possible values:
• • 2. 3. 4. 5.

Choose System > Performance > Open Performance Monitoring. Double-click the name of the server where you want to add a counter to monitor. Double-click the Number of Replicates Created and State of Replication object. Double-click the Replicate_State counter. Choose the ReplicateCount instance and click Add.

0—Initializing. The counter equals 0 when the server is not defined or when the server is defined but the realize template has not completed. 1—The system created replicates of some tables but not all tables. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure. 2—Good Replication. 3—Bad Replication. When the counter displays a value of 3, consider replication in the cluster as bad. It does not mean that replication failed on a particular node. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure. 4—Replication setup did not succeed.

•

• •

•

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

35

Post-Upgrade Tasks

Table 7

Post-Upgrade Tasks (continued)

Post-Upgrade Tasks From Cisco Unified Communications Manager Administration, make sure that the number of phones, gateways, trunks, users, and route patterns that are configured in the database matches the numbers that you recorded before the server replacement. From the Firmware Load Information window in Cisco Unified Communications Manager Administration, make sure that the phone load and device type values match those that you recorded before the server upgrade.

Important Notes See the “Determining System Configuration Counts” section on page 13.

If a device type is missing, you may need to reinstall the COP file enabler for that type. Then, reboot the cluster and start post-upgrade checklist again. See the “Firmware Information” section on page 14.

Compare the system version on each node in See the “Obtaining System Version Information” your cluster by using Cisco Unified section on page 14. Communications Operating System Administration and make sure that each node runs the same version. Reconfigure CDR destinations, if applicable. See the “Accessing CDR Management Configuration” section on page 12. Reconfigure all Trace and Log Central jobs. Perform any system tests that you performed before the upgrade and verify that all test calls succeed. Configure the backup settings. Remember to back up your Cisco Unified Communications Manager data daily. The locale, English_United_States, installs automatically on the server. If required, you can add new locales to the server. Cisco recommends that you implement authentication and encryption in your Cisco IP Telephony network. Refer to the Disaster Recovery System Administration Guide. Refer to the Cisco Unified Communications Operating System Administration Guide. Refer to the Cisco Unified Communications Manager Security Guide. See the “Recording Trace and Log Central Job Details” section on page 12.

If you are using Microsoft Active Directory or For more information on directories, refer to the Cisco Netscape Directory, enable synchronization Unified Communications Manager Security Guide. with the LDAP server. For more information on enabling synchronization, refer to the Cisco Unified Communications Manager Administration. Upgrade subscriber servers as subsequent Cisco Unified Communications Manager nodes in the cluster. Subscriber servers automatically get defined as subsequent nodes in the database. Remember to enter the same security password for the first node. See the “Upgrading Subsequent Nodes in the Cluster” section on page 32

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

36

OL-12536-01

Post-Upgrade Tasks

Table 7

Post-Upgrade Tasks (continued)

Post-Upgrade Tasks If necessary, you can add additional, subsequent nodes to the cluster.

Important Notes You must add additional subsequent nodes to the cluster by performing the following tasks:
1.

Define all subsequent nodes in the cluster by adding the host name or IP address of subsequent Cisco Unified Communications Manager nodes to Cisco Unified Communications Manager Administration. For more information, refer to Cisco Unified Communications Manager Administration Guide. Install the new application and configure subsequent Cisco Unified Communications Manager nodes in the cluster. See the “Upgrading Subsequent Nodes in the Cluster” section on page 32.

2.

Remember to enter the same security password that you used for the first node. Reinstall customer background images, custom TFTP files, custom MoH files, and customer ring tones. To upload these files, log in to Cisco Unified Communications Operating System Administration and navigate to the Software Upgrades>Upload TFTP Server File menu. See the Cisco Unified Communications Operating System Administration Guide for more information. Install the required client-side plug-ins, such as Cisco Unified Communications Manager Real-Time Monitoring Tool and Cisco Unified Communications Manager Attendant Console. Inform end users that they must reconfigure their ring tones and background images after the upgrade. From Cisco Unified Communications Manager Administration, choose Application>Plugins. For more information, see the Cisco Unified Communications Manager Administration Guide. These settings do not get migrated.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

37

Post-Upgrade Tasks

Upgrading Product Licenses
When you upgrade from supported Cisco Unified CallManager Manager 4.x releases, the system calculates the licenses that are required for existing devices and nodes and generates an intermediate file (XML file) that contains this information. You use this file to obtain license files that you can upgrade into Cisco Unified Communications Manager Administration. You receive these licenses free of cost because you are already using these phones for a Cisco Unified CallManager 4.x release. Use the following procedure to obtain licenses for Cisco Unified Communications Manager when you are upgrading from supported 4.x releases.
Procedure
Step 1

After you complete the Cisco Unified Communications Manager upgrade process, navigate to Cisco Unified CallManager Administration and choose System > Licensing > License File Upload. The License File Upload window displays. Choose the license XML file from the Existing Files drop-down list, and click View File. The window refreshes and displays the information for the selected license. Copy this information. To copy the contents on this window, you can use Ctrl-A (Select All) and Ctrl-C (Copy). Navigate to the License Registration web tool at https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet?FormId=806. Enter the MAC address of the Ethernet 0 NIC of the first node of the Cisco Unified Communications Manager cluster. In the text box that is provided, paste the license file contents that you copied in Step 2 by using the appropriate keyboard shortcuts, such as Ctrl-V. Enter a valid e-mail address and click Continue. A license file generates. The system sends the license file to you via e-mail using the e-mail address that you provided. You must upload the license file to the server with the matching MAC address that you provided in Step 4. See the “Upgrading Product Licenses” section on page 39. You can obtain licenses for new devices that you are adding to the upgraded system, if your system requires additional device license units. For more information, refer to the document Installing Cisco Unified Communications Manager.

Step 2

Step 3 Step 4 Step 5 Step 6

Step 7 Step 8

Related Topics

Post-Upgrade Tasks, page 34

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

38

OL-12536-01

Using the Disaster Recovery Disc

Verifying Cisco Unified Communications Manager Services
To access Cisco Unified Communications Manager Administration or Cisco Unified Serviceability, you will need to use a web browser from a PC with network access to the Cisco Unified Communications Manager server. To review service activation procedures and service recommendations, refer to theCisco Unified Serviceability Administration Guide.
Related Topics

Post-Upgrade Tasks, page 34

Using the Disaster Recovery Disc
In case of a system emergency, you can use the Disaster Recovery disc to revert to a Windows-based version of Cisco Unified Communications Manager or to force the system to restart on the inactive partition. The recovery disk can be used to try to recover a system when a system is completely unrecoverable in all other ways. When you boot the server from the recovery disk, the following options display:
•

[S]|[s]—Swaps the active and inactive partitions. This option only appears if a valid inactive partition exists. With the firmware leveling feature, this option also configures (flashes) RAID and BIOS firmware and settings. For more information on this option, see the “Switching Partitions” section on page 41. [W]|[w]—Windows pre-installation setup. This option wipes out the master boot record so that the Windows operating system can be installed. This option also reverts the BIOS settings to factory defaults. For more information on using this option to revert to a previous version, see the “Reverting to a Previous Version of Cisco Unified Communications Manager” section on page 40. [F]|[f] and [M][m]—These options check and automatically correct disk file systems. Cisco recommends that you run option [F] before [M] to allow the system to automatically try to fix any disk file system issues. [V]|[v] Verify the disk partitioning layout. [Q]|[q] Quit this recovery disk program.

•

•

• •

Reverting to a Previous Version of Cisco Unified Communications Manager
If the upgrade from Cisco Unified Communications Manager 4.x to Cisco Unified Communications Manager 6.1(1) is unsuccessful, you can use the Disaster Recovery Disc to revert to a Windows-based version of Cisco Unified Communications Manager.

Caution

If you revert to a previous version of Cisco Unified Communications Manager, you will lose any configuration changes that you made by using Cisco Unified Communications Manager 6.1(1). To use the Disaster Recovery Disk, use this procedure:

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

39

Using the Disaster Recovery Disc

Procedure
Step 1 Step 2 Step 3

Insert the Disaster Recovery disc and restart the system, so it boots from the CD. After the server completes the boot sequence, the Disaster Recovery menu displays. For Windows preinstallation setup, enter W. To continue, enter Yes.

Caution

If you continue, you will lose all the data that is currently on your hard drive. The Disaster Recovery disc formats your hard drive, so you can reinstall a Windows-based version of Cisco Unified Communications Manager.

Step 4

Following the instructions in the installation guide for your Windows-based version of Cisco Unified Communications Manager, install Cisco Unified Communications Manager on the publisher server first and then on the subscriber nodes. Using the Backup and Restore Utility, restore the previously backed-up data to the servers. For more information, see the Backup and Restore Utility documentation for your version of BARS.

Step 5

Switching Partitions
If the system cannot start on the current partition, you can use the Disaster Recovery disc to force it to switch to the inactive partition and start running the software version on that partition.

Caution

If you force the system to restart on the inactive partition, you will lose any configuration changes that you made after you upgraded to the current partition. To force the system to switch partitions and restart, follow this procedure:
Procedure

Step 1 Step 2 Step 3

Insert the Disaster Recovery disc and restart the system, so it boots from the CD. After the server completes the boot sequence, the Disaster Recovery menu displays. To restart the server, so it is running the software on the currently inactive partition, enter S. Press Enter. The server restarts.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

40

OL-12536-01

Examining Log Files

Examining Log Files
If you encounter problems with the installation, you can obtain and examine the install log files by entering the following commands in Command Line Interface. To obtain a list of install log files from the command line, enter
CLI>file list install

To view the log file from the command line, enter
CLI>file view install log_file

where log_file is the log file name. You can also view logs by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT). For more information on using and installing the Cisco Unified Communications Manager RTMT, refer to the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.

Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.

CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0710R) Copyright © 2007.Cisco Systems, Inc. All rights reserved.

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases OL-12536-01

41

Obtaining Documentation, Obtaining Support, and Security Guidelines

Upgrading to Cisco Unified Communications Manager Release 6.1(1) from Cisco Unified Communications Manager 4.x Releases

42

OL-12536-01


								
To top