1 |
Install the signature file and ASC file that you downloaded from the Avaya Support Site or from the Avaya PLDS website. |
Adding the key bundles file and uploading upgrade files to EMS |
|
2 |
Check if the system can be upgraded using the pre-upgrade script. For unsupported servers, the upgrade will fail. |
Running the pre-upgrade check |
|
3 |
Back up your data before starting the upgrade. |
Creating a backup before doing an upgrade |
|
Upgrade Procedures |
|
4A |
Upgrade the standalone EMS and SBC system using the web interface. |
Upgrading a standalone EMS and SBC using the web interface |
|
Upgrade the primary EMS using the web interface. |
Upgrading EMS using the web interface for active-active EMS |
|
Upgrade the secondary EMS using the web interface, if present. While upgrading secondary EMS, the primary EMS must be upgraded and functional otherwise you will not be able to upgrade SBC using secondary EMS. |
Upgrading EMS using the web interface for active-active EMS |
|
Upgrade the single SBC servers using the web interface. |
Upgrading single SBC servers using the web interface |
|
Upgrade the SBC HA pairs using the web interface |
Upgrading SBC HA pair servers using the web interface |
|
Upgrade the EMS and SBC using the CLI. |
Upgrading EMS or SBC using the CLI |
|
4B |
If the upgrade fails for any reason, roll back to the previous release. |
Rolling back an upgrade using the web interface Rolling back an upgrade using the CLI |
|
Upgrade and migration verification |
|
5 |
Check the upgrade status using the following log file: /archive/log/icu/ursbce.log |
|
|
6 |
Use the following command to check the upgrade status: grep UPGRADE_STATE /usr/local/ipcs/etc/sysinfo |
The system displays one of the following messages:
|
|
7 |
Update the server interworking, if required. |
|
|