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 chapter explains how to roll back an upgrade.
Caution | Configuration/reporting updates that are made after the upgrade are not be preserved when you roll back. |
Step 1 | Check and Perform Switch
Version
|
Step 2 | Verify Version of Unified CCX
|
Step 3 | Verify Status of
Services
|
Step 4 | Roll Back Unified CCX Clients
|
Step 1 |
Check and
Perform Switch Version. Perform switch version on the first node.
|
Step 2 | Check and Perform Switch Version. Perform switch version on the second node. |
Step 3 | Verify Version of Unified CCX
|
Step 4 | Verify Status of
Services
|
Step 5 | Roll Back Unified CCX Clients
|
Step 6 | Reset Database Replication after Rollback
|
Step 7 | Verify Unified CCX Database Replication
|
Step 8 | Verify Cisco Database Replication
|
If you roll back to an older version of Unified CCX, you must manually reset database replication within the cluster for an HA setup.
Rolling back versions from a later version of Unified CCX to an earlier version does not retain the privileges of Historical Report Users that were created in later version. These users will not have access to Historical Reports. After reverting to the earlier version, update the reporting capability for them.
To update the reporting capability: