The cluster upgrade takes a minimum of one hour. During the upgrade, folders and virtual machines are created on the host machines visible in the vCenter of the host.
Before you begin
Remove the previous version of Async messaging.
Restart the CCM local Docker registry and ChartMuseum processes.
Log in to Cluster Control Manager with your customer account.
Use a utility, such as WinSCP, to transfer the solution configuration spreadsheet to the ~/artifacts directory.
To run the upgrade in the background, at the CCM prompt, type screen.
Go to the directory where solution spreadsheet is copied and run the ccm upgrade spec <solution spreadsheetname>.xlsm --infra --force command.
When prompted, enter your Avaya SSO credentials.
When prompted, type y to confirm the cluster node upgrade to the new version specified in the solution spreadsheet and to accept the warning reminding you to start a screen session.
ADDITIONAL INFORMATION:
Only type y if you have already run screen. Do not continue with the upgrade until you do this.
Failure to run the screen command exits the process and you have to start over.
When prompted, accept the EULA.
ADDITIONAL INFORMATION:
Validation runs after accepting the EULA. If any part of the validation fails, you must address the detected issues and restart the upgrade.
When prompted to perform a backup, enter y or n.
ADDITIONAL INFORMATION:
If you enter y, a backup runs after the upgrade is complete. The backup takes approximately 5 to 10 minutes to complete. If the archive destination is set to Local, the backup file is located at /var/avaya/artifactCache/ccmClusterBackup. If the archive destination is set to Remote, the ccmClusterBackup folder, which contains the backup file, is located in the base directory you specified.
To monitor the progress of the upgrade, run the tail -f /var/log/avaya/ccm/ccm-main.log command.
Check status of the pgo-client pod, it must be up and running.