Skip to end of metadata
Go to start of metadata

This section describes the different methods to upgrade the SBC Core (SBC 5000 series, SBC 7000 series and SBC SWe) application.

When an SBC software maintenance upgrade is available, it is mainly posted on the Sonus TAC site and the SalesForce Global Support Portal. Refer to Downloading the Software from SalesForce for more information.

Live Software Upgrade (LSWU)

LSWU allows the user to upgrade the SBC application software without dropping the active stable calls. This upgrade is mainly recommended for redundant or High Availability SBC systems. Refer to Live Software Upgrade using CLI for more information on LSWU.

Non-Live Software Upgrade (Non-LSWU)

Non-LSWU upgrade process requires taking the SBC system offline to perform the application upgrade. This upgrade is usually performed on standalone SBC systems using the Platform Manager. The Platform Manager is accessed only when the user upgrades the ConnexIP OS version to 1.8.2R0 or higher and SBC version to 3.0.3R0 or higher.

Refer to Upgrading SBC Application Using Platform Manager for more information on SBC application upgrade using the Platform Manager.

Before upgrading ConnexIP OS, firmware, and SBC application, you must first save the configuration. In case you encounter any issues during the upgrade, you need to restore the system and continue the upgrade. For Saving and Restoring the configuration, refer to Saving the SBC Configuration and Reloading the SBC Configuration for more information.

Starting 4.2.4, CPU resource allocation requirements for SWe SBC VM are more strictly enforced than in previous releases.  You must review and verify these VM settings against the documented recommendations under VM configuration Recommendations section (vCPU settings) before upgrading. If the current CPU reservation is not as specified, LSWU procedure needs manual intervention as the application fails to start. If you encounter this problem, correct the CPU reservation settings as specified in Step 6 under “Adjust Resource Allocations” section. CPU reservation should be set as “number of vCPUs assigned to VM * physical processor CPU frequency.  If VM has same number of vCPUs as the number of physical logical processors on the server, this reservation may not be possible. In this case, reduce the number of vCPUs assigned to VM by one and set the CPU reservation to the appropriate value.



  • No labels