In case of a High Availability setup, initiate the switch-version process through Cisco Unified Operating System Administration web interface or CLI after completing the software upgrade installation on both the publisher and subscriber nodes, with publisher being the first, followed by the subscriber node. To identify whether the switch-version is successful, follow the steps mentioned below after triggering the switch-version process. The time needed to trigger the switch-version process will depend on the amount of data available.
Warning: If you are upgrading Unified CCX in a two-node (high availability) deployment, once you complete the switch version of second node, execute the following CLI command utils uccx dbreplication repair all to remove any data discrepancy between the two nodes.
This command is only available in the High Availability deployment of Unified CCX. This command can be executed on any node. This command repairs mismatched data between cluster nodes; it does not repair replication setup. The command initiates the repair which executes in the background. The user would have to go to data store control centre in serviceability administration to monitor the status of the repair process. For more information, see the Cisco Unified CCX Serviceability Administration Guide available here:
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.