Use this task to perform a product upgrade to increase the capacity of each service in the cluster and also add a new service or feature.
Before you begin
Obtain a copy of the cluster configuration spreadsheet and revise it as instructed by your solution documentation.
Procedure
Log in to Cluster Control Manager using your customer account.
Use a utility, such as WinSCP, to transfer the solution configuration spreadsheet to the ~/artifacts directory.
Enter the screen command to run the upgrade in the background.
Enter the ccm upgrade spec <cluster-config>.xlsx --products --force command and wait for upgrade to complete successfully.
When prompted, type y to confirm the requested products to upgrade to the new versions specified in the solution spreadsheet and to accept the warning reminding you to start a screen session.
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.
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.
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.
Optional To monitor the progress of the upgrade, run the tail -f /var/log/avaya/ccm/ccm-main.log command.
Wait approximately 30 minutes, then run ccm smoke-test on Cluster Control Manager and confirm that all tests pass.If ccm smoke-test fails, run it again in 10 minutes. If the test continuously fails for over an hour, contact your technical support representative.
After infra upgrade, if mstr pods are in 0/1 state then delete the pod and wait till it comes up in good state.
Use the following commands to stop and start the mstr pods.
To stop the mstr pods, run
k scale deployment mstr-srv --replicas=0 -n mstr
Wait till the command completes. Then run
k scale deployment mstr-web --replicas=0 -n mstr
Ensure that the pods are not displaying when executing the command k get pods -n mstr.
