This section describes upgrading the
Unable to show "metadata-from": No such page "_space_variables"
application in a standalone or HA configuration using the EMA. 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.Prior to performing an application upgrade to 6.2.0 release, upgrade the SBC Firmware to the latest version on both Active and Standby SBCs for HA pair.
- To know the latest firmware version, refer to Production Releases.
- To upgrade the firmware, refer to Upgrading BMC Firmware.
Ensure that the following requirements are met prior to performing an upgrade or LSWU to 06.02.00R000 release:
- Ensure the value of the flag,
tgMtrgReqMaxBw, is twice the value of flagtgMtrgBwPerReq. Refer to SIP Trunk Group - TG MTRG Req Max BW - CLI fortgMtrgReqMaxBwconfiguration details. Ensure the value of the flag,
tgMtrgReqMaxCalls, is twice the value of flagtgMtrgCallsPerReq. Refer to SIP Trunk Group - TG MTRG Req Max Calls - CLI fortgMtrgReqMaxCallsconfiguration details.
Procedure
Warning
This procedure is service impacting.
The BIOS firmware upgrade is not part of SBC application upgrade in
Unable to show "metadata-from": No such page "_space_variables"
platforms. Refer to Upgrading SBC 7000 Series Firmware for more information.The following procedure describes the
Unable to show "metadata-from": No such page "_space_variables"
application upgrade from version 6.1.0R1 to 6.2.0R0 release using the EMA (Non-LSWU):- Download the SBC application package from the Salesforce customer portal to your local folder on a PC or remote server. To know more on how to download files, refer to Downloading the Software from Salesforce.
- 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.
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 active and standby SBC servers.
Click File Upload tab.
File Upload Screen
Click Add Files to Queue.
Browse the SBC application package files in the File Upload screen and click Open.
A 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-V06.02.00R000-connexip-os_03.04.00-R000.qcow2".Selecting SBC application package
The files are listed in Upload Queue section. Click Upload All Files. The file upload starts.
Uploading SBC package
Files on SBC
- Repeat steps "a" through "e" for Standby SBC server.
Stop the application on Active server using Administration > System Administration > Platform Management > Stop SBC Application.
Stopping SBC Application in Active Server
The stop application is a service affecting operation. Click OK to continue the stop operation.
Confirming Stop SBC Application
The application is stopped on the active server.
Application Stopped on Active Server
Launch the Platform Manager on the Standby server.
After stopping the application on the Active server (WFDSBC01a), the automatic switchover happens and Standby server (WFDSBC01b) becomes active.
Stop the application on the Standby server using Administration > System Administration > Platform Management > Stop SBC Application.
Stopping SBC Application on Standby Server
The stop application is a service affecting operation. Click OK to continue the stop operation.
Confirming Stop Application
The application is stopped on the Standby server.
Application Stopped on Standby Server
From the EMA of initial active server (WFDSBC01a), click Administration > System Administration > Software Install/Upgrade tab.
Select the SBC Package Name to upgrade, and click Standalone Software Upgrade.
Since, you are performing an non-LSWU upgrade, and both the Active and Standby SBCs are down, it is considered as Standalone Upgrade even for a 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 on Upgrade Log section.
Copying Package to Staging and Extract package contents
Performing pre-install checks
Performing Sonus DB install
You may lose connectivity to browser session as the server goes for reboot.
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.
Log on to the 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.Completing SBC Upgrade
Verify the SBC application status on the Administration > System Administration > Platform Management screen.
Verifying Active SBC Status
Once all the SBC process starts running, continue upgrading the Standby SBC server.
Follow the step 13 through step 19 to perform upgrade on the Standby server (WFDSBC01b).
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 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
End of Procedure
Overview
Content Tools