Guest

Cisco Unified Communications Manager (CallManager)

Upgrading Cisco Unified CallManager Release 5.0(4)

  • Viewing Options

  • PDF (554.8 KB)
  • Feedback
Upgrading Cisco Unified CallManager Release 5.0(4)

Table Of Contents

Upgrading Cisco Unified CallManager Release 5.0(4)

Contents

Installation Overview

Related Documentation

Important Considerations

Frequently Asked Questions About the Cisco Unified CallManager Installation

How long does it take to perform the Cisco Unified CallManager Windows Upgrade?

MCS-7845H-3000 Typical Windows Upgrade Performance Measurements

MCS-7835-H1 Typical Windows Upgrade Performance Measurements

MCS-7825-H1 Typical Windows Upgrade Performance Measurements

What Passwords do I Need to Specify?

Which servers does Cisco support for this installation?

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

Browser Requirements

Configuring the Hardware

Upgrading Cisco Unified CallManager

Performing Pre-Upgrade Tasks

Gathering Information for an Installation

Upgrading the First Cisco Unified CallManager Node

Navigating Within the Installation Wizard

Selecting an Installation Option

Installing the New Operating System and Application on the First Node

Upgrading Subsequent Nodes in the Cluster

Install the New Operating System and Application on Subsequent Nodes

Post-Upgrade Tasks

Verifying Cisco Unified CallManager Services

Installing Upgrade Software After Upgrading to Cisco Unified CallManager 5.0(4)

Upgrading the System

From Local Source

From Remote Source

Reverting to a Previous Version

Using the Disaster Recovery Disc

Reverting to a Previous Version of Cisco Unified CallManager

Switching Partitions

Examining Log Files

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Upgrading Cisco Unified CallManager Release 5.0(4)


The 5.0(x) release of Cisco Unified CallManager uses a different installation framework than previous releases of Cisco Unified CallManager. Before upgrading to Cisco Unified CallManager 5.0(4), review all installation instructions carefully. This document includes information about upgrading to Cisco Unified CallManager 5.0(4) from a Cisco Unified CallManager 4.x release. This document also provides instructions for installing software patches and upgrade software after you have upgraded to Cisco Unified CallManager 5.0(4).

Contents

This document contains the following topics:

Installation Overview

Related Documentation

Important Considerations

Frequently Asked Questions About the Cisco Unified CallManager Installation

Browser Requirements

Configuring the Hardware

Upgrading Cisco Unified CallManager

Upgrading the First Cisco Unified CallManager Node

Upgrading Subsequent Nodes in the Cluster

Post-Upgrade Tasks

Installing Upgrade Software After Upgrading to Cisco Unified CallManager 5.0(4)

Using the Disaster Recovery Disc

Examining Log Files

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Installation Overview

Cisco Unified CallManager 5.0(4) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified CallManager 4.x to Cisco Unified CallManager 5.0(4), 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 CallManager 5.0(4) 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 the latest service release. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process.

Windows Upgrade

This option allows you to import database information from a Cisco Unified CallManager 4.x system by using a file that by the Data Migration Assistant (DMA) tool produces.



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


Related Documentation

Cisco strongly recommends that you review the following documents before you perform the Cisco Unified CallManager installation:

Cisco Unified CallManager Administration Guide and Cisco Unified CallManager System Guide

The Cisco Unified CallManager Administration Guide provides step-by-step instructions for configuring, maintaining, and administering the Cisco Unified CallManager voice over IP network.

The Cisco Unified CallManager System Guide provides descriptions of the Cisco Unified CallManager system and its components, configuration checklists, and links to associated Cisco Unified CallManager Administration Guide procedures.

Cisco Unified CallManager Features and Services Guide

This document describes how to configure features and services for Cisco Unified CallManager, including Cisco Music On Hold, Cisco Unified CallManager Extension Mobility, and so on.

The Cisco Unified CallManager Serviceability System Guide and Cisco Unified CallManager Serviceability Administration Guide

These documents provide descriptions of Cisco Unified CallManager serviceability and remote serviceability and step-by-step instructions for configuring alarms, traces, and other reporting.

Disaster Recovery System Administration Guide

This document describes how to configure the backup settings, back up Cisco Unified CallManager data, and restore the data.

Data Migration Assistant User Guide

This document provides procedures for migrating data from earlier versions of Cisco Unified CallManager to Cisco Unified CallManager 5.0(4).

Cisco Unified Communications Operating System Administration Guide

This document provides information on how to access and use the utilities that are available on the platform. This document also includes instructions for installing new locales.

Cisco Unified CallManager Security Guide

This document provides instructions on how to configure and troubleshoot authentication and encryption for Cisco Unified CallManager, Cisco Unified IP Phones, SRST references, and Cisco MGCP gateways.

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 
CallManager Compatibility Matrix

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

Cisco Unified 
CallManager documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

Cisco Unified 
CallManager Security Guide

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/a

e/index.htm

Cisco Unified 
CallManager backup and restore documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm

Cisco Unified 
CallManager service releases

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

Related Cisco IP telephony application documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm


Important Considerations

Before you proceed with the Cisco Unified CallManager installation, consider the following requirements and recommendations:

Be aware that when you install Cisco Unified CallManager 5.0(4) 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 CallManager 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 CallManager 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 CallManager 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 CallManager 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.

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

Frequently Asked Questions About the Cisco Unified CallManager Installation

The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified CallManager installation.

How long does it take to perform the Cisco Unified CallManager Windows Upgrade?

The entire upgrade process, excluding pre- and post-installation tasks, takes approximately 60 to 100 minutes per server, depending on your server type and the number of database entries that you have configured on the Cisco Unified CallManager server. The following tables provide Windows upgrade performance measurements for three different servers with various database sizes.

MCS-7845H-3000 Typical Windows Upgrade Performance Measurements

Table 3 shows the upgrade performance measurements for an MCS-7845H-3000 server that is configured as follows:

CPUs: 2, 3.066 GHz

Memory: 4 GB

Hard drives: 4, 72 GB, RAID 1+0

Table 3 MCS-7845H-3000 Typical Windows Upgrade Performance Measurements 

Performance Measure
Publisher With 500 Database Entries
Publisher With 2500 Database Entries
Publisher With 10,000 Database Entries
Subscriber With 2500 Database Entries
System Boot From DVD

1.5 minutes

1.5 minutes

1.5 minutes

1.5 minutes

DVD Checksum

8 minutes

8 minutes

8 minutes

8 minutes

RIOS/RAID Setting

0.5 minutes

0.5 minutes

0.5 minutes

0.5 minutes

Reboot

2 minutes

2 minutes

2 minutes

2 minutes

DVD Checksum

8 minutes

8 minutes

8 minutes

8 minutes

Start Installing (Skip option)

21 minutes

21 minutes

21 minutes

21 minutes

Reboot

2 minutes

2 minutes

2 minutes

2 minutes

Installation and Configuration

42 minutes

43.5 minutes

50 minutes

23 minutes

Service Start

5 minutes

5 minutes

5 minutes

5 minutes

Total

90 minutes

91.5 minutes

98 minutes

71 minutes


MCS-7835-H1 Typical Windows Upgrade Performance Measurements

Table 4 shows the upgrade performance measurements for an MCS-7835-H1 server that is configured as follows:

CPUs: 1, 3.4 GHz

Memory: 2 GB

Hard drives: 1, 72 GB

Table 4 MCS-7835-H1 Typical Windows Upgrade Performance Measurements 

Performance Measure
Publisher With 500 Database Entries
Publisher With 2500 Database Entries
Publisher With 10,000 Database Entries
Subscriber With 2500 Database Entries
System Boot From DVD

1.5 minutes

1.5 minutes

1.5 minutes

1.5 minutes

DVD Checksum

6 minutes

6 minutes

6 minutes

6 minutes

RIOS/RAID Setting

0.5 minutes

0.5 minutes

0.5 minutes

0.5 minutes

Reboot

2 minutes

2 minutes

2 minutes

2 minutes

DVD Checksum

6 minutes

6 minutes

6 minutes

6 minutes

Start Installing (Skip option)

13 minutes

13 minutes

13 minutes

13 minutes

Reboot

2 minutes

2 minutes

2 minutes

2 minutes

Installation and Configuration

33 minutes

35 minutes

40 minutes

17 minutes

Service Start

5 minutes

5 minutes

5 minutes

5 minutes

Total

69 minutes

71 minutes

76 minutes

53 minutes


MCS-7825-H1 Typical Windows Upgrade Performance Measurements

Table 5 shows the upgrade performance measurements for an MCS-7825-H1 server that is configured as follows:

CPUs: 1, 3.4 GHz

Memory: 2 GB

Hard drives: 1, 72 GB

Table 5 MCS-7825-H1 Typical Windows Upgrade Performance Measurements 

Performance Measure
Publisher With 500 Database Entries
Publisher With 1000 Database Entries
Subscriber With 1000 Database Entries
System Boot From DVD

1.5 minutes

1.5 minutes

1.5 minutes

DVD Checksum

10 minutes

10 minutes

10 minutes

RIOS/RAID Setting

0.5 minutes

0.5 minutes

0.5 minutes

Reboot

2 minutes

2 minutes

2 minutes

DVD Checksum

10 minutes

10 minutes

10 minutes

Start Installing (Skip option)

21.5 minutes

21.5 minutes

21.5 minutes

Reboot

2 minutes

2 minutes

2 minutes

Installation and Configuration

40 minutes

42 minutes

20 minutes

Service Start

5 minutes

5 minutes

4 minutes

Total

92.5 minutes

94.5 minutes

71.5 minutes


What Passwords do I Need to Specify?

During the Cisco Unified CallManager installation, 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 the following default application user names:

CCMAdministrator

CCMSysUser

WDSysUser

CCMQRTSysUser

IPMASysUser

WDSecureSysUser

CCMQRTSecureSysUser

IPMASecureSysUser

You can change the application user password for each application in Cisco Unified CallManager Administration through User Management>Application User. See the Cisco Unified CallManager 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 CallManager.


Note After you upgrade the system, you must inform all end users about this new 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 CallManager 5.0 releases, please refer to the Guide to Cisco CallManager 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 CallManager on the server?

For Cisco Unified CallManager 5.0(4), 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 CallManager with Cisco Unified CallManager 5.0(4).

Browser Requirements

You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Administration by using the following browsers:

Microsoft Internet Explorer version 6.0 or later

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 CallManager application. See Table 6 for the BIOS settings and Table 7 for the RAID settings that are set up during installation.

Table 6 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 7 RAID Settings

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

RAID not applicable

Logical drives: 1

Logical drives: 2

RAID not applicable

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

RAID type: 1(1+0)

RAID type: 1(1+0)



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 6 and Table 7.


Upgrading Cisco Unified CallManager

Ensure the Cisco Unified CallManager server with the publisher database is configured as the first node and Cisco Unified CallManager servers with subscriber databases are configured as subsequent nodes. This section contains the procedures for upgrading the first and subsequent nodes. Review the following sections carefully before you perform the upgrade:

Performing Pre-Upgrade Tasks

Gathering Information for an Installation

Upgrading the First Cisco Unified CallManager Node

Navigating Within the Installation Wizard

Selecting an Installation Option

Installing the New Operating System and Application on the First Node

Upgrading Subsequent Nodes in the Cluster

Post-Upgrade Tasks

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 CallManager nodes in the cluster.

See the "Frequently Asked Questions About the Cisco Unified CallManager Installation" section.

Step 2 

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

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

Step 3 

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.

Note Cisco Unified CallManager 5.0(4) does not support third-party tools to access the CDR data. You must use Cisco CDR Analysis and Reporting (CAR) tool to access CDR data.

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

Step 4 

If you do not need to carry over your CDR data to Cisco Unified CallManager 5.0(4), 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 5 

Export the data on the current Cisco Unified CallManager 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 CallManager configuration data, named DMABackupInfo.inf. The system saves it in the D:\DMA folder as part of the TAR file.

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

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

Step 6 

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

See the "Gathering Information for an Installation" section.

Step 7 

Familiarize yourself with the navigation options within the installation wizards.

See "Navigating Within the Installation Wizard" section.

Gathering Information for an Installation

Use Table 8 to record the information about your Cisco Unified CallManager server. Gather this information for each Cisco Unified CallManager 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 8 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 IP

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

See "End User Configuration" in the Cisco Unified CallManager Administration Guide.

End-User PIN

 

Yes

See "End User Configuration" in the Cisco Unified CallManager Administration Guide.


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

Table 9 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 the the CLI on the platform and for logging in to Cisco Unified Communications Operating System Administration.

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

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.

Note You cannot change the DNS settings after the installation is complete. To change DNS settings, you must reinstall Cisco Unified CallManager.

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 CallManager contacts this DNS server first when attempting 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 CallManager 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 CallManager Node

The first Cisco Unified CallManager 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 CallManager node in the cluster.

If you are configuring subsequent nodes, see Table 9 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 only being able to communicate 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 are 10 or 100.

NIC Duplex

This field specifies the duplex setting of the server NIC.

The possible settings are 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 CallManager 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.


Upgrading the First Cisco Unified CallManager Node

To upgrade and migrate data from a publisher server, you must perform the following tasks.

1. Verify that you have completed all pre-upgrade tasks. See the "Performing Pre-Upgrade Tasks" section.

2. Familiarize yourself with navigation within the installation wizard. See the "Navigating Within the Installation Wizard" section.

3. Know which installation options to choose. See Table 11.

4. Configure the hardware with the hardware configuration disc. See the "Configuring the Hardware" section.

5. Install the new operating system on the first node. See the "Installing the New Operating System and Application on the First Node" section

6. Perform the appropriate "Post-Upgrade Tasks" section.

Navigating Within the Installation Wizard

For instructions on how to navigate within the installation wizard, see Table 10.

Table 10 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)


Selecting an Installation Option

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

Table 11 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 CallManager 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.


Installing the New Operating System and Application on the First Node

Use this procedure to begin installing the operating system and Cisco Unified CallManager application on the first Cisco Unified CallManager node:


Caution Before beginning this procedure, ensure that you have backed up the data on your current Windows-based version of Cisco Unified CallManager. For more information, see the Cisco Unified Communications Backup and Restore System Administration Guide for your version of BARS.

Procedure


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 Media Check window displays.


Note If you have a new server with preinstalled Cisco Unified CallManager, you do not need to install from a DVD. Go directly to the "If You Choose Skip" procedure.


Step 2 Verify that the checksum that displays on the Media Check matches the checksum for the release on Cisco.com.

When the media check completes, the Media Check Result window displays.

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

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

First, the installation process checks for the correct drivers, and you may see the following warning:

Drivers not found, do you want to install manually?

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 to Cisco support.

The installation process then verifies RAID configuration and BIOS settings. If the installation process makes any changes to your hardware configuration settings, you will get prompted to restart your system.

After the hardware checks complete, the Overwrite Hard Drive window displays.

Step 4 The Overwrite Hard Drive window indicates the current software version on your hard drive, if any, 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 5 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 skip to the "If You Choose Proceed" section.

If you want to install the software now and configure it later, choose Skip and continue with the "If You Choose Skip" section.

If You Choose Skip

Start here if you have a server that has Cisco Unified CallManager preinstalled or if you chose Skip on Platform Installation Wizard window.

Step 6 After the system restarts, the Preexisting Installation Configuration window displays. If you have configuration information on a USB drive or on a diskette, insert it now.


Note If you have a file that the Data Migration Assistant created, see the Data Migration Assistant User Guide for more information.


Step 7 To continue, choose OK.

The Platform Installation Wizard window displays.

Step 8 To continue with the installation, choose Proceed.

The Upgrade During Install window displays. Continue with the "If You Choose Proceed" section.

If You Choose Proceed

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

a. In the Upgrade During Install window, choose one of the options:

To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrade During Install" section.

To skip this step, choose No.

To return to the previous window, choose Back.

b. In the Windows Upgrade window, choose Yes. Continue with the "Windows Upgrade" section.


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


Upgrade During Install

If you chose Upgrade During Install, the installation wizard installs the software version on the DVD first and then restarts the system. You then get prompted to enter certain network configuration parameter values and the location of the upgrade file.

Step 10 After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed.

The Upgrade During Install window displays.

Step 11 Choose Yes.

The Install Upgrade Retrieval Mechanism Configuration window displays.

Step 12 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 "Upgrade From a Remote Server" section.

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

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

Upgrade From a Local Disc

Before you can upgrade from a local drive, 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.

The patch-file name has the following format:

cisco-ipt-k9-patchX.X.X.X-X.tar.gz

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


Note Do not untar or unzip the patch file before you install it because the system will not recognize it as a valid file.


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


The Install Upgrade Patch Selection Validation window displays.

Step 14 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue.

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

The Auto Negotiation Configuration window displays.

Step 15 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) 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 16 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 17 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 configured in your network and want to use DHCP, choose Yes. The system restarts and checks for network connectivity. Skip to the "Retrieving the Remote Patch" section.

If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.

Step 18 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 9 for field descriptions.

The DNS Client Configuration window displays.

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

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

Retrieving the Remote Patch

Step 20 Enter the location and login information for the remote file server. See Table 9 for field descriptions. After restarting the network, 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 21 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system so it is running the upgraded software version.

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

Using Preexisting Configuration Information

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

The Platform Installation Wizard window displays.

Step 23 To continue with the Platform Installation Wizard, choose Proceed.

Step 24 To configure the platform now, choose Proceed.

Step 25 In the Upgrade During Install window, choose No.

Step 26 In the Windows Upgrade window, choose Yes. Continue with the "Windows Upgrade" section.

Windows Upgrade

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 27 In the Windows Upgrade window, choose Yes.

The Timezone Configuration window displays.

Step 28 Choose the appropriate time zone for the server and then choose OK.

The Auto Negotiation Configuration window displays.

Step 29 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 30 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 31 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 32 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 9 for field descriptions.

The DNS Client Configuration window displays.

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

The Administrator Login Configuration window displays.

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

The Certificate Signing Request Information window displays.

Step 35 Enter your certificate signing request information from Table 8 and choose OK.

The First Node Configuration window displays.

Step 36 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 37 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 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 38 Enter the Database Access Security password from Table 8.


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 39 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 40 Choose the mechanmism to use to retrieve the DMA file:

SFTP—Retrieves the DMA file from a remote server by using Secure File Transfer Protocol (SFTP)

FTP—Retrieves the DMA file from a remote server by using File Transfer Protocol (FTP)

TAPE—Retrieves the DMA file from a locally attached tape drive

To continue with the installation wizard, choose OK.


Note If you choose SFTP or FTP, the DMA Backup Configuration Screen 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 41 If you chose SFTP or FTP, enter the DMA Backup Configuration information and choose OK. See Table 9 for parameter definitions.

The Platform Configuration Confirmation window displays.

Step 42 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 43 Enter the Application User Password from Table 8 and confirm the password by entering it again.

Step 44 Choose OK.

The End User Password/PIN Configuration window displays.

Step 45 Enter the End User Password and PIN and choose OK.

The end user password must consist of five or more alphanumeric or special characters. The end user PIN must consist of 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 46 To continue, choose OK, or to choose a different DMA file, choose Back.

When you choose OK, the Platform Configuration Confirmation window displays.

Step 47 To continue, choose OK.

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

Step 49 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 CallManager application on the first node and then configure the subsequent node on the first node by using Cisco Unified CallManager 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 CallManager 4.x to Cisco Unified CallManager 5.0(4), perform the following steps:

1. Upgrade the first node, the Cisco Unified CallManager 4.x publisher, to Cisco Unified CallManager 5.0(4).

2. Using Cisco Unified CallManager 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 CallManager application from a DVD.

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

6. Configure the Platform and Cisco Unified CallManager.


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


Install the New Operating System and Application on Subsequent Nodes

Use this procedure to begin installing the operating system and Cisco Unified CallManager application on a subsequent node.


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


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 Media Check window displays.


Note If you have a new server that has Cisco Unified CallManager preinstalled, you do not need to install from a DVD. Go directly to the "If You Choose Skip" procedure.


Step 2 Verify that the checksum that displays on the Media Check matches the checksum for the release on Cisco.com.

When the media check completes, the Media Check Result window displays.

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

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


Note The installation process performs various hardware checks on your server and verifies RAID configuration and BIOS settings. If the installation process makes any changes to your hardware configuration settings, you will get prompted to restart your system.


The Overwrite Hard Drive window displays.

Step 4 The Overwrite Hard Drive window indicates the current software version on your hard drive, if any, 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 5 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 skip to the "If You Choose Proceed" section.

If you want to install the software now and configure it later, choose Skip and continue with the "If You Choose Skip" section.

If You Choose Skip

Start here if you have a server that has Cisco Unified CallManager preinstalled or if you chose Skip on Platform Installation Wizard window.

Step 6 After the system restarts, the Preexisting Installation Configuration window displays. If you have configuration information on a USB drive or on a diskette, insert it now.


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


Step 7 To continue, choose OK.

The Platform Installation Wizard window displays.

Step 8 To continue with the installation, choose Proceed.

The Install During Upgrade window displays. Continue with the "If You Choose Proceed" section.

If You Choose Proceed

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

a. In the Upgrade During Install window, choose one of the options:

To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrade During Install" section.

To skip this step, choose No.

To return to the previous window, choose Back.

b. In the Windows Upgrade window, choose No.

c. In the Basic Install window, choose Continue to install the software version on the DVD or configure the preinstalled software with the basic installation. Continue with the "Basic Installation" section.

Upgrade During Install

If you chose Upgrade During Install, the installation wizard installs the software version on the DVD first and then restarts the system. You then get prompted to enter certain network configuration parameter values and the location of the upgrade file.

Step 10 After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed.


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


The Upgrade During Install window displays.

Step 11 Choose Yes.

The Install Upgrade Retrieval Mechanism Configuration window displays.

Step 12 Choose the upgrade retrieval mechanism that you want 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 "Upgrade From a Remote Server" section.

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

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

Upgrade From a Local Disc

Before you can upgrade from a local drive, 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.

The patch-file name has the following format:

cisco-ipt-k9-patchX.X.X.X-X.tar.gz

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


Note Do not untar or unzip the patch file before you install it because the system will not recognize it as a valid upgrade file.


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


The Install Upgrade Patch Selection Validation window displays.

Step 14 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue.

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

The Auto Negotiation Configuration window displays.

Step 15 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 16 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 17 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 the "Retrieving the Remote Patch" section.

If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.

Step 18 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 9 for field descriptions.

The DNS Client Configuration window displays.

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

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

Retrieving the Remote Patch

Step 20 Enter the location and login information for the remote file server. See Table 9 for field descriptions. After restarting the network, 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 21 Choose the upgrade patch that you want to install. The system downloads, unpacks, and installs the patch and then restarts the system so it is running on the upgraded software version.

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

Using Preexisting Configuration Information

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

The Platform Installation Wizard window displays.

Step 23 To continue with the Platform Installation Wizard, choose Proceed.

The Product Installation Configuration window displays.

Step 24 To configure the platform now, choose Proceed.

The Upgrade During Installation window displays.

Step 25 In the Upgrade During Install window, choose No.

Step 26 In the Windows Upgrade window, choose No.

Step 27 In the Basic Install window, choose Continue. Continue with the "Basic Installation" section

Basic Installation

Step 28 When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK.

The Auto Negotiation Configuration window displays.

Step 29 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) 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 30 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 31 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 32 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 9 for field descriptions.

The DNS Client Configuration window displays.

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

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

Step 34 Enter your Administrator login and password from Table 8.


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 35 Enter your certificate signing request information from Table 8 and choose OK.

The First Node Configuration window displays.

Step 36 To configure this server as a subsequent node in the cluster, choose No.

The First Node Access Configuration window displays.

Step 37 Enter the First Node Access Configuration information from Table 8.

The SMTP Host Configuration window displays.

Step 38 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 39 To start installing the software, choose OK, or if you want to change the configuration, choose Back.

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

Step 41 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 CallManager, you must perform all appropriate tasks as described in the following table:

Table 12 Post-Upgrade Tasks 

Post-Upgrade Tasks
Important Notes

Verify that all appropriate Cisco Unified CallManager services started.

Verify that you can make internal calls.

Verify that you can place and receive a call across gateways.

Refer to the following documents:

Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Serviceability System Guide

See the "Verifying Cisco Unified CallManager 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 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 CallManager security, refer to the Cisco Unified CallManager Security Guide.

Configure the backup settings.

Remember to back up your Cisco Unified CallManager 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 CallManager 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 CallManager System Guide.

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

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

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

See the "Upgrading Subsequent Nodes in the Cluster" section

Install and configure subsequent Cisco Unified CallManager nodes in the cluster.

Subscriber servers automatically get defined as subsequent nodes in the database. Remember to enter the same security password that you used 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 CallManager nodes to Cisco Unified CallManager Administration. For more information, refer to Cisco Unified CallManager Administration Guide.

2. Install the new application and configure subsequent Cisco Unified CallManager 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 plugins, such as Cisco Unified  CallManager Real-Time Monitoring Tool and Cisco CallManager Attendant Console.

From Cisco Unified CallManager Administration, choose Application>Plugins.

For more information, see the Cisco Unified CallManager 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 CallManager Services

To access Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability, you will need to use a web browser from a PC with network access to the Cisco Unified CallManager server.

To review service activation procedures and service recommendations, refer to the Cisco Unified CallManager Serviceability Administration Guide and the Cisco Unified CallManager Serviceability System Guide

Procedure


Step 1 Open a web browser on a computer with network access to the Cisco Unified CallManager server.

Step 2 Enter in the following url:

http://ccm_server:8080/ccmadmin

where ccm_server specifies the IP address or hostname of the Cisco Unified CallManager server.

Step 3 Enter in the Cisco Unified CallManager Administrator user name and password.

Step 4 From the Navigation menu, choose Cisco Unified CallManager Serviceability and click Go.

Step 5 Navigate to Tools>Service Activation.

Step 6 Verify that all migrated services are running.


Installing Upgrade Software After Upgrading to Cisco Unified CallManager 5.0(4)

With this version of Cisco Unified CallManager, you can install upgrade software on your server while the system continues to operate. Two partitions exist on your system: an active, bootable partition and an inactive, bootable partition. The system boots up and operates entirely on the partition that is marked as the active partition.

When you install upgrade software, you install the software on the inactive partition. The system continues to function normally while you are installing the software. When you are ready, you activate the inactive partition and reboot the system with the new upgrade software. The current active partition will then get identified as the inactive partition when the system restarts. The current software remains in the inactive partition until the next upgrade. You must activate new software on the first node before activating it on all other nodes.


Note You can only make changes to the database on the active partition. The database on the inactive partition does not get updated. If you make changes to the database after an upgrade, you must repeat those changes after switching the partition.


Upgrading the System

You can install a patch or upgrade version from a DVD (local source) or from a computer (remote source) that the Cisco Unified CallManager server can access.

You must install the upgrade patch on the first node before installing it on subscriber nodes. You can install the upgrade patch on multiple subscriber servers at the same time. When you are ready to activate the new version, you must activate the new software on the first node before activating it on all other nodes.

From Local Source

You can install software from a CD or DVD that is located in the local disc drive and then start the upgrade process.


Note Be sure to back up your system data before starting the software upgrade process. For more information, see the Disaster Recovery System Administration Guide.


To install or upgrade software from a CD or DVD, follow this procedure:

Procedure


Step 1 Download the appropriate upgrade file from Cisco.com.


Note Do not unzip or untar the file. If you do, the system may not be able to read the upgrade files.


Step 2 Copy the upgrade file to a writeable CD or DVD.

Step 3 Insert the new CD or DVD into the disc drive on the local server that is to be upgraded.


Note Because of their size, some upgrade files may not fit on a CD and will require a DVD.


Step 4 Open Cisco Unified Communications Operating System Administration directly by entering the following URL:

http://server-name/iptplatform

where server-name is the host name or IP address of the Cisco Unified CallManager server.

Step 5 Enter your Administrator username and password.

Step 6 Choose Software Upgrades>Install/Upgrade.

Step 7 For the software location source, choose DVD/CD.

Step 8 If you burned the patch file to a subdirectory on the CD or DVD, enter the path in the Directory field.

Step 9 To continue the upgrade process, click Next.

Step 10 Choose the upgrade version that you want to install and click Next.

Step 11 In the next window, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred.

When the download completes, the Checksum window displays.

Step 12 Verify the checksum value against the checksum for the file that you downloaded that is shown on Cisco.com.


Caution The two checksum values must match to ensure the authenticity and integrity of the upgrade file. If the checksum values do not match, download a fresh version of the file from Cisco.com and try the upgrade again.

Step 13 After determining that the cheksums match, click Next to proceed with the software upgrade.

A Warning window displays the current and upgrade software versions.

Step 14 To continue with the software upgrade, click Next.

The Post Installation Options window displays.

Step 15 Choose whether you want the system to automatically reboot to the upgraded partition after installing the upgrade software:

To install the upgrade and automatically reboot to the upgraded partition, choose Reboot to upgraded partition.

To install the upgrade and then manually reboot to the upgraded partition at a later time, choose Do not reboot after upgrade.

Step 16 Click Upgrade.

The Upgrade Status windows displays and displays the Upgrade log.

Step 17 When the installation completes, click Finish.

Step 18 To restart the system and activate the upgrade, choose Restart>Switch Versions.

The Switch Software Version window displays.

Step 19 To switch software versions and restart the system, click Switch Versions.

The Switch Software Version window displays.

When you verify that you want to restart the system, the system restarts by running the upgraded software.


From Remote Source

To install software from a network drive or remote server, use the following procedure.


Note Be sure to back up your system data before starting the software upgrade process. For more information, see the Disaster Recovery System Administration Guide.


Procedure


Step 1 Navigate to Software Upgrades>Install.

Step 2 For the Software Location Source, choose Remote File System.

Step 3 Enter the directory name for the software upgrade, if required.

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.

Step 4 Enter the required upgrade information as described in the following table:

Field
Description

Remote Server

Host name or IP address of the remote server from which software will be downloaded.

Remote User

Name of a user who is configured on the remote server.

Remote Password

Password that is configured for this user on the remote server.

Download Protocol

Choose sftp or ftp.


Note You must choose Remote File System to enable the remote server configuration fields.

Step 5 Click Next.

The system checks for available upgrades.

Step 6 Choose the upgrade or option that you want to install and click Next.

Step 7 In the next window, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred.

When the download completes, the Checksum window displays.

Step 8 Verify the checksum value against the checksum for the file that you downloaded that was shown on Cisco.com.


Caution The two checksum values must match to ensure the authenticity and integrity of the upgrade file. If the checksum values do not match, download a fresh version of the file from Cisco.com and try the upgrade again.

Step 9 After determining that the cheksums match, click Next to proceed with the software upgrade.

A Warning window displays the current and upgrade software versions.

Step 10 To continue with the software upgrade, click Next.

The Post Installation Options window displays.

Step 11 Choose whether you want the system to automatically reboot to the upgraded partition after installing the upgrade software:

To install the upgrade and automatically reboot to the upgraded partition, choose Reboot to upgraded partition.

To install the upgrade and then manually reboot to the upgraded partition at a later time, choose Do not reboot after upgrade.

Step 12 Click Upgrade.

The Upgrade Status window, which shows the Upgrade log, displays.

Step 13 When the installation completes, click Finish.

Step 14 To restart the system and activate the upgrade, choose Restart>Switch Versions.

The Switch Software Version window displays.

When you verify that you want to restart the system, the system restarts by running the upgraded software.


Reverting to a Previous Version

If an upgrade seems unstable or for some other reason you want to revert to the software version before the upgrade, you can restart your system and switch to the software version on the inactive partition.

Procedure


Step 1 Open Cisco Unified Communications Operating System Administration directly by entering the following URL:

http://server-name/iptplatform

where server-name is the host name or IP address of the Cisco Unified CallManager server.

Step 2 Enter your Administrator username and password.

Step 3 Choose Restart>Switch Versions.

The Switch Software Version window displays.

When you verify that you want to restart the system, the system restarts running the upgraded software.


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 CallManager or to force the system to restart on the inactive partition.

Reverting to a Previous Version of Cisco Unified CallManager

If the upgrade from Cisco Unified CallManager 4.x to Cisco Unified CallManager 5.0(4) is unsuccessful, you can use the Disaster Recovery Disc to revert to a Windows-based version of Cisco Unified CallManager.


Caution If you revert to a previous version of Cisco Unified CallManager, you will lose any configuration changes that you made by using Cisco Unified CallManager 5.0(4).

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

Step 4 Following the instructions in the installation guide for your Windows-based version of Cisco Unified CallManager, install Cisco Unified CallManager on the publisher server first and then on the subscriber nodes.

Step 5 Using the Cisco Unified Communications Backup and Restore System (BARS), restore the previously backed-up data to the servers. For more information, see the Cisco Unified Communications Backup and Restore System Administration Guide 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 CallManager Real-Time Monitoring Tool (RTMT). For more information on using and installing the Cisco Unified CallManager RTMT, refer to the Cisco Unified CallManager Serviceability Administration Guide.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have.pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

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.

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

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

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html