Table Of Contents
Upgrading Cisco CallManager Release 5.0(1)
Frequently Asked Questions About the Cisco CallManager Installation
How long does it take to perform the Cisco 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 CallManager on the server?
Gathering Information for an Installation
Using the Standalone Configuration Wizard
Navigating Within the Standalone Configuration Wizard
Running the Standalone Configuration Wizard
Upgrading the First Cisco CallManager Node
Navigating Within the Installation Wizard
Selecting an Installation Option
Install 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 CallManager Services
Installing Upgrade Software After Upgrading to Cisco CallManager 5.0
Reverting to a Previous Version
Using the Disaster Recovery Disc
Reverting to a Previous Version of Cisco CallManager
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Upgrading Cisco CallManager Release 5.0(1)
This release of Cisco CallManager uses a different installation framework than previous releases of Cisco CallManager. Before upgrading to Cisco CallManager 5.0, review all installation instructions carefully. This document includes information about upgrading to Cisco CallManager 5.0 from a Cisco CallManager 4.x release. This document also provides instructions for installing software patches and upgrade software after you have upgraded to Cisco CallManager 5.0.
Contents
This document contains the following topics:
•
Frequently Asked Questions About the Cisco CallManager Installation
•
•
•
•
•
•
•
Installation Overview
Cisco CallManager 5.0(1) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco CallManager 4.x to Cisco CallManager 5.0, 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 CallManager installation:
•
The Cisco CallManager Administration Guide provides step-by-step instructions for configuring, maintaining, and administering the Cisco CallManager voice over IP network.
The Cisco CallManager System Guide provides descriptions of the Cisco CallManager system and its components, configuration checklists, and links to associated Cisco CallManager Administration Guide procedures.
•
This document describes how to configure features and services for Cisco CallManager, including Cisco Music On Hold, Cisco CallManager Extension Mobility, and so on.
•
This document provides descriptions of Cisco 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 CallManager data, and restore the data.
•
This document provides procedures for migrating data from earlier versions of Cisco CallManager to Cisco CallManager 5.0.
•
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 CallManager, Cisco IP Phones, SRST references, and Cisco MGCP gateways.
See 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 CallManager Compatibility Matrix
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Cisco CallManager documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Cisco CallManager Security Guide
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/a
e/index.htm
Cisco CallManager backup and restore documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm
Cisco CallManager service releases
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 CallManager installation, consider the following requirements and recommendations:
•
•
•
•
•
•
•
•
•
•
•
•
•
Frequently Asked Questions About the Cisco CallManager Installation
The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco CallManager installation.
How long does it take to perform the Cisco 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 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 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 6 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 IP Telephony Platform 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 CallManager Administration through User Management>Application User. See the Cisco 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 6 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 CallManager.
Note
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 CallManager on the server?
For Cisco CallManager 5.0, 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 CallManager with Cisco CallManager 5.0.
Browser Requirements
You can access Cisco CallManager Administration, Cisco CallManager Serviceability, and Cisco IPT 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 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 CallManager
Ensure the Cisco CallManager server with the publisher database is configured as the first node and Cisco 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 CallManager nodes in the cluster.
See the "Frequently Asked Questions About the Cisco CallManager Installation" section.
Step 2
Perform the recommended backup procedures on the publisher server. Back up every database that is associated with your Cisco 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
For more information on CAR, refer to the CDR Analysis and Reporting Administration Guide.
Step 4
If you do not have to carry over your CDR records to Cisco CallManager 5.0, Cisco recommends that you purge the CDR records before you run DMA.
Purging the CDR records speeds up the migration process and decreases the size of the DMA tar file.
Step 5
Export the data on the current Cisco CallManager Publisher server by running the Cisco IP Telephony 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 Cisco IP Telephony Data Migration Assistant 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 CallManager on the first and subsequent nodes.
Step 7
Familiarize yourself with the navigation options within the installation wizards.
See Navigating Within the Standalone Configuration Wizard, and Navigating Within the Installation Wizard.
Gathering Information for an Installation
Use Table 8 to record the information about your Cisco CallManager server. Gather this information for each Cisco 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. It is a good idea to 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 logging in to the CLI on the platform or into the Cisco IPT Platform Administration.
Note
Administrator Password
This field specifies the password that you use for logging into the the CLI on the platform and for logging into Cisco IPT Platform 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 logging in to the Cisco 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 IP Telephony network.
If you have a DNS server, Cisco recommends entering Yes to enable DNS. Disabling DNS limits the systems ability to resolve some domain names.
DNS Primary
Cisco 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 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 CallManager Node
The first Cisco 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 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)
NTP Server
This field identifies the NTP with which server 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 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 character. 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.
Using the Standalone Configuration Wizard
To install a server, you must install the new operating system and Cisco CallManager application. You can speed up the installation of the server if you have a configuration file with all necessary parameters in the correct XML format. Use the Standalone Configuration Wizard to create the configuration file and store this file on a diskette or a USB memory key. Insert the USB memory key or the diskette at the start of installation or when prompted during the installation process.
Note
Navigating Within the Standalone Configuration Wizard
For instructions on how to navigate within the Standalone Configuration Wizard, see Table 10.
Note
Running the Standalone Configuration Wizard
Use the following procedure to set up and run the Standalone Configuration Wizard:
Procedure
Step 1
Step 2
Step 3
Step 4
Note
Step 5
The Summary window displays.
Step 6
The Welcome to the Cisco CallManager Installation Wizard displays.
Step 7
Step 8
Step 9
Upgrading the First Cisco 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 11.
Selecting an Installation Option
After the platform software installation starts, you will be asked to select one of the options that Table 12 lists.
Install the New Operating System and Application on the First Node
Use this procedure to begin installing the operating system and Cisco CallManager application on the first Cisco 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?Choose Yes to continue the installation.
–
–
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 with Cisco 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 Product Installation Configuration window displays. Continue with the "If Your Choose Proceed" section.
If Your Choose Proceed
Step 9
–
–
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 Platform Installation Configuration 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.gzWhere 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
–
–
Step 18
The DNS Client Configuration window displays.
Step 19
After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.
Retrieving the Remote Patch
Step 20
The Install Upgrade Patch Selection window displays.
Step 21
After the system restarts, the Preexisting Configuration Information window displays.
Using Preexisting Configuration Information
Step 22
The Platform Installation Wizard window displays.
Note
Step 23
The Product Installation Configuration window displays.
Step 24
The Product Installation Configuration window displays.
Step 25
Windows Upgrade
When you choose Windows Upgrade, the installation wizard prompts you for the location of the preexisting Windows configuration information created by the Data Migration Assistant (DMA) tool. See the Cisco IP Telephony Data Migration Assistant 2.0 User Guide for more information on the DMA tool.
Step 26
The Timezone Configuration window displays.
Step 27
The Auto Negotiation Configuration window displays.
Step 28
–
Note
–
Step 29
The DHCP Configuration window displays.
Step 30
–
–
Step 31
The DNS Client Configuration window displays.
Step 32
The Administrator Login Configuration window displays.
Step 33
The Certificate Signing Request Information window displays.
Step 34
The First Node Configuration window displays.
Step 35
The Network Time Protocol Client Configuration window displays.
Note
Step 36
–
Note
The system contacts an NTP server and automatically sets the time on the hardware clock.
–
The Database Access Security Configuration window displays.
Step 37
Note
The SMTP Host Configuration window displays.
Step 38
Note
The DMA Retrieval Mechanism Configuration window displays.
Step 39
–
–
–
Choose OK to continue with the installation wizard.
Note
Step 40
The Platform Configuration Confirmation window displays.
Step 41
When you choose OK, the Application User Password Configuration window displays.
Step 42
Step 43
The End User Password/PIN Configuration window displays.
Step 44
The system installs the software, restarts the network, and reads the DMA file you specified.
The DMA Retrieval Mechanism Configuration window displays.
Step 45
When you choose OK, the Platform Configuration Confirmation window displays.
Step 46
Step 47
Step 48
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 CallManager application on the first node and then configure the subsequent node on the first node using Cisco 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 CallManager 4.x to Cisco CallManager 5.0(1), perform the following steps:
1.
2.
3.
4.
5.
6.
Note
Install the New Operating System and Application on Subsequent Nodes
Use this procedure to begin installing the operating system and Cisco CallManager application on a subsequent node.
Caution
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.
Note
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 with Cisco CallManager preinstalled or if you chose Skip on Platform Installation Wizard window.
Step 6
Note
Note
Step 7
The Platform Installation Wizard window displays.
Step 8
The Product Installation Configuration window displays. Continue with the "If Your Choose Proceed" section.
If Your Choose Proceed
Step 9
–
–
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
Note
The Platform Installation Configuration 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.gzWhere 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
–
–
Step 18
The DNS Client Configuration window displays.
Step 19
After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.
Retrieving the Remote Patch
Step 20
The Install Upgrade Patch Selection window displays.
Step 21
After the system restarts, the Preexisting Configuration Information window displays.
Using Preexisting Configuration Information
Step 22
The Platform Installation Wizard window displays.
Note
Step 23
The Product Installation Configuration window displays.
Step 24
The Product Installation Configuration window displays.
Step 25
Basic Installation
Step 26
The Auto Negotiation Configuration window displays.
Step 27
–
Note
–
Step 28
The DHCP Configuration window displays.
Step 29
–
–
Step 30
The DNS Client Configuration window displays.
Step 31
The network restarts using the new configuration information, and the Administrator Login Configuration window displays.
Step 32
Note
The Certificate Signing Request Information window displays.
Step 33
The First Node Configuration window displays.
Step 34
The First Node Access Configuration window displays.
Step 35
The SMTP Host Configuration window displays.
Step 36
Note
The Platform Configuration Confirmation window displays.
Step 37
Step 38
Step 39
Performing Post-Upgrade Tasks
When you complete your upgrade of Cisco CallManager, you must perform all appropriate tasks as described in the following table:
Table 13 Post-Upgrade Tasks
Verify that all appropriate Cisco 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:
•
•
Configure the backup settings.
Remember to back up your Cisco CallManager data daily.
Refer to the Cisco IP Telephony Disaster Recovery System 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 IP Telephony Platform Administration Guide.
Cisco recommends that you implement authentication and encryption in your Cisco IP Telephony network.
Refer to the Cisco 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 CallManager System Guide.
For more information on enabling synchronization, refer to the Cisco CallManager Administration Guide.
Upgrade subscriber servers as subsequent Cisco CallManager nodes in the cluster.
Remember to enter the same security password for the first node.
Install and configure subsequent Cisco 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.
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.
2.
Remember to enter the same security password that you used for the first node.
Reinstall customer background images, custom TFTP files, custom MoH files, and customer ring tones.
To upload these files, log in to Cisco IP Telephony Platform Administration and navigate to the Software Upgrades>Upload TFTP Server File menu.
See the Cisco IP Telephony Platform Administration Guide for more information.
Install the required client-side plugins, such as Cisco CallManager Real-Time Monitoring Tool and Cisco CallManager Attendant Console.
From Cisco CallManager Administration, choose Application>Plugins.
For more information, see the Cisco 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 CallManager Services
To access Cisco CallManager Administration or Cisco CallManager Serviceability, you will need to use a web browser from a PC with network access to the Cisco CallManager server.
To review service activation procedures and service recommendations, refer to the Cisco CallManager Serviceability Administration Guide and the Cisco CallManager Serviceability System Guide
Procedure
Step 1
Step 2
http://ccm_server:8080/ccmadmin
where ccm_server specifies the IP address or hostname of the Cisco CallManager server.
Step 3
Step 4
Step 5
Step 6
Installing Upgrade Software After Upgrading to Cisco CallManager 5.0
With this version of Cisco 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
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 CallManager server can access. You can install the software patch independently on the inactive partition of each node prior to actually activating the new software. When you are ready, you must activate the new software on the first node before activating it on all other nodes.
Note
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
To install or upgrade software from a CD or DVD, follow this procedure:
Procedure
Step 1
Note
Step 2
Step 3
Note
Step 4
http://server-name/iptplatform
where server-name is the host name or IP address of the Cisco CallManager server.
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
When the download completes, the Checksum window displays.
Step 12
Caution
Step 13
A Warning window displays the current and upgrade software versions.
Step 14
The Post Installation Options window displays.
Step 15
–
–
Step 16
The Upgrade Status windows displays and displays the Upgrade log.
Step 17
Step 18
The Switch Software Version window displays.
Step 19
The Switch Software Version window displays.
When you verify that you want to restart the system, the system restarts running the upgraded software.
From Remote Source
To install software from a network drive or remote server, use the following procedure.
Note
Procedure
Step 1
Step 2
Step 3
Step 4
Note
Step 5
The system checks for available upgrades.
Step 6
Step 7
When the download completes, the Checksum window displays.
Step 8
Caution
Step 9
A Warning window displays the current and upgrade software versions.
Step 10
The Post Installation Options window displays.
Step 11
–
–
Step 12
The Upgrade Status window, which shows the Upgrade log, displays.
Step 13
Step 14
The Switch Software Version window displays.
When you verify that you want to restart the system, the system restarts 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
http://server-name/iptplatform
where server-name is the host name or IP address of the Cisco CallManager server.
Step 2
Step 3
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 CallManager or to force the system to restart on the inactive partition.
Reverting to a Previous Version of Cisco CallManager
If the upgrade from Cisco CallManager 4.0 or 4.1 to Cisco CallManager 5.0 is unsuccessful, you can use the Disaster Recovery Disc to revert to a Windows-based version of Cisco CallManager.
Caution
To use the Disaster Recovery Disk, use this procedure:
Procedure
Step 1
Step 2
Step 3
Caution
The Disaster Recovery disc formats your hard drive so that you can re-install a Windows-based version of Cisco CallManager.
Step 4
Step 5
Switching Partitions
If the system is unable to 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
To force the system to switch partitions and restart, follow this procedure:
Procedure
Step 1
Step 2
Step 3
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 installTo view the log file from the command line, enter:
CLI>file view install log_filewhere log_file is the log file name.
You can also view logs using the Cisco CallManager Real-Time Monitoring Tool (RTMT). For more information on using and installing the Cisco CallManager RTMT, refer to the Cisco CallManager Serviceability Administration Guide, Release 5.0(1).
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:
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-9883We 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:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
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:
•
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.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
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
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-2447For 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.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
Guest
