SBC Core RAMP support only

Beginning with release 12.0, the SBC Core supports the Ribbon Application Management Platform (RAMP), which replaces the EMS.

However, the EMA, CLI and API will continue to include EMS-labeled parameters and screens to facilitate SBC migrations from older releases. Accordingly, any references to "EMS" in this documentation pertain to the RAMP platform.


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.

In this section:

Related articles:


This section describes the different methods to upgrade the SBC Core 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.

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.

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

    The performance/capacity of the SBC SWe is impacted by the amount of memory assigned to the VM. Review SBC SWe Performance Metrics to see the memory requirements for the current release plus a procedure to upgrade memory, if required. 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.
  • Check minimum disk space requirements: 

    The amount of disk space used during the upgrade process depends on how the hypervisor internally handles the disk lifecycle for an instance. The following table provides 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.


Note

To recover from a mismatch in session estimates in an HA pair, refer to Recovering from Default Indices in 1:1 HA SBC SWe, if applicable.

Note

The E1000E network interface type is unsupported in VMware.


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.

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.


Note

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



Notes for Performing Upgrade from 11.1.0x Release

On a SBC 7000 setup, the active node takes more than expected the time for the services to come up after an upgrade to V12.00.00R000 from 11.1.0x. Before performing an upgrade from 11.1.0x, apply the following steps:

  1.  Confirm that the cnixpmadmin password is not default by running the following command as root on the active and standby nodes:
    $ENCRYPTED_STORE_SH cnxipmadmin
    NOTE: The command must not show the default password "Cnx1PmAdm1n"
  2. If the password is still default, randomize the password by running the following command as root on the active node:
    $CHANGE_DEFAULT_PASSWDS_SH
  3. Check the cnxipmadmin password is updated to random on the active and standby node by running the following command:
    $ENCRYPTED_STORE_SH cnxipmadmin