CUCM Installation and Upgrade Overview Windows Upgrade Best Cisco CCNA Institute in Gurgaon

Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192

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
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.
Cisco Unified
CallManager
4.2(3) Publisher
Unified CM
6.0(1) Publisher
Network Share
Server
S/FTP
Appliance
Unified CM
6.0(1)
Installation
Imports File
DMA
Exports TAR
File or Tape
DMA
CUCM Installation and Upgrade Overview 67
■ 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.
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).
NOTE CUCM Version 5.0 requires an upgrade to CUCM Version 5.1(1) before it can
be upgraded to CUCM Version 6.
68 Chapter 3: Installation and Upgrade
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).