Table Of Contents
Upgrading Cisco Unified CallManager Release 5.1(1)
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?
Upgrading Cisco Unified CallManager
Gathering Information for an Installation
Handling Network Errors During Installation
Upgrading the First Cisco Unified CallManager Node
Navigating Within the Installation Wizard
Selecting an Installation Option
Assigning the Host Name/IP Address (Servername) to the 5.1(1) Server
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
Verifying Cisco Unified CallManager Services
Installing Upgrade Software After Upgrading to Cisco Unified CallManager 5.1(1)
Reverting to a Previous Version
Using the Disaster Recovery Disc
Reverting to a Previous Version of Cisco Unified CallManager
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Upgrading Cisco Unified CallManager Release 5.1(1)
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.1(1), review all installation instructions carefully. This document includes information about upgrading to Cisco Unified CallManager 5.1(1) 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.1(1).
Contents
This document contains the following topics:
•
Frequently Asked Questions About the Cisco Unified CallManager Installation
•
•
•
•
•
•
•
Installation Overview
Cisco Unified CallManager 5.1(1) 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.1(1), and upgrade to a newer service release during the installation.
For a more detailed description of the different installation types, see Table 1.
Note
Related Documentation
Cisco strongly recommends that you review the following documents before you perform the Cisco Unified CallManager installation:
•
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.
•
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.
•
These documents provide descriptions of Cisco Unified CallManager serviceability and remote serviceability and step-by-step instructions for configuring alarms, traces, and other reporting.
•
This document describes how to configure the backup settings, back up Cisco Unified CallManager data, and restore the data.
•
This document provides procedures for migrating data from earlier versions of Cisco Unified CallManager.
•
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.
•
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
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 Matrixhttp://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Cisco Unified
CallManager documentationhttp://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Cisco Unified
CallManager Security Guidehttp://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/a
e/index.htm
Cisco Unified
CallManager backup and restore documentationhttp://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm
Cisco Unified
CallManager service releasesRelated 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:
•
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
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:
•
•
•
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:
•
•
•
What Passwords do I Need to Specify?
During the Cisco Unified CallManager installation, you must specify the following user names and passwords:
•
You use the Administrator username and password to log in to the following areas:
–
–
–
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.
•
You use the Application User password for the following default application user names:
–
–
–
–
–
–
–
–
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.
•
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.
•
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
Which servers does Cisco support for this installation?
To find which servers support Cisco CallManager 5.0 releases, 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.1(1), you must do all software installations and upgrades by using the Software Upgrades menu options in Platform Administration. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 5.1(1).
Browser Requirements
You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Administration by using the following browsers:
•
•
Note
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.
Note
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
Perform the following tasks before you begin the upgrade:
Step 1
Verify that you meet the system requirements for upgrading Cisco Unified CallManager nodes in the cluster.
See the "Which servers does Cisco support for this installation?" section.
Step 2
Run Cisco Unified CallManager Upgrade Utility on the server to verify that the system is ready for upgrade.
Refer to Using Cisco Unified CallManager Upgrade Utility.
Step 3
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 4
If you are using a third-party application to access Call Detail Records (CDR), perform a backup of the CDR data as recommended in the third-party vendor documentation.
For more information on CAR, refer to the CDR Analysis and Reporting Administration Guide.
Step 5
If you do not need to carry over your CDR data to Cisco Unified CallManager 5.1(1), Cisco recommends that you purge the CDR data before you run DMA.
Purging the CDR data speeds up the migration process and decreases the size of the DMA TAR file.
Step 6
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:
•
•
•
•
DMA generates two files:
•
•
Note
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 7
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 8
Record the Host Name/IP Address value that is configured on the Server Configuration Settings window of the Cisco Unified CallManager 4.x server.
To access the Host Name/IP Address field on the 4.x server, navigate to System > Server.
For more information, see the "Assigning the Host Name/IP Address (Servername) to the 5.1(1) Server" section
Step 9
Familiarize yourself with the navigation options within the installation wizards.
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
Caution
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).
For more detailed descriptions of each installation field, see Table 9.
Table 9 Installation Field Definitions
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
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
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 it attempts to resolve host names.
Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).
Consider this field mandatory if DNS is set to yes.
DNS Secondary
When a primary DNS server fails, Cisco Unified 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 communicating only with devices on your subnet.
Hostname
A host name represents an alias that is assigned to an IP address to identify it.
Enter a host name that is unique to your network.
The host name can comprise up to 64 characters and can contain alphanumeric characters and hyphens.
If DHCP is set to No, consider this field mandatory.
IP Address
This field specifies the IP address of this machine. It will uniquely identify the server on this network. Another machine in this network should not be using this IP address.
Enter the IP address in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).
If DHCP is set to No, consider this field mandatory.
IP Mask
This field specifies the IP subnet mask of this machine. The subnet mask together with the IP address defines the network address and the host address.
Enter the IP mask in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).
A valid mask should have contiguous '1' bits on left side and contiguous '0' bits on the right.
For example, a valid mask follows: 255.255.240.0 (11111111.11111111.11110000.00000000)
An invalid mask follows: 255.255.240.240 (11111111.11111111.11110000.11110000)
NIC Speed
This field specifies the speed of the server network interface card (NIC) in megabits per second.
The possible speeds comprise 10 or 100.
NIC Duplex
This field specifies the duplex setting of the server NIC.
The possible settings comprise half and full.
NTP Server
This field identifies the NTP server with which you want to keep time synchronization.
Enter the hostname or IP Address of NTP server(s).
If you enabled the system to be NTP client, you must enter the hostname or IP address of at least one NTP server.
Note
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
Set Hardware Clock
The field specifies the date and local time for the machine.
Note
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
SMTP
This field specifies the name of the SMTP host that is used for outbound e-mail.
Enter the hostname or dotted IP address for the SMTP server. For a host, it can contain alphanumeric characters, hyphens, or periods. For a host name, it must start with an alphanumeric character.
You must fill in this field if you plan to use electronic notification. If not, you can leave it blank.
Time zone
This field specifies the local time zone and offset from Greenwich Mean Time (GMT)
Choose Yes if you want to change the time zone.
Choose the time zone that most closely matches the location of your machine.
Handling Network Errors During Installation
During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration that you enter. If it cannot, a message displays, and you are prompted to select one of the following options:
•
•
Networking is validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window appears again.
•
•
Upgrading the First Cisco Unified CallManager Node
To upgrade and migrate data from a publisher server, you must perform the following tasks.
1.
2.
3.
4.
5.
6.
Navigating Within the Installation Wizard
For instructions on how to navigate within the installation wizard, see Table 10.
Selecting an Installation Option
After the platform software installation starts, you will be asked to select one of the options that Table 11 lists.
Assigning the Host Name/IP Address (Servername) to the 5.1(1) Server
In 4.x releases, the Host Name/IP Address field (also known as Servername) on the publisher server Server Configuration Settings window contains one of the following types of values:
•
•
To access Server Configuration Settings, navigate to System > Server.
The Data Migration Assistant (DMA) file that is used to migrate data from 4.x to 5.1(1) releases includes the Host Name/IP Address value. When you migrate data by using DMA, the Host Name/IP Address (Servername) for the publisher server gets imported into the 5.1(1) database as follows:
•
–
–
–
•
–
–
–
This feature allows you to import your 4.x data to a 5.1(1) server without having to preserve the IP Address or Host Name. The IP Address and/or Host name of the 5.1(1) server can differ from the 4.x servername.
Caution
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
Procedure
Step 1
Note
Step 2
When the media check completes, the Media Check Result window displays.
Step 3
If the media fails the Media Check, either download another copy from Cisco.com or obtain another disc directly from Cisco Systems.
–
Drivers not found, do you want to install manually?To continue the installation, choose Yes.
–
–
After the hardware checks complete, the Overwrite Hard Drive window displays.
Step 4
Caution
The Platform Installation Wizard window displays.
Step 5
–
–
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
Note
Step 7
The Platform Installation Wizard window displays.
Step 8
The Upgrade During Install window displays. Continue with the "If You Choose Proceed" section.
If You Choose Proceed
Step 9
a.
•
•
•
b.
Note
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
The Upgrade During Install window displays.
Step 11
The Install Upgrade Retrieval Mechanism Configuration window displays.
Step 12
–
–
–
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.sgnWhere X.X.X.X-X represents the release and build number
Note
Step 13
Note
The Install Upgrade Patch Selection Validation window displays.
Step 14
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
–
Note
–
Step 16
The DHCP Configuration window displays.
Step 17
Guest
