Table Of Contents
Upgrading Cisco Unified CallManager Release 5.0(2)
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
Using the Standalone Configuration Wizard
Navigating Within the Standalone Configuration Wizard
Running the Standalone Configuration Wizard
Upgrading the First Cisco Unified 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 Unified CallManager Services
Installing Upgrade Software After Upgrading to Cisco Unified CallManager 5.0
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
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Upgrading Cisco Unified CallManager Release 5.0(2)
This 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, review all installation instructions carefully. This document includes information about upgrading to Cisco Unified CallManager 5.0 from a Cisco Unified CallManager 4.0 or 4.1 release. This document also provides instructions for installing software patches and upgrade software after you have upgraded to Cisco Unified CallManager 5.0.
Contents
This document contains the following topics:
•
Frequently Asked Questions About the Cisco Unified CallManager Installation
•
Upgrading Cisco Unified CallManager
•
Upgrading the First Cisco Unified CallManager Node
•
Upgrading Subsequent Nodes in the Cluster
•
Installing Upgrade Software After Upgrading to Cisco Unified CallManager 5.0
•
Using the Disaster Recovery Disc
•
Cisco Product Security Overview
•
Obtaining Technical Assistance
Installation Overview
Cisco Unified CallManager 5.0(2) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified CallManager 4.0 or 4.1 to Cisco Unified 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
The document describes the procedure for performing a Windows Upgrade. For basic installation instructions, see Installing Cisco Unified CallManager Release 5.0(2).
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
This document provides 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 2.0 User Guide
This document provides procedures for migrating data from earlier versions of Cisco Unified CallManager to Cisco Unified CallManager 5.0.
•
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.
See Table 2, lists URLs for software and additional documentation.
Table 2 Quick Reference for URLs
Related Information and Software URLCisco 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:
•
Be aware that when you install Cisco Unified CallManager 5.0 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 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 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 the 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 follows 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
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
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
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 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 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 6 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, 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.
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.
Note
If the hardware configuration precess fails during installation, you can use boot-time utilities found 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:
•
Gathering Information for an Installation
•
Using the Standalone Configuration Wizard
•
Upgrading the First Cisco Unified 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
Performing Pre-Upgrade Tasks
Perform the following tasks before you begin the upgrade:
Pre-Upgrade Task Important NotesStep 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(2) 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 have to carry over your CDR records to Cisco Unified 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 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.
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 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. 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
Because some of the fields are optional, they may not be relevant to your configuration. For example, you choose not to set up an SMTP host.
CautionYou 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).
For more detailed descriptions of each installation field, see Table 9.
Table 9 Installation Field Definitions
Field Description UsageAdministrator 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 Platform Administration.
Note
You cannot change this field after installation.
Administrator Password
This field specifies the password that you use for logging into the the CLI on the platform and for logging into 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 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 systems 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)
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
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 character. It can contain hyphens and underscores, but it must start with an alphanumeric character.
CautionYou 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.
Using the Standalone Configuration Wizard
To install a server, you must install the new operating system and Cisco Unified 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
You can only use Standalone Configuration Wizard on a system that is running the Linux operating system.
Navigating Within the Standalone Configuration Wizard
For instructions on how to navigate within the Standalone Configuration Wizard, see Table 10.
Note
Be aware that all fields are case-sensitive.
Running the Standalone Configuration Wizard
Use the following procedure to set up and run the Standalone Configuration Wizard:
Procedure
Step 1
Copy the Standalone Configuration Wizard to a machine that is running on the Linux operating system.
Step 2
Execute WizardConfigurator.
Step 3
To add Cisco Unified CallManager as a product, choose Add.
Step 4
Enter an output filename. The default output filename specifies platformConfig.xml.
Note
If you enter a filename other than platformConfig.xml, remember to change the filename to platformConfig.xml before you start your installation. The installation program looks specifically for a file with the exact filename of DMABackupInfo.inf or platformConfig.xml file.
Step 5
Enter time, network, and account information as described in Table 9.
The Summary window displays.
Step 6
Verify the configuration information. Press P to change the configuration and press Enter to start the configuration.
The Welcome to the Cisco Unified CallManager Installation Wizard displays.
Step 7
Enter the Cisco Unified CallManager configuration information as described in Table 9. When you complete this window, press Enter.
Step 8
The Cisco Unified CallManager Installation Wizard summary displays. Verify the configuration information. Press P to change the configuration and press Enter to start the configuration.
Step 9
Copy the output file to a diskette or a USB memory key.
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 Performing Pre-Upgrade Tasks.
2.
Familiarize yourself with navigation within the installation wizard. See Table 11.
3.
Know which installation options to choose. See Table 12.
4.
Configure the hardware with the hardware configuration disc. See Configuring the Hardware.
5.
Install the New Operating System and Application on the First Node
6.
Perform the appropriate Post-Upgrade Tasks.
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 Unified CallManager application on the first Cisco Unified CallManager Node:
CautionBefore 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 that 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 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 displayed 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?Choose Yes to continue the installation.
–
The installation next checks to see if you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.
–
The installation process 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.
CautionIf 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
Choose Proceed to configure the platform now. 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 Your 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 with 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 information created by the Standalone Configuration Wizard, the system automatically enters the values you configured in the appropriate fields. If you have a file created by the Data Migration Assistant, see the Data Migration Assistant 2.0 User Guide for more information.
Step 7
Choose OK to continue.
The Platform Installation Wizard window displays.
Step 8
Choose Proceed to continue with the installation.
The Product Installation Configuration window displays. Continue with the "If Your Choose Proceed" section.
If Your Choose Proceed
Step 9
When the Product Installation Configuration window displays, choose the type of installation you want to perform. See Table 12 for more information on installation options.
–
If you want to perform a Windows Upgrade installation with the software version on the DVD or the preinstalled software, choose Windows Upgrade and continue with the "Windows Upgrade" section.
–
If you want to upgrade to a later Service Release of the software during installation, choose Upgrade During Install and continue with the "Upgrade During Install" section.
Note
To perform a basic installation, that is, to install the application without importing Windows data, see Installing to Cisco Unified CallManager Release 5.0(2).
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. Choose Proceed to continue the installation.
The Platform Installation Configuration window displays.
Step 11
Choose Upgrade During Install and then choose OK.
The Install Upgrade Retrieval Mechanism Configuration window displays.
Step 12
Choose the upgrade retrieval mechanism you want to use to retrieve the upgrade file:
–
SFTP—Retrieves the upgrade file from a remote server 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 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.gzWhere 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 available on the CD or DVD. Choose Continue to update the system with this patch.
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.
–
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


