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:

  • 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.

Note

To recover from the default indices, refer to MOP to Recover from Mismatch in 1:1 SBC SWe HA Session Estimates, if applicable.

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

When an SBC upgrade is available, the software is posted on the Ribbon Support Portal. Refer to Downloading Software from the Ribbon Support Portal for more information.


Prerequisities

Prior to performing an upgrade on the SBC Core, ensure the following activies are accomplished.

For SBC Core (in general):

  • Before upgrading the ConnexIP OS, firmware, and the SBC application, you must first save the configuration in case you encounter any issues during the upgrade.

  • Before upgrading the application, upgrade the SBC firmware to the latest version on both the active and standby SBCs for an HA pair.

For 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.

    SBC SWe instances configured with only 12 GB of RAM have lower capacity limits than instances with higher memory configurations, thus they may not perform at optimum capacity. Contact your Ribbon representative to order DIMM kits to increase the RAM to 24 GB.

    For SBC SWe memory requirements for the current release, and a procedure to upgrade memory, refer to SBC SWe Performance Metrics.
    Complete the procedure to upgrade memory prior to performing the upgrade.

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


Note

The disk space used during the upgrade process depends on how the hypervisor internally handles the disk lifecycle for an instance.

The following table shows Ribbon's recommendation for extra disk space for different types of nodes/instances:

Note

For proper performance, you must provide the minimum resources shown here.

Node Type

Extra Disk Space*

(in GB)

S-SBC80
M-SBC80
PSX-M360
PSX-S360
PSX-Test360
EMS_SA150

* Extra disk space (in addition to the disk space requirement for the instance) is only applicable during the upgrade process.

Total disk space requirement during upgrade = Disk Space for the upgraded instance + extra disk space required only during upgrade.

Live Software Upgrade (LSWU)

LSWU allows a user to upgrade the SBC application software on HA pairs without impacting service (dropping calls). This is mainly recommended for HA SBC systems. You can also perform a LSWU on the SBC EMA and in SBC EMA Platform Mode. Refer to Live Software Upgrade using CLI and System Administration - Software Install-Upgrade for more information.

To recover from a mismatch in the session capacity estimates of Active and Standby of 1:1 HA pair, refer to MOP to Recover from Mismatch in 1:1 SBC SWe HA Session Estimates.

Non-Live Software Upgrade (Non-LSWU)

The non-LSWU upgrade process requires taking the SBC system offline to perform an application upgrade. This refers to upgrading the SBC application in a standalone or HA configuration using EMA Platform Mode. Refer to Upgrading SBC Application using EMA Platform Mode for more information.

To recover from a mismatch in the session capacity estimates of Active and Standby of 1:1 HA pair, refer to MOP to Recover from Mismatch in 1:1 SBC SWe HA Session Estimates.


Note

Once the upgrade is complete, rediscover the SBC from the EMS, if present, and edit any attributes that may have been modified post-upgrade. Attributes are listed under the EMS page Register an SBC Core Node.