In this section:

Related articles:

Warning

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:

  • Performing LSWU from a pre-5.1 version to a 5.1 or later version.
  • There is a need to revert the upgraded server after a single server upgrade while the peer is still on an older version.
  • A revert will be performed by doing a re-ISO.

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

When the SBC upgrade is available, it is mainly posted on the Salesforce customer portal. Refer to Downloading Software from the Ribbon Support Portal for more information.

Note

Prior to performing an upgrade on the SBC SWe, increase the memory to the larger of:

  • the minimum memory required for the release.
    or
  • the memory required for the desired session capacity.

For SBC SWe memory requirements for the current release, refer to SBC SWe Performance Metrics. Follow the procedure listed in this page to upgrade the system to the required memory, prior to performing the upgrade.

Note

Ensure the SBC SWe memory reservation meets the requirements for the current release. Refer to SBC SWe Performance Metrics.

Note

Before upgrading the 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 Restoring the SBC Configuration. 

Note

Prior to performing an application upgrade to 6.0.0, upgrade the SBC Firmware to the latest version on both Active and Standby SBCs for HA pair.

Live Software Upgrade (LSWU)

LSWU allows the user to upgrade the SBC application software on High Availability (HA) pairs without impacting the service (call drops). This is mainly recommended for HA SBC systems. LSWU can also be performed on SBC EMA and SBC EMA Platform Mode. Refer to Live Software Upgrade using CLI and System Administration - Software Install-Upgrade for more information.

Non-Live Software Upgrade (Non-LSWU)

Non-LSWU upgrade process requires taking the SBC system offline to perform the application upgrade. This section describes upgrading the SBC application in a standalone or HA configuration using the Platform Manager or EMA Platform Mode. The Platform Manager tool is used to upgrade the SBC application from 3.x/4.x release to 5.0 release. Beginning with 5.0 release, the Platform Manager is integrated into the EMA and hereafter referred to as EMA Platform Mode. Thus, post 5.0 SBC application upgrades are performed using the EMA.

Refer to Upgrading SBC Application Using Platform Manager or Upgrading SBC Application using EMA for more information.

Note

SBC Core User passwords automatically expire after upgrading to 5.1.x. As a result, users are required to change their passwords upon initial login immediately following the upgrade. 


  • No labels