Ensure that file integrity validation is disabled. You can check this by running clusterFileIntegrity. To disable file integrity validation, run clusterFileIntegrity disable.
You can re-enable file integrity validation after the entire solution upgrade process is complete.
Upgrade Cluster Control Manager and cluster nodes.
If upgrading a multinode cluster, run the checkInfra -p -cn <IPs-FQDNs> command and verify that the cluster IOPS, network latency, and network bandwidth meet the minimum requirements.
For <IPs-FQDNs> specify a comma-separated list of all cluster node IP addresses or FQDNs. This command can take over 15 minutes to complete.
Confirm the following are completed:
The configuration spreadsheet values are correct and saved to the file.
The solution configuration spreadsheet is transferred to the Cluster Control Manager.
Confirm the operational state of the cluster by running the ccm smoke-test and ccm status --pod-details commands before proceeding with the solution upgrade. The status of all services, except for tools-policy and utility-service, should be DEPLOYED. The status of all pods should be RUNNING or COMPLETE.
When a service fails, you must delete and reinstall the service before you can deploy another service. If you require additional assistance, contact Avaya Support personnel.
Note:
ccm smoke-test shows a different value for the number of pods than what was reported for the previous version of Cluster Control Manager. If this command reports fewer pods than expected, then you must resolve this issue before you proceed. For example, if it reports 55 out of 60 pods, then you must investigate and resolve this issue.
Take note of the index patterns in use on the logging service (Kibana). You will need to manually recreate them after the upgrade process is complete.
Prestaging artifacts is non-service impacting and can be completed outside of a maintenance window.