Page History
This section describes upgrading the
| Spacevars | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
Prior to performing an application upgrade to the 7.1.0 release, upgrade the SBC firmware to the latest version on both active and standby SBCs in an HA pair.
|
...
| Info | ||
|---|---|---|
| ||
Ensure that the following requirements are met prior to performing an upgrade or LSWU to the 07.01.xx release:
|
...
| Info | ||||
|---|---|---|---|---|
| ||||
The BIOS firmware upgrade is not part of the SBC application upgrade in
|
The following procedure describes
| Spacevars | ||
|---|---|---|
|
- 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 md5 checksum using the checksum calculator. See Validating MD5Sum 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.
Caption 0 Figure 1 System and Software Info Screen for Active Server Caption 0 Figure 1 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.
Caption 0 Figure 1 File Upload Screen Click Add Files to Queue.
Browse for the SBC application package files in the File Upload screen and click Open.
noteA new "
qcow2" image file is added to the list of upgrade files for upgrade to 6.0.0 R0 and later releases.For example: "
sbc-V07.01.00R000-connexip-os_06.01.00-R000.qcow2".Caption 0 Figure 1 Selecting SBC application package The files are listed in the Upload Queue section. Click Upload All Files. The file upload starts.
Caption 0 Figure 1 Files on SBC - Repeat steps "a" through "e" for the standby SBC server.
Stop the application on on the active server using Administration > System Administration > Platform Management > Stop SBC Application.
Stopping the application is a service-affecting operation.Caption 0 Figure 1 Stopping SBC Application in Active Server Stopping the application is a service-affecting operation. Click OK to continue the stop operation.
Caption 0 Figure 1 Confirming Stop SBC Application The application
is stoppedstops on the active server.
Launch the EMA Platform Mode on the Standby standby server.
Info title Note Once the active server (WFDSBC01a) is stopped, the standby server (WFDSBC01b) automatically becomes active.
Stop the application on the Standby standby server using Administration > System Administration > Platform Management > Stop SBC Application.
Stopping the application is a service-affecting operation.Caption 0 Figure 1 Stopping SBC Application on Standby Server Stopping the application is a service-affecting operation. Click OK to continue the stop operation.
Caption 0 Figure 1 Confirming Stop Application The application
is stoppedstops on the
Standbystandby server.
Caption 0 Figure 1 Application Stopped on Standby Server Info title 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.
From the EMA of the initial active server (WFDSBC01a), Navigate navigate to Administration > System Administration > Software Install/Upgrade.
Select the SBC Package Name to upgrade, and click Standalone Software Upgrade.
Info title 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.
Caption 0 Figure 1 Selecting SBC Package The The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.
Caption 0 Figure 1 Verifiying Package Integrity Click Start Upgrade.
Caption 0 Figure 1 Selecting Offline Upgrade The The upgrade process starts on the active server (WFDSBC01a) and displays the upgrade status in the Upgrade Log section.
Caption 0 Figure 1 Performing pre-install checks and DB install Info title Note You may lose connectivity to the browser session when the server reboots.
Info title Note This process takes approximately 45 minutes to complete on a single server.
Warning Once the upgrade is successful, clear the browser cache prior to accessing the SBC EMA.
Log on to EMA using the default credentials.
Caption 0 Figure 1 Logging On to EMA Platform Caption 0 Figure 1 Logging On to EMA Platform Verify the SBC installation status on the Administration > System Administration > Software Install/Upgrade screen.
Caption 0 Figure 1 Continuing the SBC Upgrade Wait until the SBC upgrade is complete.
Verify the SBC application status on the Administration > System Administration > Platform Management screen.
Caption 0 Figure 1 Verifying Active SBC Status Info title Note Once all the SBC processes start running, continue upgrading the Standby standby SBC server.
Note If upgrading your SBC from a release prior to 57.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 13 11 through 18 16 to perform an upgrade on the standby server (WFDSBC01b).
Info title Note If 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.
Caption 0 Figure 1 Verifying Standby SBC Status Verify the firmware, ConnexIP OS and SBC application versions in Monitoring > Dashboard > System and Software Info.
Caption 0 Figure 1 System and Software Information for Active Server Caption 0 Figure 1 System and Software Information for Standby Server Verify the system sync status is in Sync Completed state in All > System > Sync Status.
Caption 0 Figure 1 System Sync Status Pagebreak
Overview
Content Tools