Checklist for upgrade method 3 - Rolling cluster upgrade

Last Updated : Oct 10, 2024 |
Prolog information
An ISO upgrade can fail due to networking and other problems outside the control of Avaya Breeze® platform. If that happens, and the ISO was complete and not truncated by the SFTP file transfer to the VM, you may be able to redo the upgrade.
  • This method is not supported for upgrades to Avaya Breeze® platform R3.9 from earlier releases.
#
Action
Link/Notes
1.
Check the prerequisites and post-upgrade tasks for snap-ins before proceeding with the upgrade.
Refer to the snap-in documentation.
2.
Before upgrading Avaya Breeze® platform, upgrade the following in this order to the required release:
  1. System Manager
  2. Session Manager
See Upgrading Avaya Aura® System Manager and Upgrading Avaya Aura® Session Manager.
If only upgrading the Avaya Breeze® platform Element Manager, use the upgradeSolution script. Refer to Deploying Avaya Breeze® platform.
3.
Upgrade Avaya Aura® Media Server.
See Deploying and Updating Avaya Aura® Media Server Appliance.
Upgrade Avaya Aura® Media Server within the same maintenance window as the Avaya Breeze® platform upgrade.
4.
If you have a cluster database enabled, take a backup.
5.
On the Cluster Administration page, identify the cluster you want to upgrade. For clusters with multiple servers, determine the sequence in which you want to upgrade the servers.
This step is for upgrading Avaya Breeze® platform nodes with snap-ins that support non-service impacting upgrades.
Check your snap-in documentation for specific upgrade considerations.
6.
To upgrade using the ISO file method, download the ISO file and patch file (if required) from PLDS. Confirm the files are complete by running checksum comparisons and then compare to the value on PLDS. If the file is correct, copy the ISO file and the patch file to each Avaya Breeze® platform server you will be upgrading.
For upgrades using SDM:
  • Download the OVA file and patch file (if required) from PLDS. Confirm the files are complete by running checksum comparisons and then compare to the value on PLDS.
  • Download the versions*.xml file.
For more information about SDM upgrades, see Upgrades using Solution Deployment Manager.
7.
Verify that the enrollment password has not expired.
8.
Change the state of the cluster you are upgrading to Deny New Service.
9.
If a cluster database is enabled and the next node is an active node, change the status of the active node to Standby.
10.
Verify that the server Activity field is set to 0.
11.
Take a snapshot of the current VM to enable reverting if necessary.
This task is not required if you are using the SDM upgrade option.
12.
Upgrade the Avaya Breeze® platform software.
To upgrade using the ISO file method, see Upgrading the Avaya Breeze platform server.
For more information about SDM upgrades, see Upgrades using Solution Deployment Manager.
The server reboots automatically when the upgrade script completes.
13.
Install the patch file (if required) .
14.
Upgrade the mandatory snap-ins and connector snap-ins.
For more information, see your snap-in documentation.
15.
Verify data replication between System Manager and Avaya Breeze® platform.
16.
Run Avaya Breeze® platform maintenance tests for the server.
See Running maintenance tests. Resolve errors before proceeding. For information, see Maintaining and Troubleshooting Avaya Breeze® platform.
17.
On the Server Administration page verify the following for the upgraded server:
If using Reliable Eventing Framework, verify that the state of the node changes from Electing to Slave.
Complete this procedure only if you have disabled secure grid for the cluster that contains the servers you are upgrading. This procedure is service impacting.
18.
Change the state to Accept New Service for the upgraded Avaya Breeze® platform node.
19.
Verify the Avaya Breeze® platform SIP entity link with Session Manager.
20.
Repeat steps 7 through 17 for each cluster you are upgrading.
21.
Install new snap-ins.
22.
Set the preferred version for each snap-in.
23.
Test Avaya Breeze® platform snap-ins to verify that they are functioning correctly.
Delete any snapshots that you no longer need.
It is important to delete snapshots you no longer need within 12–24 hours. For more information, see VMware snapshots.
24.
Run a test alarm.