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.
If you encounter an issue during your upgrade and need to rollback to the pre-upgrade version, see Upgrade Guide for Cisco Unified Communications Manager.
Because the migration was done using Prime Collaboration Deployment, the original Cisco Unified Communications Manager cluster is still available on the MCS servers, but in a shutdown state. Rolling back to previous version involves shutting down Cisco Unified Communications Manager 10.5(1) nodes running on virtual machines and bringing-up the Pre-10.5(1) Cisco Unified Communications Manager nodes on MCS servers. This process needs to be done in an ordered sequence to avoid extended downtime for the end users. Review the below information regarding rolling back to Cisco Unified Communications Manager releases prior to 8.0(x)
If you are reverting your cluster to a release prior to 8.0(x), review the following documents, which explain important security-related changes:
Migrating IP Phones Between Clusters with Cisco Unified Communications Manager 8 and ITL Files
Rolling Back the Cluster to a Pre-8.0 Release
When the rollback is completed, execute your test plan again to make sure that all services and features are functioning as expected.