Pre-upgrade checklist

Last Updated : Mar 05, 2024 |
Prolog information
Metadata
Keywords:
Caution:
Doing an upgrade or migration on your system is service affecting. Plan upgrades or migrations for a maintenance period or when there is no traffic or during a low traffic period.
Tasks
References
Install the latest service packs and patches required for the current Avaya SBC system.
Latest software updates and patch information
Ensure that the system does not show any alarms related to disk space.
Checking system alarms
Disable all debug logs.
Disabling debug logs
Ensure that the SBC servers in the deployment have unique host names.
Checking the status of the deployed servers
Ensure that the EMS and SBC are in the commissioned or registered state.
Checking the status of the deployed servers
Ensure that the SBC instances are not in sync state.
To verify whether SBC instances have a problem with synchronization, clone a SigMa profile, save the profile, and then check whether any SBC moves to the sync state.
If any SBC instance is in the sync state, log a ticket with Avaya Support to get the issue addressed.
If you revert the VMware snapshot before upgrading, ensure that you restore the VMware snapshots in the following order:
  1. EMS
  2. SBC
For an SBC HA pair, ensure that the HA state is showing primary and secondary, respectively.
Ensure that you place all manually installed RPMs, which came as a patch, in the following directory:
/archive/SBC-RPM-Repository/RPMs/
Download the upgrade-related files from the Avaya Support Site or from the Avaya PLDS website.
Copy these files to the server on which you are doing the upgrade. If you upgrade using a USB device, ensure that the USB device has at least 4 GB of free space for the upgrade files.
Download upgrade files
View all the downloaded upgrade files that are on your system. You might want to delete any upgrade files that are older than your last two upgrades.
Managing downloaded upgrade packages
Copy upgrade package to Avaya SBC HA pair servers or single Avaya SBC servers.
Copying upgrade package to Avaya SBC HA pair servers or single Avaya SBC server
If you have rolled back before upgrading, ensure that you have rebooted your device before starting the upgrade again.
Upgrades from one major release to another major release require license upgrade. If you are adding new features with an upgrade, you must upgrade your license. You must download the new license and install on it on the WebLM server before you start the upgrade.
About licensing requirements
Note:
You cannot administer an SBC that is on an earlier version than the EMS until you upgrade the SBC to the same version as EMS.