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.
With this release, when you perform any upgrade from 12.5 to 12.5 and above, the direct standard upgrade sequence does not allow you to run the switch version on IM and Presence publisher and Cisco Unified Communications Manger subscriber in parallel.
You can perform the switch version on the Cisco Unified Communications Manager subscriber first and then IM and Presence publisher.
With this release, Cisco Prime Collaboration Deployment supports chaining of install, migrate, and upgrade task. Cisco Prime Collaboration Deployment can handle multiple COP files in a single task without any manual intervention. You can make a task dependent on an existing task. Dependent task is triggered automatically on the successful completion of an existing task. This feature helps you to perform install, upgrade, and migration tasks without manual intervention, so that you can efficiently handle upgrades of large or geo-distributed environments.
Install Upgrade Patch—Enables you to install patch files on freshly installed clusters chained to the install task on Prime Collaboration Deployment.
For example: Fresh install task for 10.5 followed by upgrade task for 10.5 SU3.
Migrate Upgrade Patch—Enables you to install patch files on migrated clusters chained to the migration task on Prime Collaboration Deployment.
For example: Migration task for 10.5 followed by upgrade task for 10.5 SU3.
Multi COP Upgrade—Enables you to upgrade nodes in a cluster chained with multiple cops one after another in a single task without creating separate tasks for each COP file.
 Note |
If the user select the multiple cop files for upgrade then the task sequence will load up according to the selected COP files. |
Note |
Maximum 32 COP files can be selected for a specific product. |
For example:
Fresh install task followed by (separate task) batch-install of a long list of COP files.
If the upgrade task is completed, and a week later you need to do a (separate task) batch-install of a long list of COP files.
(Single task) batch-install a long list of COP files with a Prime Collaboration Deployment upgrade task for direct standard upgrade or direct refresh upgrade.
Multi cluster Upgrade—Enables you to upgrade nodes in a cluster chained with another upgrade task for a different cluster. The task sequence will load up according to the selected cop file.
For example: when a task to upgrade cluster X is successful then the next task to upgrade cluster Y starts automatically.
COP file Installation for Install Task—Enables you to install COP files on a freshly installed cluster.
For example: Fresh install task for 11.5 followed by COP file install task.
COP file Installation for Migration Destination Cluster—Enables you to install COP files on a freshly migrated destination cluster.
For example: Migration task to 11.5 followed by COP file install task.
Upgrade Migrate—Enables you to upgrade a cluster chained with a migration task.
For example: Prime Collaboration Deployment upgrade followed by a Virtual-to-Virtual Prime Collaboration Deployment Migration.
This release of Unified Communications Manager, Cisco IM and Presence Service, Cisco Emergency Responder, and Cisco Prime Collaboration Deployment contain software patches to address the Meltdown and Spectre microprocessor vulnerabilities.
Before you upgrade to Release 12.5(1) or above, we recommend that you work with your channel partner or account team to use the Cisco Collaboration Sizing Tool to compare your current deployment to an upgraded 12.5(1)SU1 deployment. If required, change VM resources to ensure that your upgraded deployment provides the best performance.
Feedback