The 'roll back' procedures on this page describe how to restore your previous version of SBC Edge (SBC) in the unlikely event that you encounter an issue with your SBC Edge upgrade.
Prior to rolling back your SBC Edge upgrade, ensure that you have a backup of your SBC Edge data for the version you intend to roll back to.
Do not attempt to restore your version 3.0 or earlier SBC Edge configuration from a backup made using version 3.1 or higher release. Doing so will result in a complete user lockout and the system must be reset to factory default to recover.
Downgrading a node that has a value license or a Revised ASM (type Pentium or type Xeon) from release SBC Edge 6.1 to an earlier version is not allowed.
Refer to the appropriate upgrade instructions below for your SBC Edge hardware configuration:
The instructions in this section may be best coordinated with your Sonus service representative.
Similarly to upgrading, to ensure the Sonus can communicate with the ASM, you must downgrade the SBC Edge Communication Service before downgrading the SBC Edge software.
.zip
file for the version that you are downgrading to..zip
file and unpack it to a temporary folder. This will produce a Setup.msi
file.Setup.msi
onto a local folder directly onto the ASM.If you are downgrading from 2.0.x (or later) to → 1.3.x (or earlier), all disabled Network Adapters on the ASM must be enabled. This is because the 2.0.x (or later) upgrade disables one of the network adapters (by design), and it must be re-enabled if you're downgrading to 1.3.x (or earlier).
Once the network adapter is enabled, you must set the necessary permissions to allow the downgraded SBC Edge Communication Service to Install ASM packages via the Sonus SBC Edge WebUI.
You now may proceed with rolling back the SBC Edge software version, follow the instructions below
The Sonus SBC 1000/2000 keeps its system software (firmware) in containers known as "Application Partitions". There are two application partitions, one of which is Active. When the Sonus SBC 1000/2000 system is operational, it is running off of the Active Partition, and the remaining (inactive) partition serves as a spare.
You can rollback to the previous SBC Edge version stored in the inactive partition:
This completes the rollback procedure.