Guest

Cisco Unified Communications Manager (CallManager)

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

  • Viewing Options

  • PDF (614.9 KB)
  • Feedback
Upgrading to Cisco Unified Communications Manager Release 6.0(1) from Cisco Unified Communications Manager 4.x Releases

Table Of Contents

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

Purpose of this Document

Contents

Installation Overview

Related Documentation

Important Considerations

Preparing To Upgrade

Frequently Asked Questions About the Cisco Unified Communications Manager Installation

What Passwords do I Need to Specify?

Which servers does Cisco support for this installation?

May I install other software besides Cisco Unified Communications Manager on the server?

Browser Requirements

Configuring the Hardware

Performing Pre-Upgrade Tasks

Gathering Information for an Installation

Handling Network Errors During Upgrade

Selecting an Installation Option

Assigning the Host Name/IP Address (Servername) to the 6.0(1) Server

Using the Cisco Unified Communications Answer File Generator

Upgrading Cisco Unified Communications Manager

Navigating Within the Installation Wizard

Starting the Installation

Entering Preexisting Configuration Information

Upgrading During Installation

Upgrading From a Local Disk

Upgrading From a Remote Server

Upgrading the First Cisco Unified Communications Manager Node

Upgrading Subsequent Nodes in the Cluster

Post-Upgrade Tasks

Verifying Cisco Unified Communications Manager Services

Using the Disaster Recovery Disc

Reverting to a Previous Version of Cisco Unified Communications Manager

Switching Partitions

Examining Log Files

Obtaining Documentation, Obtaining Support, and Security Guidelines


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


The 6.0(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.0(1), review all upgrade instructions carefully.

Purpose of this Document

This document describes how to upgrade to Cisco Unified Communications Manager 6.0(1) from a Cisco Unified Communications Manager 4.x release.

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.

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.

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

Installation Overview

Cisco Unified Communications Manager 5.x 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.0(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
Description

Basic Install

This option represents the basic Cisco Unified Communications Manager 6.0(1) installation, which installs the software from the installation disc and does not use any imported data.

Upgrade During Install

This option allows you to upgrade the software version that the installation disc contains with a later release. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process.

Note Ensure that you have the software image available on DVD or on a remote server prior to choosing this option.

Windows Upgrade

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.

Note Before upgrading from a Windows-based release, ensure you have all software licenses ready to ensure successful operation after the upgrade.



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
URL

Cisco MCS data sheets

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

Software-only servers (IBM, HP, Compaq, Aquarius)

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

Cisco Unified Communications Manager service releases

http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml


Important Considerations

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

Be aware that when you install Cisco Unified Communications Manager 6.0(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.

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

The demo license feature that is introduced in release 6.0(1) is not available when you upgrade from a previous product version.

Directory names and filenames that you enter while running the installation program are case-sensitive.

Carefully read the instructions that follow before you proceed with the installation.

Preparing To Upgrade

This section describes how to prepare to upgrade from a Cisco Unified Communications Manager release older than release 5.0 to release 6.0(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.

What Passwords do I Need to Specify?

During the Cisco Unified Communications Manager upgrade, you must specify the following user names and passwords:

Administrator account

You use the Administrator username and password to log in to the following areas:

Platform Administration

Disaster Recovery System

Command Line Interface

The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You can change the Administrator password or add a new Administrator account by using the command line interface. See the Cisco Unified Communications Operating System Administration Guide for more information.

Application User password

You use the Application User password for as the default password for applications that are installed on the system.

You can change the application user password for each application in Cisco Unified Communications Manager Administration. See the Cisco Unified Communications Manager Administration Guide for more information.

Database Access Security Password

The system uses this password to authorize communications between nodes, and this password must be the same on all nodes in the cluster.

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.

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.


Which servers does Cisco support for this installation?

To find which servers support Cisco Communications Manager 5.0 and later releases, refer to the Guide to Cisco Communications Manager Upgrades and Server Migrations 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?

For Cisco Unified Communications Manager 6.0(1), you must do all software installations and upgrades by using the Software Upgrades menu options in Platform 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.0(1).

Browser Requirements

You can access Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and Cisco Unified Communications Operating System Administration 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.


Table 3 BIOS Configuration Settings for HP and IBM Servers 

HP Servers
IBM Servers

OS Selection: Linux (not applicable on newer models)

OS Selection: Not applicable

Boot order: CD, C:, Floppy

Boot order: CD, C:, Floppy

Post F1 prompt: Delayed

Post F1 prompt: Delayed

Hyperthreading: Enabled

Hyperthreading: Enabled


Table 4 RAID Settings

MCS 7825 Servers (HP and IBM)
MCS 7835 Servers (HP and IBM)
MCS 7845 Servers (HP and IBM)

Software RAID

Logical drives: 1

Logical drives: 2

Software RAID

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

RAID type: 1(1+0)

RAID type: 1(1+0)


Performing Pre-Upgrade Tasks

Perform the following tasks before you begin the upgrade:

 
Pre-Upgrade Task
Important Notes

Step 1 

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

See the "Which servers does Cisco support for this installation?" section.

Step 2 

Ensure the Cisco Unified Communications Manager server with the publisher database is configured as the first node and Cisco Unified Communications Manager servers with subscriber databases are configured as subsequent nodes.

 

Step 3 

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

Refer to Using Cisco Unified Communications Manager Upgrade Utility.

Step 4 

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

Refer to Backup and Restore Utility Administration Guide.

Step 5 

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

For more information on CAR, refer to the Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide.

Step 6 

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

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

Step 7 

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

DMA generates two files:

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

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

Note Do not do anything with the D:\DMA\DMABackupInfo.inf file.

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

Step 8 

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

See the "Gathering Information for an Installation" section.

Step 9 

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

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

For more information, see the "Assigning the Host Name/IP Address (Servername) to the 6.0(1) Server" section

Step 10 

Familiarize yourself with the navigation options within the installation wizards.

See "Navigating Within the Installation Wizard" section.

Step 11 

Obtain licenses for Cisco Unified Communications Manager 6.0 before upgrading to this release. You must import your new licenses after upgrading to Cisco Unified Communications Manager 6.0 to enable the system.

Refer to Cisco Unified Communications Manager Administration Guide for information about licensing and obtaining licenses.

Step 12 

Stop Cisco Security Agent for Cisco Unified Communications Manager (CSA).

 

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 platform administration or through the Command Line Interface (CLI).

Table 5 Configuration Data 

Configuration Data
Your Entry
Can Entry Be Changed After Installation

Administrator Password

 

Yes

CLI: set password admin

Application User Password

 

Yes

CLI: set password

Country

 

Yes

CLI: set web-security

DHCP

 

Yes

CLI: set network dhcp

DNS Primary

 

Yes

CLI: set network dns

DNS Secondary

 

Yes

CLI: set network dns

Domain

 

Yes

CLI: set network domain

Domain Name Service DNS Enable

 

No

Gateway Address

 

Yes.

Use Platform Administration > Settings>IP

or

CLI: set network gateway

Host Name

 

No

IP Address

 

Yes

Use Platform Administration >Settings>IP

or

CLI: set network IP

IP Mask

 

Yes.

Use Platform Administration > Settings>IP

or

CLI:> set network ip eth0

Location

 

Yes

CLI: set web-security

Master Administrator ID

 

No

NTP Server IP Address

Note You can enter up to five NTP servers.

 

Yes

Use Platform Administration > Settings>NTP Servers

Organization

 

Yes

CLI: set web-security

Security Password

 

Yes

CLI: set password security

SMTP Location

 

Yes

CLI: set smtp

State

 

Yes

CLI: set web-security

Time Zone

 

Yes

CLI: set timezone

Unit

 

Yes

CLI: set web-security

End-User Password

 

Yes

Refer to Cisco Unified Communications Manager Administration Guide.

End-User PIN

 

Yes

Refer to Cisco Unified Communications Manager Administration Guide.


For more detailed descriptions of each installation field, see Table 6.

Table 6 Installation Field Definitions 

Field
Description
Usage

Administrator ID

This field specifies the name that you want to assign to this account.

Ensure the name is unique; it can contain lowercase, alphanumeric characters, hyphens, and underscores. It must start with a lowercase alphanumeric character.

For this mandatory field, you should record it for use when you log in to the CLI on the platform or into Platform Administration.

Note You cannot change this field after installation.

Administrator Password

This field specifies the password that you use for logging in to Cisco Unified Communications Operating System Administration and the CLI.

Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.

For this mandatory field, you should record it for use when you log in to the Cisco Unified Communications Manager.

DHCP

Dynamic Host Configuration Protocol

Choose Yes if you want to use DHCP to automatically configure the network settings on your server.

If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway.

DNS Enabled

A DNS server represents a device that resolves a hostname into an IP address or an IP address into a hostname.

If you do not have a DNS server, enter No. When DNS is not enabled, you should only enter IP addresses (not hostnames) for all network devices in your Cisco Unified Communications network.

If you have a DNS server, Cisco recommends entering Yes to enable DNS. Disabling DNS limits the system ability to resolve some domain names.

DNS Primary

Cisco Unified Communications Manager contacts this DNS server first when it attempts to resolve host names.

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 where ddd can have a value between 0 and 255 (except 0.0.0.0).

Consider this field mandatory if DNS is set to yes.

DNS Secondary

When a primary DNS server fails, Cisco Unified Communications Manager will attempt to connect to the secondary DNS server.

In this optional field, enter the IP address of the secondary DNS. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).

Domain

This field represents the name of the domain in which this machine is located.

Consider this field mandatory if DNS is set to yes.

First Cisco Unified Communications Manager Node

The first Cisco Unified Communications Manager node contains the database.

Subsequent nodes connect to the the first node to access database content.

The first node also synchronizes with an external NTP server and provides time to the other nodes.

Choose Yes if you are configuring the first Cisco Unified Communications Manager node in the cluster.

If you are configuring subsequent nodes, see Table 6 for information on the different fields.

Gateway Address

A gateway represents a network point that acts as an entrance to another network. Outbound packets get sent to the gateway that will forward them to their final destination.

Enter the IP address of the gateway in the format ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0)

If you do not have a gateway, you must still fill in this field by setting it to 255.255.255.255. Not having a gateway may limit you to communicating only with devices on your subnet.

Hostname

A host name represents an alias that is assigned to an IP address to identify it.

Enter a host name that is unique to your network.

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.

IP Address

This field specifies the IP address of this machine. It will uniquely identify the server on this network. Another machine in this network should not be using this IP address.

Enter the IP address in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).

If DHCP is set to No, consider this field mandatory.

IP Mask

This field specifies the IP subnet mask of this machine. The subnet mask together with the IP address defines the network address and the host address.

Enter the IP mask in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).

A valid mask should have contiguous '1' bits on left side and contiguous '0' bits on the right.

For example, a valid mask follows: 255.255.240.0 (11111111.11111111.11110000.00000000)

An invalid mask follows: 255.255.240.240 (11111111.11111111.11110000.11110000)

NIC Speed

This field specifies the speed of the server network interface card (NIC) in megabits per second.

The possible speeds comprise 10 or 100.

NIC Duplex

This field specifies the duplex setting of the server NIC.

The possible settings comprise half and full.

NTP Server

This field identifies the NTP server with which you want to keep time synchronization.

Enter the hostname or IP Address of NTP server(s).

If you enabled the system to be NTP client, you must enter the hostname or IP address of at least one NTP server.

Note You can add additional NTP servers or make changes to the NTP server list at a later time

Security Password

Cisco Unified Communications Manager servers in the cluster use the security password to communicate with one another.

You will be asked to enter the same security password for each subsequent node in the cluster.

Enter the security password.

Enter the same password in the confirm password field.

The password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character.


Caution You must enter the same password for all nodes in the cluster.

Set Hardware Clock

The field specifies the date and local time for the machine.

Note If you set the hardware clock manually, the node does not use an external NTP server for time synchronization.

Choose Yes if you want to set the date and local time for the time zone that you chose.

Enter the hours based on a 24-hour format.

Note If you configure an external NTP server, the hardware clock gets set automatically.

SMTP

This field specifies the name of the SMTP host that is used for outbound e-mail.

Enter the hostname or dotted IP address for the SMTP server. For a host, it can contain alphanumeric characters, hyphens, or periods. For a host name, it must start with an alphanumeric character.

You must fill in this field if you plan to use electronic notification. If not, you can leave it blank.

Time zone

This field specifies the local time zone and offset from Greenwich Mean Time (GMT)

Choose Yes if you want to change the time zone.

Choose the time zone that most closely matches the location of your machine.


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.

Networking is validated after you complete each networking window, so 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.

Selecting an Installation Option

After the platform software installation starts, you will be asked to select one of the options that Table 7 lists.

Table 7 Installation Options 

Installation Options
Description

Basic Install

This option represents the basic installation and does not use any imported data.

Upgrade During Install

This option allows you to upgrade the preinstall software with the latest service release prior to configuring your system. You can also choose Upgrade During Install followed by the a Windows Upgrade and perform both during the installation process.

Note You must have the software image available on DVD or on a remote server prior to choosing this option.

Windows Upgrade

This option allows you to import the TAR file that the DMA tool produced while upgrading an existing Cisco Unified Communications Manager server.

Note If you choose to upgrade your server by using this option, you will need to provide the TAR file that contains the migrated data from the DMA tool on tape or a remote drive.


Assigning the Host Name/IP Address (Servername) to the 6.0(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.0(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.0(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.0(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 5.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 5.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 5.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.

This feature allows you to import your 4.x data to a 6.0(1) server without having to preserve the IP Address or Host Name. The IP Address and/or Host name of the 6.0(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.

Using the Cisco Unified Communications Answer File Generator

Cisco Unified Communications Answer File Generator is a web application that is used to generate answer files for unattended installations of Cisco Unified Communications Manager Business Edition. Individual answer files get copied to a USB key or a floppy diskette that accompanies the Cisco Unified Communications Manager Business Edition DVD during the installation process.

The web application supports the following features:

Allows simultaneous generation and saving of answer files for unattended installs on the publisher server and all subscriber servers.

Provides syntactical validation of data entries.

Provides online help and documentation.

The following usage requirements apply:

The web application supports only fresh installs (for example, it does not include upgrades).

If DHCP client is being used on the publisher server, and subscriber server answer files are also being generated, you must specify the publisher server IP address.

You can access the Cisco Unified Communications Answer File Generator at the following URL:

http://www.cisco.com/web/cuc_afg/index.html

The Cisco Unified Communications Answer File Generator supports Internet Explorer version 6.0 or higher and Mozilla version 1.5 or higher.

If a USB key is being used to perform an unattended installation of Cisco Unified Communications Manager Business Edition, you may need to reformat the USB key to the FAT32 file system beforehand. You need to reformat especially in the case of USB keys with larger storage capacity (for example, 1 Gigabyte) that are formatted with the FAT file system.

You can use the Windows XP Disk Management Utility to reformat a USB key to the FAT32 file system as follows (you might need to be logged in as an administrator or a member of the Administrators group to perform these tasks):


Step 1 Insert the USB key into a USB slot on the Windows XP PC.

Step 2 Choose Start > Control Panel > Administrative Tools and then double-click Computer Management.

Step 3 Expand the Storage tree and click Disk Management.

Step 4 Right-click the Removable Disk icon and click Format.

Step 5 You may be asked whether you are sure that you want to format this partition; click Yes.

Step 6 Click the File System: pull down and select FAT32.

Step 7 Click OK. When prompted to format the volume, click OK again.

The Removable Disk icon text should now show the file system format as FAT32.


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.0(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 8.

Table 8 Installation Wizard Navigation

To Do This
Press This

Move to the next field

Tab

Move to the previous field

Alt-Tab

Choose an option

Spacebar

Scroll up or down in a list

Up or down arrow

Go to the previous window

Space bar to choose Back (when available)

Get help information on a window

Space bar to choose Help (when available)


Starting the Installation


Step 1 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.

Step 2 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.


Note If you have a new server with Cisco Unified Communications Manager Business Edition preinstalled, you do not need to install from a DVD. Go directly to the "Entering Preexisting Configuration Information" procedure.


Step 3 If you choose Yes to perform the media check, the Media Check Result window displays. Perform these tasks:

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

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

Step 4 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, select the product to install; then, choose OK. You can choose from these options:

Cisco Unified Communications Manager

Cisco Unity Connection

Cisco Unified Communications Manager Business Edition (includes Cisco Unified Communications Manager and Cisco Unity Connection)


Note Only the products that are supported on your server appear in the list.



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. 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 To configure the platform now, choose Proceed. If you want to configure the platform later, choose Skip.

If you want to install and configure the software at this time, choose Proceed and continue with this procedure.

If you want to install the software now and configure it later or if you have a server that has Cisco Unified Communications Manager Business Edition preinstalled, choose Skip and continue with the "Entering Preexisting Configuration Information" section.

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 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 "Upgrading During Installation" section.

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.

c. If you are upgrading a subsequent node in a Cisco Unified Communications Manager cluster, in the Import Windows Data window, choose No.

Step 9 In the Basic Install window, choose Continue. Continue with the "Upgrading Subsequent Nodes in the Cluster" section.


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 Business Edition preinstalled or if you chose Skip in the Platform Installation Wizard window.


Step 1 After the system restarts, the Preexisting Installation Configuration window displays.

Step 2 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.

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 "Upgrading During Installation" section.

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.


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



Upgrading During Installation

If you choose Yes in the Upgrade During Install 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.

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.


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.

FTP—Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the "Upgrading From a Remote Server" section.

LOCAL—Retrieves the upgrade file from a local CD or DVD. Continue with the "Upgrading From a Local Disk" section.


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 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue.

Step 3 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system running the upgraded software version.

After the system restarts, the Preexisting Configuration Information window displays. Skip to the "Entering Preexisting Configuration Information" section.


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 The Auto Negotiation Configuration window displays.

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

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 DHCP Configuration window displays.

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

If you want to configure static IP addresses 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 6 for field descriptions.

The DNS Client Configuration window displays.

Step 6 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 6 for field descriptions.

After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.

Step 7 Enter the location and login information for the remote file server. See Table 6 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, check with your system administrator for the correct directory path.

The Install Upgrade Patch Selection window displays.

Step 8 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system running the upgraded software version.

After the system restarts, the Preexisting Configuration Information window displays. Continue with the "Entering Preexisting Configuration Information" section.

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, choose 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.

Step 3 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 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.

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

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. The Administrator Login Configuration window displays.

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 6 for field descriptions.

The DNS Client Configuration window displays.

Step 7 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 6 for field descriptions.

The Administrator Login Configuration window displays.

Step 8 Enter your administrator login and password from Table 5.

The Certificate Signing Request Information window displays.

Step 9 Enter your certificate signing request information and choose OK.

The First Node Configuration window displays.

Step 10 You must configure this node as the first node in the cluster. To continue, choose Yes.

The Network Time Protocol Client Configuration window displays.


Note Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. The external NTP server must be stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node.


Step 11 Choose whether you want to configure an external NTP server or manually configure the system time.

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.


Note If the Test button displays, you can choose Test to check whether the NTP servers that you entered are accessible.


The system contacts an NTP server and automatically sets the time on the hardware clock.

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 12 Enter the Database Access Security password from Table 5.


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. The system uses this password to authorize communications between nodes, and this password must be the same on all nodes in the cluster.


The SMTP Host Configuration window displays.

Step 13 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 platform features; however, you can also configure an SMTP server later by using the platform GUI or the command line interface.


The DMA Retrieval Mechanism Configuration window displays.

Step 14 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 (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.


Step 15 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 DMA file is located on a Windows server, check with your system administrator for the correct directory path.

The Platform Configuration Confirmation window displays.

Step 16 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.

Step 17 Enter the Application User Password from Table 5 and confirm the password by entering it again.

Step 18 Choose OK.

The End User Password/PIN Configuration window displays.

Step 19 Enter 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.

Step 20 To continue, choose OK, or to choose a different DMA file, choose Back.

When you choose OK, the Installation program assigns a Host Name/ IP Address (Servername) to the 6.0(1) server by comparing the value in the DMA file to the value that is configured on the 6.0(1) system. For more information, refer to the "Assigning the Host Name/IP Address (Servername) to the 6.0(1) Server" section.

Step 21 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 22 If no mismatch exists, or you select Proceed, the Platform Configuration Confirmation window displays.

Step 23 To continue, choose OK.

The DVD drive ejects and the server reboots. Do not reinsert the DVD.

Step 24 When the installation process completes, you get prompted to log in by using the Administrator account and password.

Step 25 Complete the post-upgrade tasks that are listed in the "Post-Upgrade Tasks" section.


Upgrading Subsequent Nodes in the Cluster

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.

To upgrade a subsequent node in the cluster from Cisco Unified Communications Manager 4.x to Cisco Unified Communications Manager release 6.0(1) or later, perform the following steps:

1. Upgrade the first node, the Cisco Unified Communications Manager 4.x publisher server, to Cisco Unified Communications Manager 6.0(1) or later.

2. Using Cisco Unified Communications Manager Administration on the first node, configure the subsequent nodes.

3. Ensure that the subsequent nodes have network connectivity to the first node.

4. Install the new operating system and Cisco Unified Communications Manager application from a DVD.

5. If required, upgrade the software to a later service release.

6. 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.0(1) first node, and have network connectivity to the first node. Failure to meet these conditions can cause the installation to fail.


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.

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

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 DHCP Configuration window displays.

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

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 6 for field descriptions.

The DNS Client Configuration window displays.

Step 6 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 6 for field descriptions.

The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.

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.

Step 10 Enter the First Node Access Configuration information from Table 5.

The SMTP Host Configuration window displays.

Step 11 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 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 To log in, enter the administrator account name and password that you entered during installation.

Step 14 Complete the post-upgrade tasks that are listed in the "Post-Upgrade Tasks" section.


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 9 Post-Upgrade Tasks 

Post-Upgrade Tasks
Important Notes

Upload license files for the new product version to the server and restart the Cisco CallManager service.

Note You must do this when you upgrade to Cisco Unified Communications Manager 6.0, or the system will not work.

Refer to Cisco Unified Communications Manager Administration Guide for information about licensing and obtaining licenses, and additional migration information.

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.

Refer to the Cisco Unified Serviceability Administration Guide.

See the "Verifying Cisco Unified Communications Manager Services" section.

If security is enabled on the cluster, you must configure CTL.

To configure CTL on the upgraded cluster

1. Uninstall the existing CTL client.

2. Install the new CTL client.

3. Run the CTL client by using at least one of the previously used USB keys.

4. Update the new CTL file on all nodes.

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

Configure the backup settings.

Remember to back up your Cisco Unified Communications Manager data daily.

Refer to the Disaster Recovery System Administration Guide.

The locale, English_United_States, installs automatically on the server. If required, you can add new locales to the server.

Refer to the Cisco Unified Communications Operating System Administration Guide.

Cisco recommends that you implement authentication and encryption in your Cisco IP Telephony network.

Refer to the Cisco Unified Communications Manager Security Guide.

If you are using Microsoft Active Directory or Netscape Directory, enable synchronization with the LDAP server.

For more information on directories, refer to the Cisco Unified Communications Manager System Guide.

For more information on enabling synchronization, refer to the Cisco Unified Communications Manager Administration Guide.

Upgrade subscriber servers as subsequent Cisco Unified Communications Manager nodes in the cluster.

Remember to enter the same security password for the first node.

See the "Upgrading Subsequent Nodes in the Cluster" section

If necessary, you can add additional, subsequent nodes to the cluster.

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.

2. Install the new application and configure subsequent Cisco Unified Communications Manager nodes in the cluster. See the "Upgrading Subsequent Nodes in the Cluster" section.

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 Real-Time Monitoring Tool and Cisco Unified Communications Manager Attendant Console.

For more information, see the Cisco Cisco Unified Communications Manager Administration Guide.

Inform end users that they must reconfigure their ring tones and background images after the upgrade.

These settings do not get migrated.


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.

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.

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.0(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.0(1).

To use the Disaster Recovery Disk, use this procedure:

Procedure


Step 1 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.

Step 2 For Windows preinstallation setup, enter W.

Step 3 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.

Step 5 Using the Backup and Restore Utility, restore the previously backed-up data to the servers. For more information, see theBackup and Restore Utility documentation for your version of BARS.


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

Step 2 To restart the server, so it is running the software on the currently inactive partition, enter S.

Step 3 Press Enter.

The server restarts.


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