Table Of Contents
Frequently Asked Questions About the Cisco Unified Communications Manager Installation
From What Version Can I Upgrade to Cisco Unified Communications Manager 6.1(2)?
What User Names Passwords do I Need to Specify?
Which servers does Cisco support for this installation?
May I install other software besides Cisco Unified Communications Manager on the server?
Determining Registration Counts by Using RTMT
Recording Critical Service Status
Locating System Errors by Using Syslog Viewer
Recording Trace and Log Central Job Details
Accessing CDR Management Configuration
Determining System Configuration Counts
Obtaining System Version Information
Gathering Information for an Installation
Handling Network Errors During Upgrade
Assigning the Host Name/IP Address (Servername) to the 6.1(2) Server
Upgrading Cisco Unified Communications Manager
Navigating Within the Installation Wizard
Using the Data Migration Assistant Generated Configuration File
Entering Preexisting Configuration Information
Upgrading From a Remote Server
Upgrading the Cisco Unified Communications Manager First Node
Upgrading Subsequent Nodes in the Cluster
Obtaining Software Feature Licenses
Verifying Cisco Unified Communications Manager Services
Using the Disaster Recovery Disc
Reverting to a Previous Version of Cisco Unified Communications Manager
Obtaining Documentation, Obtaining Support, and Security Guidelines
Upgrading to Cisco Unified Communications Manager Release 6.1(2) from Cisco Unified Communications Manager 4.x Releases
This document describes how to upgrade to Cisco Unified Communications Manager 6.1(2) from a Cisco Unified Communications Manager 4.x release.
For information about upgrading your Cisco Unified Communications Manager software after you have upgraded to release 5.0(1) or later, refer to Cisco Unified Communications Operating System Administration Guide.
For information about performing a fresh installation of Cisco Unified Communications Manager (rather then upgrading from an earlier release) or configuring Cisco Unified Communications Manager when it is preinstalled on your server, refer to Installing Cisco Unified Communications Manager.
The 6.1(2) release of Cisco Unified Communications Manager uses a different installation framework than releases of Cisco Unified Communications Manager prior to 5.0. Before upgrading to Cisco Unified Communications Manager 6.1(2), review all upgrade instructions carefully.
Contents
This document contains the following topics:
•
Upgrading Cisco Unified Communications Manager
•
•
Installation Overview
Cisco Unified Communications Manager uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified Communications Manager 4.x to Cisco Unified Communications Manager 6.1(2), 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
For further information about related Cisco IP telephony applications and products, refer to the Cisco Unified Communications Manager Documentation Guide at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_documentation_roadmaps_list.html
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 Communications Manager service releases
Important Considerations
Before you proceed with the Cisco Unified Communications Manager upgrade, consider the following requirements and recommendations:
•
Caution
•
•
•
•
•
•
•
•
When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table is full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.
•
•
•
•
•
•
•
•
•
Preparing To Upgrade
This section describes how to prepare to upgrade from Cisco Unified Communications Manager 4.x to release 6.1(2).
Frequently Asked Questions About the Cisco Unified Communications Manager Installation
The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified Communications Manager installation.
From What Version Can I Upgrade to Cisco Unified Communications Manager 6.1(2)?
For information on supported upgrades, refer to the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
What User Names Passwords do I Need to Specify?
Note
During the Cisco Unified Communications Manager upgrade, you must specify the following user names and passwords:
•
•
•
•
Administrator User Name and Password
You use the Administrator user name and password to log in to the following areas:
•
•
•
To specify the Administrator user name and password, follow these guidelines:
•
•
You can change the Administrator Account password or add a new Administrator account by using the command line interface. For more information, see Table 5 in the "Gathering Information for an Installation" section or the Cisco Unified Communications Operating System Administration Guide.
Application User Name and Password
You use the Application user name and password to access applications that are installed on the system, including the following areas:
•
•
•
•
To specify the Application user name and password, follow these guidelines:
•
•
You can change the Application User name and password by using the command line interface. For more information, see Table 5 in the "Gathering Information for an Installation" section or the Cisco Unified Communications Operating System Administration Guide.
Security Password
The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster.
The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
End User Password and PIN
The system uses this password and PIN to reset the password and PIN for all end users that were configured on the Windows-based Cisco Unified Communications Manager.
Note
What is a Strong Password?
The installation wizard checks to ensure that you enter a strong password. To create a strong password, follow these recommendations:
•
•
•
•
Avoid the following types of passwords:
•
•
•
•
•
Which servers does Cisco support for this installation?
To find which servers support Cisco Unified Communications Manager 6.1(2), refer to the Cisco Unified Communications Manager Server Support Matrix at
http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html
May I install other software besides Cisco Unified Communications Manager on the server?
You must do all software installations and upgrades by using Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified Communications Manager with Cisco Unified Communications Manager 6.1(2).
Browser Requirements
You can access Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, Cisco Unified Reporting, Cisco Unified Communications Operating System Administration, and Disaster Recovery System 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 Communications Manager application. See Table 3 for the BIOS settings and Table 4 for the RAID settings that are set up during installation.
Note
Performing Pre-Upgrade Tasks
Perform the following tasks before you begin the upgrade:
Step 1
Verify that your servers meet the system requirements for upgrading Cisco Unified Communications Manager nodes in the cluster.
Refer to the following documentation for information about the capacity of server models:
•
•
Make sure to account for any growth that has occurred since initial system configuration.
Step 1
Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
Caution
Step 2
Verify the integrity of any new server hardware (such as hard drives and memory) by running any manufacturer-provided utilities.
Step 3
Make sure that you have a copy of all custom ring files, phone backgrounds, and music on hold sources.
Consider this as precautionary because the restore is designed to restore these items.
Step 4
Obtain and store files for any locales that are installed on the server.
You might need to reinstall locales after doing the upgrade.
Step 5
Do not change computer names or IP addresses, or add more nodes to the cluster.
Step 6
Verify the integrity of your software downloads and DVDs.
Perform the following tasks:
•
•
Step 7
Perform any system tests that you intend to perform after the replacement before the replacement also, to verify that the tests pass before you do the replacement.
Document these tests, so you can perform them identically after doing the replacement.
Step 8
If you use DNS, verify that all servers to be replaced are configured in DNS properly. All nodes in the cluster must either use DNS or not use it.
See the "Verifying DNS Registration" section.
Step 9
If you are getting the system time from an NTP server, verify that the first node can synchronize with the NTP server before you install a subsequent node.
To verify the NTP status of the first node, log into the Command Line Interface on the first node and enter the following command: utils ntp status
For more information, see the Cisco Unified Communications Operating System Administration Guide.
Caution
Step 10
Do not run Network Address Translation (NAT) or Port Address Translation (PAT) between Cisco Unified Communications Manager nodes.
Step 11
Record all the registration information by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT).
See the "Determining Registration Counts by Using RTMT" section.
Step 12
Record all the critical services and their activation status by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT).
Step 13
Using the Syslog viewer in the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT), locate any events that have a severity of Error or higher.
Perform this task to ensure that no system-affecting errors exist on your system.
See the "Locating System Errors by Using Syslog Viewer" section.
Step 14
Record the details of all Trace and Log Central jobs.
See the "Recording Trace and Log Central Job Details" section.
Step 15
Record CDR Management configuration and destinations, if applicable.
Step 16
From Cisco Unified Communications Manager Administration, determine the number of specific items that are configured on the server.
Step 17
From Cisco Unified Communications Manager Administration, record all the phone loads and device types that display on the Firmware Load Information window.
See the "Firmware Information" section.
If you have custom device types that do not ship with Cisco Unified Communications Manager, make sure that you have the appropriate files. You might need to reinstall the devices types after performing the replacement.
Step 18
If your cluster is running in secure mode, make sure that you have USB eToken devices and CTL Client plug-in utility installed on a computer that is running the Windows operating system.
For information about performing these tasks and about Cisco Unified Communications Manager security, refer to the "Installing the CTL Client" procedures in the Cisco Unified Communications Manager Security Guide.
Step 19
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 20
Perform the recommended backup procedures on the publisher server. Back up every database that is associated with your Cisco Unified Communications Manager server.
Refer to Cisco IP Telephony Backup and Restore System (BARS) Administration Guide.
Step 21
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.
Caution
For more information on CAR, refer to the Cisco Unified Serviceability Administration Guide for the version of Cisco Unified CallManager running on your system.
Step 22
If you use Cisco Unified Communications Manager CDR Analysis and Reporting, make sure that the latest CDRs exist in the CAR database by setting the CDR load schedule to run before you execute the Data Migration Assistant. DMA will not migrate any CDRs generated after you have run the loader.
For information on configuring the CAR load schedule before you upgrade, see the Cisco Unified Serviceability Administration Guide for the version of Cisco CallManager running on your system.
Step 23
If you do not need to carry over your CAR data to Cisco Unified Communications Manager 6.1(2), Cisco recommends that you purge the CAR data before you run DMA.
Make sure that you purge any CAR records older than 180 days.
Purging the CDR data speeds up the migration process and decreases the size of the DMA TAR file.
Caution
Caution
For information on configuring automatic database purging after you upgrade, refer to the Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide.
For more information on the Data Migration Assistant, see the Data Migration Assistant User Guide.
Step 24
Export the data on the current Cisco Unified Communications Manager Publisher server by running the Data Migration Assistant (DMA).
Ensure the configuration files and exported data files are located in one of the following locations:
•
•
•
•
DMA generates two files:
•
•
Note
For more information on data migration, refer to Data Migration Assistant User Guide. You will be choosing an installation option based on the location of the DMA output configuration file and TAR file.
Step 25
Before the upgrade, obtain the necessary information for configuring the platform and Cisco Unified Communications Manager on the first and subsequent nodes.
See the "Gathering Information for an Installation" section.
Step 26
Record the Host Name/IP Address value that is configured on the Server Configuration Settings window of the Cisco Unified Communications Manager 4.x server.
To access the Host Name/IP Address field on the 4.x server, navigate to System > Server.
For more information, see the "Assigning the Host Name/IP Address (Servername) to the 6.1(2) Server" section
Step 27
Familiarize yourself with the navigation options within the installation wizards.
Step 28
Make sure that you have the 6.1(2) installation DVD. Also if you plan to install a patch during the upgrade, ensure you have the patch file available on a DVD or SFTP or FTP server that the Cisco Unified Communications Manager nodes can access.
See the "Applying a Patch" section for more information.
Verifying DNS Registration
If you use DNS, verify that all servers to be replaced are registered in DNS properly.
Procedure
Step 1
Step 2
Step 3
Related Topics
Determining Registration Counts by Using RTMT
Record the number of registered devices, including the numbers of registered phones and gateways, by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT).
Procedure
Step 1
If you are planning to install the RTMT tool on a computer that is running the Microsoft Windows operating system, click the Download link for the Cisco Unified Communications Manager Real-Time Monitoring Tool-Windows. If you are planning to install the RTMT tool on a computer that is running the Linux operating system, click the Download link for the Cisco Unified Communications Manager Real-Time Monitoring Tool-Linux.
Step 2
Step 3
•
•
Step 4
Related Topics
•
Recording Critical Service Status
Record all the critical services and their status by using the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT).
Procedure
Step 1
•
•
Step 2
Related Topics
•
Locating System Errors by Using Syslog Viewer
Using the Syslog viewer in the Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT), locate any events that have a severity of Error or higher.
Procedure
Step 1
•
•
Step 2
Step 3
Step 4
Step 5
Related Topics
•
Recording Trace and Log Central Job Details
Record the details of all Trace and Log Central jobs.
Procedure
Step 1
•
•
Step 2
Related Topics
•
Accessing CDR Management Configuration
Record CDR Management configuration and destinations, if applicable.
You use the CDR Management Configuration window to set the amount of disk space to allocate to call detail record (CDR) and call management record (CMR) files, configure the number of days to preserve files before deletion, and configure up to three billing application server destinations for CDRs. The CDR repository manager service repeatedly attempts to deliver CDR and CMR files to the billing servers that you configure on the CDR Management Configuration window until it delivers the files successfully, until you change or delete the billing application server on the CDR Management Configuration window, or until the files fall outside the preservation window and are deleted.
Procedure
Step 1
The CDR Management Configuration window displays.
Step 2
Related Topics
•
Determining System Configuration Counts
From Cisco Unified Communications Manager Administration, obtain counts of each of the items that are configured on the system that you want to verify after the replacement. Some examples of items to count follow:
•
•
•
•
•
•
•
Procedure
Step 1
•
•
•
•
•
Note
•
Note
Step 2
Related Topics
•
Firmware Information
Record all of the phone loads and device types that display on the Firmware Load Information window.
Procedure
Step 1
The Firmware Load Information window displays.
Step 2
Note
Related Topics
•
Obtaining System Version Information
Compare the system version on each node in your cluster by using Cisco Unified Communications Operating System Administration.
Verify that you have DVDs with that version. If you have a service release, you need media for base image and the service release.
Procedure
Step 1
Step 2
Note
Related Topics
•
Gathering Information for an Installation
Use Table 5 to record the information about your Cisco Unified Communications Manager server. Gather this information for each Cisco Unified Communications Manager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You can make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system.
Note
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 Cisco Unified Communications Operating System Administration or through the Command Line Interface (CLI).
Table 5 Node Configuration Data
Administrator ID
This field specifies the administrator account user ID that you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.
No, you cannot change the entry after installation.
Note
Your entry:
Administrator Password
This field specifies the password for the Administrator account, which you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.
Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set password admin
Your entry:
Application User Name
You use the Application User name as the default password for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability.
Yes, you can change the entry after installation by using the following CLI command:
CLI > utils reset_ui_administrator_name
Your entry:
Application User Password
You use the Application User password as the default password for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified CallManager Serviceability.
Yes, you can change the entry after installation by using the following CLI command:
CLI > utils reset_ui_administrator_password
Your entry:
Country
Choose the appropriate country for your installation.
The system uses this information to generate certificate signing requests (CSRs), which are used to obtain third-party certificates.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
DHCP
If you want to use DHCP to automatically configure the network settings on your server, choose Yes.
If you choose Yes, you do not get prompted for DNS or static configuration settings.
If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dhcp
Your entry:
DNS Enable
A DNS server resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No.
If you have a DNS server, Cisco recommends that you enter Yes to enable DNS.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dns
Your entry:
DNS Primary
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.
Consider this field mandatory if DNS is set to yes.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dns
Your entry:
DNS Secondary (optional)
Enter the IP address of the DNS server that you want to specify as the optional secondary DNS server.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dns
Your entry:
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.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network domain
Your entry:
End User Password
The system uses this password to reset the password for all end users that were configured on the Windows-based Cisco Unified CallManager.
Yes, after you upgrade the system, you must inform all end users about this new password, which they can then change to a password of their choice.
Your entry:
End User PIN
The system uses this PIN to reset the PIN for all end users that were configured on the Windows-based Cisco Unified CallManager.
Yes, after you upgrade the system, you must inform all end users about this new PIN, which they can then change to a PIN of their choice.
Your entry:
Gateway Address
Enter the IP address of the network gateway.
If you do not have a gateway, you must still set this field to 255.255.255.255. Not having a gateway may limit you to only being able to communicate with devices on your subnet.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network gateway
Your entry:
Hostname
Enter a host name that is unique to your server.
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.
You can change the hostname after installation.
For more information on changing hostnames, refer to the Changing the IP Address and Host Name for Cisco Unified Communications Manager 5.x and 6.x Servers document at the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Your entry:
IP Address
Enter the IP address of your server.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network IP
Note
Your entry:
IP Mask
Enter the IP subnet mask of this machine.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network ip eth0
Your entry:
Location
Enter the location of the server.
The system uses this information to generate certificate signing requests (CSRs), which are used to obtain third-party certificates.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
MTU Size
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network.
Enter the MTU size in bytes for your network. If you are unsure of the MTU setting for your network, use the default value.
Default: 1500 bytes
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network mtu
Your entry:
NIC Duplex
Choose the duplex mode for the network interface card (NIC), either Full or Half.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network nic
Your entry:
NIC Speed
Choose the speed for the NIC, either 10 Megabits per second or 100 Megabits per second.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network nic
Your entry:
NTP Server
Enter the hostname or IP address of one or more network time protocol (NTP) servers with which you want to synchronize.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > utils ntp config
Your entry:
Organization
Enter the name of your organization.
The system uses this information to generate certificate signing requests (CSRs), which are used to obtain third-party certificates.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
Security Password
Guest
