Clear the upgrade directory from both servers before reattempting further upgrades using the command rm -fr /var/log/sonus/upgrade/*
under all the following conditions:
The SBC application revert from this release to the previous version is performed using the SBC EMA with the following prerequisites:
The following procedure describes the SBC Core application revert using the EMA:
Navigate to Monitoring > Dashboard > System and Software Info to verify the versions.
(An example screenshot is shown below. Your actual software version may vary).
New Application and OS Version
Navigate to Administration > System Administration screen.
System Administration Screen
Click Revert Software Version.
The Revert Software Version screen is displayed displaying the system or partition for the current version and the older version.
(An example screenshot is shown below. Your actual software version may vary).
Revert Software Screen
A confirmation message appears on the screen informing you this action will change the boot software version to the previous release, plus warn you that this is a service-impacting action. Click Ok to proceed.
The Revert Software application simultaneously reverts both the Active and Standby server. Continuing the revert will reboot the upgraded server(s) to an earlier release. During this process, the browser session is lost necessitating logging back into the session.
The Revert Software starts and changes the boot version to earlier version in both the active and standby server. For example, in this case, it is 06.02.00R000 version. You can see the revert status in the Log section.
Revert Logs
Continuing Revert Operation
Once you see Rebooting message in the logs, log out from the EMA.
Rebooting SBC Platform
The revert operation takes approximately 15 to 20 minutes to complete.
Beginning with 5.0 release, the Platform Manager is integrated into the EMA and hereafter referred to as EMA Platform Mode. So once it is reverted back to 3.x/4.x release, you may only use Platform Manager tool for further upgrades.
The roles of Active and Standby server may interchange depends upon the server, which is booting first. In this case, WFDSBC01b completed the rebooting first and became active.