This section describes upgrading the
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 BMC 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.
Ensure that the following requirements are met prior to performing an upgrade or LSWU:
- Ensure the value of the flag,
tgMtrgReqMaxBw
, is twice the value of the flagtgMtrgBwPerReq
. Refer to SIP Trunk Group - TG MTRG Req Max BW - CLI fortgMtrgReqMaxBw
configuration details. Ensure the value of the flag,
tgMtrgReqMaxCalls
, is twice the value of the flagtgMtrgCallsPerReq
. Refer to SIP Trunk Group - TG MTRG Req Max Calls - CLI fortgMtrgReqMaxCalls
configuration details.
Procedure
This procedure is service impacting.
The BIOS firmware upgrade is not part of the SBC application upgrade in
When upgrading from release 9.0 and above, upload the SHA256 checksum file. Otherwise, use the MD5 file.
The following procedure describes
- 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.
- Validate the SBC SHA256 checksum using the checksum calculator. See Validating Checksum with 'Checksums Calculator' for guidance.
Launch EMA.
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
Navigate to Administration > System Administration > File Upload to upload the SBC application package to the active and standby SBC servers.
Click File Upload tab.
File Upload Screen
Click Add Files to Queue.
Browse for the SBC application package files in the File Upload screen and click Open.
Selecting SBC application package
The files are listed in the Upload Queue section. Click Upload All Files. The file upload starts.
Files on SBC
- Repeat steps "a" through "e" for the standby SBC server.
Stop the application on the active server using Administration > System Administration > Platform Management > Stop SBC Application.
Stopping the application is a service-affecting operation.Stopping SBC Application in Active Server
Click OK to continue the stop operation.
Confirming Stop SBC Application
The application stops on the active server.
Launch the EMA Platform Mode on the standby server.
NoteOnce the active server (WFDSBC01a) is stopped, the standby server (WFDSBC01b) automatically becomes active.
Stop the application on the standby server using Administration > System Administration > Platform Management > Stop SBC Application.
Stopping the application is a service-affecting operation.Stopping SBC Application on Standby Server
Click OK to continue the stop operation.
Confirming Stop Application
The application stops on the standby server.
Application Stopped on Standby Server
NoteIf 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.
From the EMA of the initial active server (WFDSBC01a), navigate to Administration > System Administration > Software Install/Upgrade.
Select the SBC Package Name to upgrade, and click Standalone Software Upgrade.
NoteBecause 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.
Selecting SBC Package
The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.
Verifiying Package Integrity
Click Start Upgrade.
Selecting Offline Upgrade
The upgrade process starts on the active server (WFDSBC01a) and displays the upgrade status in the Upgrade Log section.
Performing pre-install checks and DB install
NoteYou may lose connectivity to the browser session when the server reboots.
NoteThis 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.
Log on to EMA using the default credentials.
Logging On to EMA Platform
Logging On to EMA Platform
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.
Verify the SBC application status on the Administration > System Administration > Platform Management screen.
Verifying Active SBC Status
NoteOnce 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.
Follow steps 11 through 16 to perform an upgrade on the standby server (WFDSBC01b).
NoteIf you are upgrading an SBC SWe deployment, power-on the standby instance from the host before returning to step 11.
Verify the SBC application status on the Administration > System Administration > Platform Management screen.
Verifying Standby SBC Status
Verify the firmware, ConnexIP OS and SBC application versions in Monitoring > Dashboard > System and Software Info.
System and Software Information for Active Server
System and Software Information for Standby Server
Verify the system sync status is in Sync Completed state in All > System > Sync Status.
System Sync Status