...
Note |
---|
Prior to performing an application upgrade to 6.12.0 release, upgrade the SBC Firmware to the latest version on both Active and Standby SBCs for HA pair. |
Note |
---|
Ensure that the following requirements are met prior to performing an upgrade or LSWU to 06.0102.00R001 00R000 release: |
...
The following procedure describes the
application upgrade from version 6.
01.
0R0 0R1 to 6.
12.
0R1 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.
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 active and standby SBC servers.
Click File Upload tab.
Caption |
---|
0 | Figure |
---|
1 | File Upload Screen |
---|
|
|
Click Add Files to Queue.
Browse the SBC application package files in the File Upload screen and click Open.
Note |
---|
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.0102.00R00100R000-connexip-os_03.0304.00-R001R000.qcow2 ". |
Caption |
---|
0 | Figure |
---|
1 | Selecting SBC application package |
---|
|
|
The files are listed in Upload Queue section. Click Upload All Files. The file upload starts.
Caption |
---|
0 | Figure |
---|
1 | Uploading SBC package |
---|
|
|
Caption |
---|
|
|
- Repeat steps "a" through "e" for Standby SBC server.
Stop the application on Active server using Administration > System Administration > Platform Management > Stop SBC Application.
Caption |
---|
0 | Figure |
---|
1 | Stopping SBC Application in Active Server |
---|
|
|
The stop application is a service affecting operation. Click OK to continue the stop operation.
Caption |
---|
0 | Figure |
---|
1 | Confirming Stop SBC Application |
---|
|
|
The application is stopped on the active server.
Caption |
---|
0 | Figure |
---|
1 | Application Stopped on Active Server |
---|
|
|
Launch the Platform Manager on the Standby server.
Note |
---|
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.
Caption |
---|
0 | Figure |
---|
1 | Stopping SBC Application on Standby Server |
---|
|
|
The stop application is a service affecting operation. Click OK to continue the stop operation.
Caption |
---|
0 | Figure |
---|
1 | Confirming Stop Application |
---|
|
|
The application is stopped on the Standby server.
Caption |
---|
0 | Figure |
---|
1 | 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.
Note |
---|
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. |
Caption |
---|
0 | Figure |
---|
1 | Selecting SBC Package |
---|
|
|
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 upgrade process starts on the Active server (WFDSBC01a) and displays the upgrade status on Upgrade Log section.
Caption |
---|
0 | Figure |
---|
1 | Copying Package to Staging and Extract package contents |
---|
|
|
Caption |
---|
0 | Figure |
---|
1 | Performing pre-install checks |
---|
|
|
Caption |
---|
0 | Figure |
---|
1 | Performing Sonus DB install |
---|
|
|
Note |
---|
You may lose connectivity to browser session as the server goes for reboot. |
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 the 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.
Caption |
---|
0 | Figure |
---|
1 | Completing SBC Upgrade |
---|
|
|
Verify the SBC application status on the Administration > System Administration > Platform Management screen.
Caption |
---|
0 | Figure |
---|
1 | Verifying Active SBC Status |
---|
|
|
Note |
---|
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.
Caption |
---|
0 | Figure |
---|
1 | Verifying Standby SBC Status |
---|
|
|
Verify the Firmware, ConnexIP OS and SBC application 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 |
---|
|
|