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 the SBC upgrade is available, it is mainly posted on the SalesForce customer portal. Refer to Downloading the Software from Salesforce for more information.

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 and the RAM upgrade procedure, refer to SBC SWe Performance Metrics.

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 Restoring the SBC Configuration for more information.

Ensure that the following requirements are met prior to performing an upgrade or LSWU to 05.01.02R000 release:

  • Ensure the value of the flag, tgMtrgReqMaxBw, is twice the value of flag tgMtrgBwPerReq. Refer to sipTrunkGroup tgMtrgBwPerReq - CLI for tgMtrgBwPerReq configuration details.
  • Ensure the value of the flag, tgMtrgReqMaxCalls, is twice the value of flag tgMtrgCallsPerReq. Refer to sipTrunkGroup tgMtrgCallsPerReq - CLI for tgMtrgCallsPerReq configuration details.

 

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.

As an SBC Core password security enhancement, 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