Cisco Prime Collaboration
Deployment is a migration application for Unified Communications applications.
Beginning with release 10.0(1) Cisco Unified Communications Manager supports
only virtual machines and does not support physical servers. Prime
Collaboration Deployment 10.5(1) allows customers to migrate their existing
clusters deployed on physical servers to Cisco Unified Communications Manager
Release 10.5(1) on virtual machines. When you have a pre-10.0(1) Cisco Unified
Communications Manager cluster that is running on a physical machine and you
use Prime Collaboration Deployment to migrate to Cisco Unified Communications
Manager 10.5(1) running on virtual machines this process is referred to as M1
This document describes the
migration procedures for Cisco Unified Communications Manager Release 10.5(1)
from the following releases.
Migration to Cisco
Unified Communications Manager Release 10.5(1) using Prime Collaboration
Deployment is supported only for the Cisco Unified Communications Manager
versions listed in the Introduction section. Upgrading directly to Unified
Communications Manager Release 10.5(1) from Releases 4.1(3), 4.2(3), 4.3(2),
5.1(2), 5.1(3), 6.0(1), 6.1(1), 6.1(2), 6.1(3), 7.0(1), 7.0(2), and 7.1(2) is
releases, you must upgrade to an intermediate release before you use the M1
migration procedure to Migrate to Unified Communications Manager Release
10.5(1). Perform the migration by performing the following tasks:
Unified Communications Manager Release 6.1(5) or 7.1(5) as an intermediate
Collaboration Deployment on a virtual machine.
Collaboration Deployment for Cisco Unified Communications Manager cluster
migration to Release 10.5(1).
current Unified Communications Manager to release 10.5(1) using Prime
process in this document is applicable to Unified Communications Manager
clusters with the following environment:
One of the
following Unified Communications Manager releases is installed: Releases
4.1(3)–4.3(2), Releases 5.1(2)-5.1(3), Releases 6.0(1)-7.1(5), or Releases
Communications Manager cluster is installed on Cisco Media Convergence Server
procedure requires licensing for Unified Communications Manager 10.5(1). The
licenses required for this migration are:
Manager Release 10.5(1)
migrate to Unified Communications Manager Release 10.5(1) from earlier
versions, install all previously purchased license files on Unified
Communications Manager before beginning the migration. If you do not install
all previously purchased license files, your unclaimed licenses will not be
available to your upgraded Unified Communications Manager. You cannot be
reinstall licenses after the upgrade.
To support high
availability, Unified Communications Manager Release 10.5(1) clusters operate
in a full-featured demo mode for 60 days without a license. After 60 days,
Unified Communications Manager clusters continue to operate and route calls,
but the functionality to add or remove devices and users is disabled until
valid licenses are available on the associated Prime License Manager (PLM).
Refer to the
license documentation posted at Migration Central for additional information:
To determine if
the versions of the devices and applications in use in your organization—such
as endpoints, gateways, voicemail, presence, or other applications—are
supported by this release of Unified Communications Manager, review the
that you consider the compatibility of applications such as Cisco IM and
Presence Service, Attendant Console, Cisco Contact Center Express (UCCX) and
Cisco Emergency Responder (CER) for upgrades.
IM and Presence
needs to be upgraded in the same maintenance windows as Cisco Unified
Communications Manager. Please refer to the following documentation for
additional information on compatibility.
applications, review the application catalog at the following link to verify
that this release of Unified Communications Manager supports the application.
If your application is not listed in the catalog, confirm with your vendor that
the application is compatible with this release of Unified Communications
recommends that you review the list of open caveats for your intermediate and
targeted Unified Communications Manager releases that may impact functionality
or integration with other applications. You can find the list of open caveats
in the Release Notes at the following location:
You need to
design your Unified Computing Servers (UCS) system for virtualization. Most
deployments require high availability and thus need planning for the type and
number of UCS servers. You also need to plan for storage, server connectivity,
and ESXi version. You can find details regarding designing a virtualized
environment at the following link:
of Unified Communications Manager Release 6.1(5) (Applicable only if you are
running Unified Communications Manager Release 4.x).
current configuration and login information for your current Unified
Communications Manager nodes in case any issues are encountered during the
upgrade procedure. Review the Unified Communications Manager Real-Time
Monitoring Tool (RTMT) and syslogs and address any errors before obtaining the
hostnames, gateways, domain names, DNS servers, NTP servers, and SMTP
cluster security, and Certificate Trust List (CTL) security token passwords
versions and time zones
running on each server and associated activation status
Record server configuration and any additional information
information and access details
Determine the registration counts by using RTMT or the Unified
Communications Manager device count summary. For each Unified Communications
Manager node, record the number for each device type that is displayed. For
example, the number of each type of registered IP phone and gateway, and each FXS,
FXO, T1CAS, PRI, MOH, MTP, CFB, or XCODE device resource.
This document assumes that the Unified Communications Manager cluster
will have a Unified Communications Manager publisher and a Unified Communications
Manager TFTP node that will not have any registrations of IP phones or devices.
All registrations will be to the primary Unified Communications Manager
subscribers in the cluster. The backup Unified Communications Manager
subscribers will be used for full registration redundancy. In a two-node
cluster deployment, the publisher node can also be the TFTP server and the
If your cluster
is a mixed-mode cluster, locate your existing security certificate tokens and
record the token information.
Create a post-upgrade test plan that you execute before you upgrade
and directly upgrading. For example, this plan can be a set of tests that cover
different use cases. Run the same tests before and after the upgrade. This
provides a way to verify expected Unified Communications Manager operational
functionality, before, and after, the upgrade.
Communications Manager Backup
recommend that you perform a Disaster Recovery System (DRS) backup of your
entire cluster before each upgrade. Upgrading without a current backup can
result in lost data, lost node configuration, or disruption to services if
there are complications during the upgrade process. Please refer to the
Recovery System Administration Guide
on Cisco.com for additional information DRS backup procedure.
To shorten the
upgrade time, delete or purge Call Detail Records (CDRs) or log files that you
no longer need.
Refer to the
recommended practices for successful migration using Prime Collaboration
Migration. Best practices outline the requirement for TFTP directory size and
WAN bandwidth requirement when Cisco Unified Communications Manager nodes are
deployed across WAN.
If you are a
partner, Cisco recommends that you contact the PDI help desk during the upgrade
planning phase. The PDI team can review the upgrade plan, provide necessary
support, and file a proactive TAC case on your behalf. To contact the PDI team,
http://www.cisco.com/go/pdihelpdesk. If you choose to contact TAC directly,
you must provide the following information for a proactive TAC case:
output from the Unified Communications Manager upgrade readiness application
(web or iPad version)
Information about contact persons and the maintenance window
firmware that corresponds to your release of Unified Communications Manager.
You can apply new firmware files to the endpoints in a controlled manner prior
to the upgrade to minimize phone downtime after an upgrade. Afterwards, restart
the TFTP service on the Unified Communications Manager servers, and restart the
IP Phones in a controlled order to minimize downtime.
download their new firmware after an upgrade. If you apply firmware to phones
in groups ahead of the upgrade, you can eliminate the load on the TFTP server
by preventing phones from upgrading their firmware following completion of the
upgrade. The phone cannot be used for calls when its firmware is being
upgraded. A maintenance window outside your Unified Communications Manager
upgrade window is recommended for phone firmware upgrade