Related articles:


This section describes upgrading the SBC application in a standalone or HA configuration using EMA. Beginning with the 5.0 release, the Platform Manager is integrated into EMA, and referred to as EMA Platform Mode. 

Note

Prior to performing an application upgrade, upgrade the SBC firmware to the latest version on both active and standby SBCs in an HA pair.

  • Refer to the release notes for the latest firmware version.
  • To upgrade the firmware, refer to Upgrading the BMC and BIOS Firmware.
  • Stop the SBC application on the already upgraded active node, prior to upgrading the standby node. Failure to stop the application on the already upgraded node results into inability to upgrade the standby.
Note

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

Procedure

Warning

 This procedure is service impacting.

Note

The BIOS firmware upgrade is not part of the SBC application upgrade in SBC 7000 platforms. Refer to Upgrading SBC 7000 Series Firmware for more information. 


Note

When upgrading from release 9.0 and above, upload the SHA256 checksum file. Otherwise, use the MD5 file.


The following procedure describes SBC Core application upgrade using the EMA (non-LSWU):

  1. Download the SBC application package from the Ribbon Support Portal to your local folder on a PC or remote server. Refer to Downloading Software from the Ribbon Support Portal.
  2. Validate the SBC SHA256 checksum using the checksum calculator. See Validating Checksum with 'Checksums Calculator' for guidance.

  3. Launch EMA.

  4. Navigate to Monitoring > Dashboard > System and Software Info to verify the software and HA peer status for both active and standby servers.

    System and Software Info Screen for Active Server

    System and Software Info Screen for Standby Server

  5. Navigate to Administration > System Administration > File Upload to upload the SBC application package to the active and standby SBC servers.

    1. Click File Upload tab.

    2. Click Add Files to Queue.

    3. Browse for the SBC application package files in the File Upload screen and click Open.

      • sbc-Vxx.xx.xxRxxx-connexip-os_xx.xx.xx-Rxxx_xx_amd64.qcow2

      • sbc-Vxx.xx.xxRxxx.x86_64.tar.gz

      • sbc-Vxx.xx.xxRxxx.x86_64.sha256

      • sbc-Vxx.xx.xxRxxx.x86_64.signature

    4. The files are listed in the Upload Queue section. Click Upload All Files. The file upload starts.

    5. Repeat steps "a" through "e" for  the standby SBC server.

  6. Stop the application on the active server using Administration > System Administration > Platform Management > Stop SBC Application.
    Stopping the application is a service-affecting operation.

  7. Click OK to continue the stop operation.

    The application stops on the active server.

  8. Launch the EMA Platform Mode on the standby server.

    Note

    Once the active server (WFDSBC01a) is stopped, the standby server (WFDSBC01b) automatically becomes active. 

  9. Stop the application on the standby server using Administration > System Administration > Platform Management > Stop SBC Application.
    Stopping the application is a service-affecting operation.

  10. Click OK to continue the stop operation.

    The application stops on the standby server.

    Application Stopped on Standby Server

    Note

    If you are upgrading an SBC SWe deployment, before starting the upgrade of the active instance, shut down or power-off the standby instance from the host.

  11. From the EMA of the initial active server (WFDSBC01a), navigate to Administration > System Administration > Software Install/Upgrade.

  12. Select the SBC Package Name to upgrade, and click Standalone Software Upgrade.

    Note

    Because you are performing a non-LSWU upgrade and both the active and standby SBCs are down, it is considered a standalone upgrade even for an HA pair. 

     The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.

  13. Click Start Upgrade.

     The upgrade process starts on the active server (WFDSBC01a) and displays the upgrade status in the Upgrade Log section.

    Note

    You may lose connectivity to the browser session when the server reboots. 

    Note

    This process takes approximately 45 minutes to complete on a single server. 

    Once the upgrade is successful, clear the browser cache prior to accessing the SBC EMA.

  14. Log on to EMA using the default credentials.

    Logging On to EMA Platform

    Logging On to EMA Platform

  15. Verify the SBC installation status on the Administration > System Administration > Software Install/Upgrade screen.

    Continuing the SBC Upgrade

    Wait until the SBC upgrade is complete.

  16. Verify the SBC application status on the Administration > System Administration > Platform Management screen.

    Verifying Active SBC Status

    Note

    Once all the SBC processes start running, continue upgrading the standby SBC server. 

     If upgrading your SBC from a release prior to 7.1.x, stop the application on the active server using Administration > System Administration > Platform Management > Stop SBC Application before proceeding to the next step.

  17. Follow steps 11 through 16 to perform an upgrade on the standby server (WFDSBC01b).

    Note

    If you are upgrading an SBC SWe deployment, power-on the standby instance from the host before returning to step 11.

  18. Verify the SBC application status on the Administration > System Administration > Platform Management screen.

  19. Verify the firmware, ConnexIP OS and SBC application versions in Monitoring > Dashboard > System and Software Info.

  20. Verify the system sync status is in Sync Completed state in All > System > Sync Status.