The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Follow these guidelines if you are using Cisco Prime Collaboration Deployment to upgrade Cisco Unified Communications Manager to release 10.5(2):
PCD upgrades or non-PCD upgrades from release 10.0(1) or 10.5(1) are supported. Migrations from 10.0(1) or 10.5(1) using Prime Collaboration Deployment are not supported. For definitions of migrations and upgrades, see the latest release of the Cisco Prime Collaboration Deployment Administration Guide. For additional details, see CSCur99079.
Before upgrading to release 10.5(2), you must download and install the COP file ciscocm.version3-keys.cop.sgn on every node in the cluster prior to upgrading. This Cisco Options Package (COP) file has the RSA keys that are required to validate the upgrade.
If you are upgrading from 6.1(5), 7.x, 8.x, 9.x, or 10.x, you must disable the time synchronization between the VM instance and the ESXi. To disable the time synchronization issue, follow the instructions at the following URL:
An alternative method is to configure the ESXi server and the Cisco Unified Communications Manager publisher node to point to the same NTP server.
This resolves CSCur94973.
You can download COP files from the following location on cisco.com:
This update resolves CSCup45479.
The document Migration to Cisco Unified Communications Manager Release 10.5(1) Using Prime Collaboration Deployment contains conflicting information if you are upgrading from Cisco Unified Communications Manager release 6.0(1). If you are upgrading from that release, you must first upgrade to release 6.1(2). From 6.1(2), you can then upgrade to 6.1(3), then 6.1(5), then 10.5(1) through Cisco Prime Collaboration Deployment.
Cisco only supports virtualized deployments of Cisco Prime Collaboration Deployment. Cisco Prime Collaboration Deployment is deployed using an OVA that contains the pre-installed Cisco Prime Collaboration Deployment application. This OVA is obtained with a licensed copy of Cisco Unified Communications Manager Release 10.5(1) software. For information about how to extract and deploy the PCD_VAPP.OVA file, see topics relating to the installation of Cisco Prime Collaboration Deployment in the Cisco Prime Collaboration Deployment Administration Guide.
For more information about the deployment of Cisco Prime Collaboration Deployment in a virtualized environment, see:
If you require DNS on a Cisco Prime Collaboration Deployment system, be sure to administer the DNS during Cisco Prime Collaboration Deployment install.
A Cisco Prime Collaboration install task assumes that all cluster nodes are being installed at the same time. You can not, for example, use a migration task to migrate a Cisco Unified Communications Manager Release 6.1(1) cluster to Release 10.5(1) and then use a separate install task to add IM and Presence Service nodes to the same cluster.
Before you perform an install or migration task, copy your ISO files to the fresh_install folder and make sure that those files contain the following permissions: rw-r-r.
This information addresses CSCum18394.
For a migration from Release 10.0(1) to Release 10.5(1) to be successful, you must upgrade all source cluster Cisco Unified Communications Manager nodes to 10.0(1)SU1, at a minimum, before using Cisco Prime Collaboration Release 10.5(1) to perform a migration.
This information addresses CSCui69450.
If you start a new upgrade task before the previous upgrade task finishes, you are notified immediately that this scenario is not supported.
Readdress tasks that require gateway and subnet changes may cause the readdress task to fail.
Cisco Prime Collaboration Deployment can lose the communication with Cisco Unified Communications Manager due to network issues, even after the readdress task is completed successfully on the Cisco Unified Communications Manager. Users may need to complete post network change steps outlined in the Changing the IP Address and Hostname for Cisco Unified Communications Manager Guide before proceeding to the next step.
Cisco Unified Communications Manager IM and Presence Service readdress is not available on Cisco Prime Collaboration Deployment. The Readdress feature can only be used to change hostnames and IP Addresses for Cisco Unified Communications Manager servers. In a cluster with both Cisco Unified Communications Manager and IM and Presence Service nodes, the readdress feature can be used to change the Cisco Unified Communications Manager server hostname and IP addresses, but not the IM and Presence Service nodes for that cluster.
For information about upgrading Cisco Prime Collaboration Deployment, as well as requirements for hardware and software, see the latest release of the Cisco Prime Collaboration Deployment Administration Guide here http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-user-guide-list.html.
Cisco Prime Collaboration Deployment supplements but does not replace native application install and upgrade functionality. Cisco Prime Collaboration Deployment does not have 100% feature parity with native install and upgrade functionality. When troubleshooting upgrade or install issues on Cisco Unified Communications Manager or Cisco Unified Communications Manager IM and Presence Service nodes, the upgrade (or install) logs will need to be retrieved from node being upgraded. Use normal upgrade and install troubleshooting actions.
Not all versions of supported applications can be upgraded to Release 10.x using Cisco Prime Collaboration Deployment. See Supported Releases for more information.
Cisco Prime Collaboration Deployment is not compatible with all license feature levels of VMware vSphere ESXi, as some license feature levels do not enable required VMware APIs.
The following are compatible with Cisco Prime Collaboration Deployment:
Cisco UC Virtualization Foundation (appears as "Foundation Edition" in vSphere Client)
The following are not compatible with Cisco Prime Collaboration Deployment: