CUCM Installation and Upgrade Overview

CUCM can be upgraded from the various previous releases of Windows Server-based CUCM or appliance-based CUCM.

Cisco CallManager Releases 3x and earlier for Windows Server have to be upgraded to Release 4.1(3) or later before upgrade to 6.0(1) is possible.

Appliance-based CUCM releases earlier than 5.1(1) have to be upgraded to Release 5.1(1) before upgrade to 6.0(1) is possible.

Figure 3-1 displays the various upgrade path options available for CUCM 6.0(1).

Figure 3-1 CUCM Upgrade Paths Windows Server 2000

Release 3.x

Release 4.x

Release 5.x

Release 6.x

Windows Server 2000 _\.

Windows Server 2003

Appliance

Appliance

Appliance-Based ( ) Windows-Based

CM Upgrade Path

CUCM Installation and Upgrade Options

Of the four installation options, only the first three options are available when booting from the DVD. These options are available when CUCM has been chosen in the Product Deployment Selection screen.

Upgrade from 5.1 does not require booting from the installation DVD, but it is presented here as one of the upgrade options.

CUCM 6.0(x) uses an installation framework similar to CUCM Release 5.x. The installation process allows performing a basic installation, upgrading to a newer service release during the installation, and upgrading from CUCM 4.1(3) or later to CUCM 6.0(1).

The sections that follow describe how the installation and upgrade options work. Basic Install

This option represents the basic installation and does not use imported data. This type of installation generally starts by booting a system from an installation DVD or powering up a new system from the factory (with preinstalled software).

Upgrade During Install

This option performs a basic installation on a system and allows the system to be upgraded to a specific service release patch level before the completion of the basic installation. This option performs a basic installation before prompting the installer for additional upgrade information.

NOTE Ensure that the patches are available on DVD or SFTP/FTP during this installation option.

Windows Upgrade

This option upgrades a Windows-based CUCM system to an appliance-based system and migrates data from an existing Windows Server-based CUCM system. This installation method can be done on the same machine or a different machine from the Windows Server-based CUCM machine. The Windows migration file can be saved to a variety of locations, including a remote hard drive or tape system. The CUCM then uploads the file from one of these locations during the upgrade process.

NOTE During upgrade from a Windows-based release, new software licenses and configuration files generated with the Data Migration Assistant tool (DMA) are required.

5.x or Later Upgrade

If you are upgrading from CUCM Release 5.x, the upgrade filename has the following format:

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

Where X.X.X.X-X represents the release and build number. An upgrade from 5.x or later is performed from the Cisco Unified Operating System Administration.

CAUTION Installation on an existing server formats the hard drive. All existing data on the drive is lost.

Upgrade Methods

The first method is a full installation from scratch where the customer inserts a DVD and loads the operating system and CUCM Release 6.0 application. This method is primarily for customers who have an existing Media Convergence Server (MCS) or when users purchase servers from a Cisco-approved third-party vendor.

The second method is a factory preinstallation in which the customer orders an MCS platform, and the operating system and CUCM Release 6.0 application are preloaded to the server at the factory and then shipped to the customer. This method is primarily for customers who order a new MCS platform. A preinstallation without configuration can also be done from the installation DVD by selecting Skip during the Platform Installation wizard prompt. In this case, only the software is installed, but no configuration is applied. When the server is booted the next time, the Configuration wizard starts automatically (like on a factory preinstalled system).

Installation Disc

The installation disc enables you to install the operating system and CUCM from the same DVD. The installation disc performs a hardware check to verify hardware requirements for the release. If any unsupported component is found, an applicable error message displays, and the installation halts.

The disc can be used for full installation or for recovery if you have a backup of the data.

A separate recovery disc is available for use for system recovery if you want to recover the operating system and application files without a backup of the data.

Cisco Unity Connection and Cisco Unified Communications Manager Business Edition (CMBE) can also be installed from the same DVD; select the product that you want to install. This lesson describes only the installation and upgrade of CUCM.

NOTE Only the products that are supported on your server appear in the list.

Hardware Configuration

Hardware configuration is integrated with the Cisco Unified Communications (UC) installation process. The hardware configuration includes the following:

■ A check for correct hardware configuration, supported platforms, and minimum hardware requirements

■ Configuration of the correct BIOS and RAID settings on the supported platforms

Basic Installation (Installation DVD)

This topic describes the process for performing a basic installation of the operating system and CUCM Release 6.0 application on the publisher. CUCM Release 6.0 has to be installed on the publisher before installing it on any subscriber nodes.

To select the Basic installation option, choose No in both the Apply Additional Release window and the Import Windows Data window.

Important Configuration Information

During the installation process, the installation prompts for various required information based on the installation engineer's answers to the installation prompts. Table 3-1 lists important configuration information requested during CUCM setup.

Table 3-1 Installation Configuration Information

Field

Description

Usage

Administrator ID

This field specifies the name that you want to assign to this account.

Ensure that 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 or into Cisco Unified Communications Operating System Administration.

Administrator Password

This field specifies the password that you use for logging in to the CLI on the platform and for logging in to Cisco Unified Communications Operating System Administration.

Ensure that the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscores.

For this mandatory field, you should record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration.

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.

If you do not have a DNS server, choose No. When DNS is not enabled, you should enter only IP addresses (not hostnames) for all network devices in your Cisco UC network.

If you have a DNS server, Cisco recommends that you choose Yes to enable DNS. Disabling DNS limits the system ability to resolve some domain names.

Table 3-1 Installation Configuration Information (Continued)

Field

Description

Usage

DNS Primary

The server contacts this DNS server first when it attempts to resolve hostnames.

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, the server attempts 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

Communications Manager Node

This field specifies the first CUCM node that contains the database.

Subsequent nodes connect to the first node to access database content.

The first node also synchronizes with an external Network Time Protocol server and provides time to the other nodes.

Choose Yes if you are configuring the first CUCM node in the cluster.

Hostname

A hostname represents an alias that is assigned to an IP address to identify it.

Enter a hostname that is unique to your network.

The hostname can consist of up to 64 characters and can contain alphanumeric characters and hyphens.

If DHCP is set to No, consider this field mandatory.

Table 3-1 Installation Configuration Information (Continued)

Field

Description

Usage

IP Address

This field specifies the IP address of this machine. It uniquely identifies the server on this network. Ensure that another machine in this network does not use 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 the left side and contiguous 0 bits on the right.

For example, a valid mask follows:

255.255.240.0

(11111111.11111111.11110000.00000000)

An invalid mask follows: 255.255.240.240 (11111111.11111111.11110000.11110000)

NIC Speed

This field specifies the speed of the server network interface card in megabits per second.

The possible speeds include 10 or 100.

NIC Duplex

This field specifies the duplex setting of the server network interface card.

The possible settings include Half and Full.

NTP Server

This field identifies the NTP servers with which you want to synchronize.

Enter the hostname or IP address of one or more NTP servers.

Note that you can add additional NTP servers or make changes to the NTP server list at a later time.

NTP Server Enable

When enabled, this server acts as an NTP server and provides time updates to the subsequent nodes in the cluster.

Choose Yes if you want to enable this machine to be an NTP server.

This option is available only on the first node in a cluster.

Table 3-1 Installation Configuration Information (Continued)

Field

Description

Usage

Security Password

Servers in the cluster use the security password to communicate with one another.

You are asked to enter the same security password for each subsequent node in the cluster.

Enter the security password.

Enter the same password in the Confirm Password field.

The password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character.

All nodes in the cluster must have the same password.

Set Hardware Clock

This field specifies the date and local time for the machine.

Note that 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 choose.

Enter the hours based on a 24-hour format.

Note that 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-decimal IP address for the SMTP server. For a host, it can contain alphanumeric characters, hyphens, or periods. For a hostname, 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.

Subnet IP Address

By entering a subnet address, you can specify a range of IP addresses that will be granted access to query this NTP server.

Enter an IP subnet that will be granted access to the NTP server

During installation, you can enter only two subnets.

Subnet Mask

This field specifies the subnet mask for the subnet address.

Enter the subnet mask for the IP subnet.

Time Zone

This field specifies the local time zone and offset from Greenwich mean time.

Choose Yes if you want to change the time zone.

Choose the time zone that most closely matches the location of your machine.

Installation Procedures for Basic Install

Installation starts the same way for all three installation options: Insert the installation disc in the DVD drive and reboot the server. The DVD Found window displays after the server completes the boot sequence.

Figure 3-2 provides a flowchart displaying the various steps involved in installing CUCM from a DVD.

Figure 3-2 Basic Installation Flow (DVD Installation)

Figure 3-2 Basic Installation Flow (DVD Installation)

The DVD prompts the installer to perform a media check. To perform the media check, choose Yes. To skip the media check, choose No. If Yes was chosen, the installation process performs a media check of the image on the DVD to ensure that the image is error free before installation. If the disk is okay, the installation continues.

A hardware check is then performed to determine whether the correct hardware is installed, and then the RAID and BIOS settings are configured.

After the hardware checks are complete, the Product Deployment Selection window displays. In the Product Deployment Selection window, you can choose from the following options:

■ Cisco Unified Communications Manager

■ Cisco Unity Connection

■ Cisco Unified Communications Manager Business Edition (includes CUCM and Cisco Unity Connection)

Select the first option (Cisco Unified Communication Manager) to install only CUCM.

The Overwrite Hard Drive window then indicates the current software version on your hard drive and the version on the DVD. Choose No to halt the installation. Choose Yes to overwrite the hard drive.

Next, choose the desired type of installation by performing the following steps.

In both the Apply Additional Release window and the Import Windows Data window, choose No to select the Basic installation option. When you click Continue, the Platform Installation wizard guides you through the installation process and gathers the required information. Review this window to familiarize yourself with navigating within the Platform Installation wizard, and follow these guidelines:

If you click Proceed, the Product Installation Configuration window displays immediately before any software is copied or installed.

If you click Skip, the software is first transferred to the hard drive, and the system shuts down. At the next boot, the system displays the Installation Configuration window. This is the same state as on a factory-installed system, in which the software is preloaded but no configuration has been done.

When the preloaded system boots, the Configuration dialog is completely skipped if a Universal Serial Bus (USB) drive with a configuration file that includes all configuration parameters is found. Such a configuration file can be prepared using the Answer File Generator, as covered in the following section.

Basic Installation (Preinstalled)

After you boot the system, the Preexisting Installation Configuration window displays. If preexisting configuration information generated by the Answer File Generator and stored on a floppy disc or a USB key exists, you must insert the disc or the USB key and then click Continue. In this case, the Installation wizard reads the configuration information from the

USB key. If no configuration file on a USB key is provided, the Installation wizard prompts for configuration data. Figure 3-3 shows this install process.

Figure 3-3 Basic Installation Flow (Preinstalled)

Figure 3-3 Basic Installation Flow (Preinstalled)

The only difference to a basic installation executed from the installation DVD is the ability to skip over the configuration portion by providing a configuration file on a USB key.

The Answer File Generator is a web-based tool available at Cisco.com that provides the answer file based on the form entries that the user has filled out. The Answer File Generator was located at http://www.cisco.com/web/cuc_afg/index.html at the time of this writing. A Cisco.com search for "Answer File Generator" will provide a link to the current version of the tool.

Upgrade During Install

Service releases, engineering special updates, and security updates may be installed during Basic installation. To install, make sure the additional release is downloaded and prepared on a DVD or FTP/SFTP server before starting the installation. Click Yes in the Apply Additional Release window.

The installation starts when the server is booted from the installation DVD. Verify the checksum for the DVD, and click Overwrite Hard Disk.

In the Platform Installation wizard, click Yes in the Apply Additional Releases window. Then the installation of the operating system and application will start; when finished, the system reboots.

After reboot, choose the upgrade retrieval mechanism:

■ Local: Specify path and filename on the local DVD.

■ FTP/SFTP: Configure network settings and enter the location and login information for the remote file server.

The upgrade will start, and the appliance server will reboot when the upgrade is complete. Figure 3-4 and Figure 3-5 show the entire process.

Figure 3-4 Upgrade During Installation Flowchart (1 of 2)

Figure 3-4 Upgrade During Installation Flowchart (1 of 2)

Figure 3-5 Upgrade During Installation Flowchart (2 of 2)
Cucm Upgrade Process

Table 3-2 outlines the information required to configure the remote path, which includes the location and login information necessary for CUCM to access patches to the product via the file transfer mechanism specified.

Table 3-2 Remote Path Information Description

Field

Description

Remote Server Name or IP

IP address of the FTP/TFTP server. If using a hostname, ensure that the DNS is configured and that the hostname can be resolved to a valid IP address.

Patch Directory

Specifies the directory path for the patch.

Remote Login ID

Login ID for the FTP or SFTP servers.

Remote Password

Remote passwords for the FTP or SFTP server.

SFTP

Specifies the filename for the patch.

Windows Upgrade

When upgrading from Windows-based CUCM (Version 4.x) to the appliance-based CUCM Version 5.x or 6.x, all the configuration and runtime data has to be exported from the Microsoft SQL database and transformed to the new format of the Informix database. These tasks are performed by the Cisco DMA tool.

To perform the Windows upgrade installation, click Yes in the Import Windows Data window. After the installation of CUCM 6, the configuration data will be retrieved from tape or an FTP/SFTP source. This installation option requires that you run DMA on the Windows-based CUCM 4.x version before the upgrade installation.

The Cisco DMA needs to be installed and run on the CUCM 4.x publisher server. The backup file created by DMA must be saved to a tape drive or to a network location.

The CUCM 6.0(1) publisher installation procedure then retrieves the DMA backup file via SFTP/FTP or from the tape and migrates CUCM 4.x data into CUCM Version 6.0(1).

Installation of CUCM subscribers follows the publisher installation. Subscribers pull data from the publisher database; therefore, no DMA files are loaded during the installation of a subscriber.

Figure 3-6 DMA Overview

Cisco Unified CallManager 4.2(3) Publisher

Network Share Server

Figure 3-6 DMA Overview

Cisco Unified CallManager 4.2(3) Publisher

Windows oo:

DMA Exports TAR File or Tape

S/FTP

Unified CM 6.0(1) Installation Imports File

Unified CM 6.0(1) Publisher

Unified CM 6.0(1) Publisher

Appliance

Caveats to keep in mind when using the DMA include the following:

■ Customized music on hold (MOH) files have to be backed up manually to be reinstalled on all CUCM servers after upgrade to 6.0(1).

■ Special phone load files and background images stored on the TFTP server will also be lost; these files have to be backed up and can be uploaded to the newly installed TFTP server after upgrade.

■ Files on CUCM subscriber servers will not be backed up, because the DMA only runs on the publisher server.

■ The default user ID for the CUCM administrator needs to be set during the CUCM 6.0(1) installation; a default user ID of CCMAdministrator is no longer mandatory.

■ All usernames are migrated, but the passwords and PINs are reset to a default defined during installation. After the upgrade, users can change their passwords and PINs on the CCMUser web pages.

CUCM 5.x and 6.x Upgrades

Updates from appliance-based CUCM versions (5.x) are performed from the CUCM

Operating System Administration web page.

NOTE CUCM Version 5.0 requires an upgrade to CUCM Version 5.1(1) before it can be upgraded to CUCM Version 6.

The system does not have to be rebooted, because the current operating system and application are not overwritten by the new version. Instead, they are installed to a second (inactive)

partition.

The upgrade procedure includes the following steps:

Step 1 Back up the existing CUCM 5.x or 6.x system using the CUCM Disaster Recovery System (DRS).

Step 2 Ensure that the SFTP/FTP server is available to perform the upgrade remotely or that the upgrade image is available on the DVD to perform the upgrade locally.

Step 3 Log in to the Cisco Unified Operating System Administration page and start the upgrade.

Step 4 CUCM upgrades can be done without affecting call processing, and the server can be rebooted later during a service window after the upgrade.

Step 5 Install the updated license file (required when upgrading from 5.x to 6.0).

Dual Partitions

Since Release 5.x, CUCM supports dual partitions, which simplify software updates:

■ Each partition keeps one version of the CUCM software and databases.

■ Operation continues during upgrades.

■ Upgrade installs to the inactive partition.

■ During reboot, versions (active and inactive partitions) can be swapped. The previously active partition becomes inactive and retains "old" software and databases until the next upgrade. Any changes made to the active partition are not replicated to the inactive partition. All changes made since the upgrade are lost when reverting.

■ If versions are switched again before the next upgrade, you revert to the previous version (downgrade).

An upgraded system always maintains two versions of software (does not apply to upgrade from 4.x).

Was this article helpful?

+2 -1

Responses

  • michelle
    Which options are the hardware requirements for a cisco ucm installation?
    1 year ago
  • melanie
    Where is cucm admin window?
    11 months ago
  • MICHELLE EICHEL
    What can ccum be installed on?
    9 months ago
  • phoebe
    Can cucm operate on certificate without dns?
    7 months ago
  • Sammy
    How to upgrade cucm publisher and subscriber?
    12 hours ago

Post a comment