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.
This feature is introduced to optimize the upgrade sequence of products to reduce the upgrade time or to minimize the impacted procedures during the upgrade. With this release, Cisco Prime Collaboration Deployment includes the following upgrade sequence optimization and support:
Provide direct refresh upgrade support for Cisco Unity Connection and Cisco Unified Contact Center.
Load upgrade sequence based on the type of upgrade (direct standard upgrade or direct refresh upgrade).
For direct refresh upgrades, wait for database replication for Cisco Unified Communications Manager cluster before proceeding to an upgrade or switch version task for IM and Presence cluster.
Report database replication status on Cisco Unified Communications Manager cluster. IM and Presence cluster upgrade or switch proceeds after successful database replication.
Provide parallel upgrade support for both Cisco Unified Communications Manager subscriber nodes and IM and Presence publisher node and subscriber nodes.
Provide detailed information for each upgrade step to indicate the type of upgrade and the inactive and active versions of a product.
Use Cisco Prime Collaboration Deployment to perform the following types of upgrade tasks:
Direct standard upgrade—This upgrade does not require upgrades to the embedded operating system. You can install upgrade software on your server while the system continues to operate.
Direct refresh upgrade—This upgrade is required in situations where incompatibilities exist between the old and new software releases. For example, a refresh upgrade is required when the major version of the embedded operating system changes between the version you are upgrading from and the version that you are upgrading to.
You can perform refresh upgrade to upgrade from existing version of a product to a later version where operating systems of both the versions are different. The supported products for this upgrade are Cisco Unified Communications Manager, IM and Presence Service, Cisco Unity Connection, and Cisco Unified Contact Center Express.
In the earlier releases, after direct refresh upgrade, even though Cisco Unified Communications Manager was upgraded to the new version, it used to switch back to its older version. The new version used to be an inactive version. For the new version to be the active version, switch version was required. The switch back used to happen because upgrade and switch version were two separate steps. It implies that the version had to be switched twice to make the new version after direct refresh upgrade.
To prevent switch version twice, in this release, Cisco Prime Collaboration Deployment includes switch version step as part of upgrade step during refresh upgrade. Check the Automatically switch to new version after successful upgrade check box in the Upgrade Task window during upgrade task configuration. Then, the switch version of the product (either Cisco Unified Communications Manager or IM and Presence Service) is included as part of the upgrade step. However, the switch version step appears as a separate step if the upgrade is for Cisco Unified Communications Manager and IM and Presence Service cluster.
Database replication is one of the steps of refresh upgrade process. Cisco Prime Collaboration Deployment runs services and commands and waits for the database replication status of the selected Cisco Unified Communications Manager nodes.
For more information, see the "Sequencing Rules and Time Requirements" chapter of the Upgrade and Migration Guide for Cisco Unified Communications Manager and IM and Presence Service at http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/tsd-products-support-series-home.html.
Note | Cisco Prime Collaboration Deployment checks the database replication when you choose the cluster that is combined with Cisco Unified Communications Manager and IM and Presence Service. The database replication runs only for Cisco Unified Communications Manager before the IM and Presence Service upgrade or switch. |
Only after successful database replication, the next task that is listed in the upgrade sequence starts. The tasks listed after database replication include upgrade or switch version of IM and Presence Service subscriber nodes.
You can use Cisco Prime Collaboration Deployment to perform upgrade and migration tasks for Unified Communications applications. The following tables list the upgrade and migration tasks that Cisco Prime Collaboration Deployment supports for each application along with the supported version.
Note | The releases listed in the tables do not specify the Engineering Special (ES)/ Service Update (SU) versions. To upgrade or migrate to ES/SU versions, see the release notes of the corresponding product, such as IM and Presence, Cisco Unified Communications Manager, and Cisco Unity Connection. |
Note | Cisco Prime Collaboration Deployment supports the destination version 10.x and above for an upgrade or a migration. The application versions 10.x and above support virtualization. If the source version is 8.x or 9.x on virtual machine, the upgrade task can upgrade to 10.x and above. However, if the source version is 8.x or 9.x on MCS, the upgrade task is not supported. A migrate cluster task can migrate from any of releases listed in the tables to 10.x or higher version on a virtual machine. The migration can happen irrespective of whether the application is on MCS 7800 or virtual machine. |
Task |
Release |
---|---|
Cluster Discovery |
6.1(5), 7.1(3), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2), 11.0(1), 11.5(x) |
Migrate Cluster (Install Application and Import Data from Old System) |
From 6.1(5), 7.1(3), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2), 11.0(1), 11.5(x) To 10.x, 11.0(1), 11.5(x) |
Upgrade Cluster (Upgrade Application Version or Install COP Files) |
From 8.6(1), 8.6(2), 9.0(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2), 11.0(1), 11.5(x) To 10.x, 11.0(1), 11.5(x) |
Restart |
8.6(1), 8.6(2), 9.0(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2), 11.0(1), 11.5(x) |
Switch Version |
8.6(1), 8.6(2), 9.0(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2), 11.0(1), 11.5(x) |
Fresh Install New Cluster or Edit or Expand an Existing Cluster |
10.x, 10.5(1), 10.5(2), 11.0(1), 11.5(x) |
Readdress (Change Hostname or IP Addresses for One or More Nodes in a Cluster) |
10.x, 11.0(1), 11.5(x) |
Task |
Release |
---|---|
Cluster Discovery |
8.5(x), 8.6(x) |
Migrate Cluster (Install Application and Import Data from Old System) |
From 8.5(4), 8.6(3), 8.6(4), 8.6(5) To 10.x, 11.0(1), 11.5(x) |
Upgrade Cluster (Upgrade Application Version or Install COP Files) |
From 8.6(3), 8.6(4), 8.6(5) To 10.x, 11.0(1), 11.5(x) |
Restart |
8.6(3), 8.6(4), 8.6(5) |
Switch Version |
8.6(3), 8.6(4), 8.6(5) |
Fresh Install New Cluster or Edit or Expand an Existing Cluster |
Not applicable |
Readdress (Change Hostname or IP Addresses for One or More Nodes in a Cluster) |
Not applicable |
Task |
Release |
---|---|
Cluster Discovery |
9.0(1), 9.1(1), 10.x, 11.0(1), 11.5(x) |
Migrate Cluster (Install Application and Import Data from Old System) |
From 9.0(1), 9.1(1), 10.x, 11.0(1), 11.5(x) To 10.x, 11.0(1), 11.5(x) |
Upgrade Cluster (Upgrade Application Version or Install COP Files) |
From 9.0(1), 9.1(1), 10.x, 11.0(1), 11.5(x) To 10.x, 11.0(1), 11.5(x) |
Restart |
9.0(1), 9.1(1), 10.x, 11.0(1), 11.5(x) |
Switch Version |
9.0(1), 9.1(1), 10.x, 11.0(1), 11.5(x) |
Fresh Install New Cluster or Edit or Expand an Existing Cluster |
10.x, 10.5(1), 10.5(2), 11.0(1), 11.5(x) |
Readdress (Change Hostname or IP Addresses for One or More Nodes in a Cluster) |
Not Supported |
Task |
Release |
---|---|
Cluster Discovery |
8.5(1), 9.0(1), 9.0(2), 10.x, 11.0(1), 11.5(x) |
Migrate Cluster (Install Application and Import Data from Old System) |
Not Supported |
Upgrade Cluster (Upgrade Application Version or Install COP Files) |
From 9.0(2), 10.x, 11.0(1), 11.5(x) To 10.x, 11.0(1), 11.5(x) |
Restart |
9.0(2), 10.x, 11.0(1), 11.5(x) |
Switch Version |
9.0(2), 10.x, 11.0(1), 11.5(x) |
Fresh Install New Cluster or Edit or Expand an Existing Cluster |
10.5(x), 11.0(1), 11.5(x) |
Readdress (Change Hostname or IP Addresses for One or More Nodes in a Cluster) |
10.5(x), 11.0(1), 11.5(x) |
Task |
Release |
---|---|
Cluster Discovery |
8.6(1), 8.6(2), 9.x, 10.x, 11.0(1), 11.5(x) |
Migrate Cluster (Install Application and Import Data from Old System) |
Not Supported |
Upgrade Cluster (Upgrade Application Version or Install COP Files) |
From 8.x, 9.x, 10.x, 11.0, 11.5 To 10.x, 11.0(1), 11.5(x) |
Restart |
8.6(1), 8.6(2), 9.x, 10.x, 11.0(1), 11.5(x) |
Switch Version |
8.6(1), 8.6(2), 9.x, 10.x, 11.0(1), 11.5(x) |
Fresh Install New Cluster or Edit or Expand an Existing Cluster |
10.5(x), 11.0 (1), 11.5(x) |
Readdress (Change Hostname or IP Addresses for One or More Nodes in a Cluster) |
10.5(x), 11.0 (1), 11.5(x) |