Page History

Add_workflow_for_techpubs

AUTH1 pmohanUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca67042e, userName='null'} REV5 gnimmagaddaUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5007d7, userName='null'} REV6 avalenteUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca64041c, userName='null'} REV3 paramachandraUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef40cd9, userName='null'} REV1 dajeruUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb870607, userName='null'} REV2 kcongerUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c820009a, userName='null'}

This section describes upgrading the

Spacevars
0 product

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.

Info
icon false title Note
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. 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.

Info
icon false title Note
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 flag tgMtrgBwPerReq. Refer to SIP Trunk Group - TG MTRG Req Max BW - CLI for tgMtrgReqMaxBw configuration details. Ensure the value of the flag, tgMtrgReqMaxCalls, is twice the value of flag tgMtrgCallsPerReq. Refer to SIP Trunk Group - TG MTRG Req Max Calls - CLI for tgMtrgReqMaxCalls configuration details.

...

1. 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 Salesforcethe Ribbon Support Portal.
2. Validate the SBC md5 checksum using the checksum calculator. See Validating MD5Sum 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.

   Caption
   0 Figure 1 System and Software Info Screen for Active Server

   
   

   Caption
   0 Figure 1 System and Software Info Screen for Standby Server

   
   

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

   1. Click File Upload tab.

      Caption
      0 Figure 1 File Upload Screen

      
      

   2. Click Add Files to Queue.

   3. 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.02.00R000-connexip-os_05.00.00-R000.qcow2".

      
      

      Caption
      0 Figure 1 Selecting SBC application package

        

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

      Caption
      0 Figure 1 Uploading SBC package

       
       

      Caption
      0 Figure 1 Files on SBC

       

   5. Repeat steps "a" through "e" for Standby SBC server.
      

6. 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

   
   

7. The stop application is a service affecting operation. Click OK to continue the stop operation.

   Caption
   0 Figure 1 Confirming Stop SBC Application

   
   

8. The application is stopped on the active server.

   Caption
   0 Figure 1 Application Stopped on Active Server

   
   

9. Launch the EMA Platform Mode on the Standby server.

   Info
   icon false title Note
   Once the Active server (WFDSBC01a) is stopped, the Standby server (WFDSBC01b) automatically becomes active.

   
   

10. 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

    
    

11. The stop application is a service affecting operation. Click OK to continue the stop operation.

    Caption
    0 Figure 1 Confirming Stop Application

    
    

12. The application is stopped on the Standby server.

    Caption
    0 Figure 1 Application Stopped on Standby Server

    
    

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

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

    Info
    icon false title 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

    
    

15. 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

    
    

    Info
    icon false title Note
    You may lose connectivity to browser session as the server goes for reboot.

    
    

    Info
    icon false 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.

    
    

16. 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

    
    

17. 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

    
    

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

    Caption
    0 Figure 1 Verifying Active SBC Status

    
    

    Info
    icon false title Note
    Once all the SBC process starts running, continue upgrading the Standby SBC server.

    
    

    Note
    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

    
    

19. Follow the step 13 through step 18 to perform upgrade on the Standby server (WFDSBC01b).
    
    

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

    Caption
    0 Figure 1 Verifying Standby SBC Status

    
    

21. 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

    
    

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

    Caption
    0 Figure 1 System Sync Status

    
    

    Info
    End of Procedure