Skip to end of metadata
Go to start of metadata

In this section:

Live Software Upgrade (LSWU) allows you to upgrade the SBC Core application in an HA environment without dropping active calls or interrupting service. This upgrade approach is recommended for High Availability SBC systems.

For information on average call rates and capacities during a LSWU, refer to LSWU Performance Metrics.

Prerequisites

  1. Verify the SBC platform is running in redundant mode using the following CLI command:

    Example
    admin@WFDSBC01a> show table system serverStatus
    																		MGMT																				DAUGHTER
    										PLATFORM		APPLICATION   	REDUNDANCY						APPLICATION UP		LAST RESTART					BOARD
    NAME      HW TYPE SERIAL NUM PART NUM  VERSION			VERSION      	ROLE		UP TIME				TIME				REASON			SYNC STATUS		PRESENT
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    WFDSBC01a SBC 5200 2044090074 821-00430 V05.00.02R000 	V05.00.02R000 	active		6 Days	15:32:47	6 Days 15:31:04		systemRestart	syncCompleted	true
    WFDSBC01b SBC 5200 2052090007 821-00430 V05.00.02R000 	V05.00.02R000 	standby		6 Days	15:32:47	6 Days 15:31:04		systemRestart	syncCompleted	true
  2. Verify the sync status using the following CLI command.

    Example
    admin@WFDSBC01a> show table system syncStatus
    SYNC MODULE                  STATUS
    -------------------------------------------
    Policy Data                 syncCompleted
    Disk Mirroring              syncCompleted
    Configuration Data          syncCompleted
    Call/Registration Data      syncCompleted
  3. Verify that at least one management port is in admnEnabledPortUp state on each server using the following CLI command:

    Example
    admin@WFDSBC01a> show table system ethernetPort mgmtPortStatus
    CE   		PORT IF 											RX		TX		RX		TX		RX		TX
    NAME 		NAME INDEX 	MAC ADDRESS 		LINK STATE			PACKETS	PACKETS	ERRORS	ERRORS	DROPPED	DROPPED
    ---------------------------------------------------------------------------------------------------------------------------
    WFDSBC01a 	mgt0 1 		0:10:6b:2e:e6:9e 	admnEnabledPortUp	1728556	132270	0		0		0		0
    WFDSBC01a 	mgt1 2 		0:10:6b:2e:e6:9f 	admnEnabledPortUp	6754292	6480	0		0		0		0
    WFDSBC01b 	mgt0 3 		0:10:6b:2e:e5:ea 	admnEnabledPortUp	3457239	0		0		0		0		0
    WFDSBC01b 	mgt1 4 		0:10:6b:2e:e5:eb 	admnEnabledPortUp	1038353	0		0		0		0		0
  4. Verify the system call arrival rate (systemCongestionCallArrivalRate) using the following CLI command. The maximum call rate allowed for LSWU differs between various SBC platforms. For more information, refer to LSWU Performance Metrics page.

    Example
    admin@WFDSBC01a> show status system systemCongestionStatus
    systemCongestionStatus entry {
    	systemCongestionMCLevel				0;
    	systemCongestionCPULevel			0;
    	systemCongestionMemLevel			0;
    	systemCongestionCallRateLevel		0;
    	systemCongestionMCDuration			67397;
    	systemCongestionCallArrivalRate		355;
    	systemCongestionCallAcceptRate		100;
    	systemCongestionCallAcceptCount		0;
    	systemCongestionCallEqArrivalRate 	355;
    	systemCongestionRegArrivalRate		0;
    	systemCongestionIRTTLevel			0;
    }
    [ok][2013-09-04 11:48:48]
  5. Set the log filter levels (in configuration mode) to major using the following CLI command.

    Example
    admin@WFDSBC01a% set oam eventLog typeAdmin debug filterLevel major
    admin@WFDSBC01a% set oam eventLog typeAdmin system filterLevel major
    admin@WFDSBC01a% commit
  6. Verify if the system and the databases are in sync with each other.

    Prior to performing a Live Software Upgrade (LSWU), verify if the system and the databases are in sync. The steps to accomplish this are included in WBA Warning-14-00020748.

    To view WBA, login to Salesforce Customer Portal, select the Solutions tab and search for 00020748.

  7. Before upgrading the SBC application in SBC Software Edition (SBC SWe), verify the Misc.TimerMaxHardPeriod and Misc.TimerMinHardPeriod parameters of ESXi are set as per recommendations in the table of "ESXi Advanced Settings" found on the page For VMware.

Transfer the Package to Target Servers

  1. Download the following files included in SBC application bundle from the Salesforce customer portal to your local PC or server. To know more on how to download, refer to Downloading the Software from Salesforce.
    1. sbc-V05.xx.xx-R000.x86_64.tar.gz(SBC application installation image)
    2. sbc-V05.xx.xx-R000.x86_64.md5 (md5 associated with the SBC application installation image)
    3. sbc-V05.xx.xx-R000.x86_64.signature
         To determine the exact version, refer to SBC Release Information.

  2. Validate the integrity of SBC tar file with the md5 file. See Validating MD5Sum with 'Checksums Calculator' for guidance.
  3. Launch EMA.
  4. Navigate to Administration > System Administration > File Upload to upload the SBC application package to the active and standby SBC servers.
    1. Click File Upload tab.
    2. Click Add Files to Queue.
    3. Browse the SBC application package files in the File Upload screen and click Open.
      The files are listed in Upload Queue section.
    4. Click Upload Files. The file upload starts.
    5. Repeat step a through d for standby SBC server.

Perform Live Software Upgrade of Application

This procedure prepares the server for revert, upgrades OS (if required) and upgrades the SBC application. During this process, server may reboot up to two times.

  1. Log on to the CLI on the active server.
  2. At the CLI prompt of active server, start the LSWU using the following CLI command:

    Example
    admin@WFDSBC01a> request system serverAdmin WFDSBC01b startSoftwareUpgrade package sbc-V05.01.00-R000.x86_64.tar.gz
    This command will start live software upgrade. Do you want to proceed (yes/no): <yes>
    Proceeding
    result success
    reason Success from: WFDSBC01b
    

     

    The package name must not contain the package path.
  3. Once the upgrade starts, monitor the status using the following CLI command.

    Example
    admin@WFDSBC01a> show table system serverSoftwareUpgradeStatus
    NAME             UPGRADE 
    				 STATUS
    ----------------------------
    WFDSBC01a        pendingUpgrade
    WFDSBC01b        upgrading
    

    At the beginning of the upgrade, server is rebooted and disk partitioning is done automatically that takes approximately 15 to 20 minutes. Do not hit the power button or restart the server during this time. Open the JViewer console to watch the progress of upgrade.

  4. Verify the sync status is in syncCompleted state, using the following CLI command.

    Example
    admin@WFDSBC01a> show table system syncStatus
    SYNC MODULE                  STATUS
    -------------------------------------------
    Policy Data                 syncCompleted
    Disk Mirroring              syncCompleted
    Configuration Data          syncCompleted
    Call/Registration Data      syncCompleted

    During an LSWU process, when the Standby SBC is in "Sync" state (which usually takes about 2 - 3 minutes), the new call data is queued on the Active SBC. Those calls are not marked as stable. Once the "Sync" is complete, the pending call data queue is moved from Active SBC to Standby SBC. Those calls are marked as stable. Therefore, check the callCountStatus when both Active and Standby SBCs complete the "Sync" state.

  5. Verify the software upgrade status is in Upgraded state, using the following CLI command.

    Example
    admin@WFDSBC01a> show table system serverSoftwareUpgradeStatus
    NAME             UPGRADE 
    				 STATUS
    --------------------------------
    WFDSBC01a        pendingUpgrade
    WFDSBC01b        upgraded
    

    This process takes approximately 45 minutes to complete on a single server.

  6. Verify the system server status using the following CLI command.

    Example
    admin@WFDSBC01a> show table system serverStatus
    																		MGMT																				
    										PLATFORM		APPLICATION   	REDUNDANCY						APPLICATION UP		LAST RESTART					
    NAME      HW TYPE SERIAL NUM PART NUM  VERSION			VERSION      	ROLE		UP TIME				TIME				REASON					SYNC STATUS		
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    WFDSBC01a SBC 5200 2044090074 821-00430 V05.00.02R000 	V05.00.02R000 	active		0 Days	02:44:22	0 Days 02:43:04		systemRestart			syncCompleted
    WFDSBC01b SBC 5200 2052090007 821-00430 V05.01.00R000 	V05.01.00R000 	standby		0 Days	00:13:02	0 Days 00:07:23		softwareUpgradeOrRevert	syncCompleted
  7. Once the WFDSBC01b state changes to upgraded, proceed with upgrading the next server.
  8. Upgrade the next server using the following CLI command.

    Example
    admin@WFDSBC01a> request system serverAdmin WFDSBC01a startSoftwareUpgrade package sbc-V05.01.00-R000.x86_64.tar.gz
    This command will start live software upgrade. Do you want to proceed (yes/no): <yes>
    Proceeding
    result success
    reason Success from: WFDSBC01a
    [ok][2015-01-20 05:37:04]
    

     

  9. This causes an automatic switch-over whereby the active role is assigned to the original standby server (WFDSBC01b) which is already upgraded.
  10. Once the upgrade starts, monitor the status using the following CLI command on the new active server.

    Example
    admin@WFDSBC01b> show table system serverSoftwareUpgradeStatus
    NAME             UPGRADE 
    				 STATUS
    ----------------------------
    WFDSBC01a        upgrading
    WFDSBC01b        upgraded
    

     

    At the beginning of the upgrade, server is rebooted and disk partitioning is done automatically that takes approximately 15 to 20 minutes. Do not hit the power button or restart the server during this time. Open the JViewer console to watch the progress of upgrade.


  11. Verify whether both the servers are upgraded using the following CLI command. 

    Example
    admin@WFDSBC01b> show table system serverSoftwareUpgradeStatus
    NAME             UPGRADE 
    				 STATUS
    ----------------------------
    WFDSBC01a        upgraded
    WFDSBC01b        upgraded
    
  12. After both the servers get upgraded and is in sync with its peer, an automatic switchover may happen.

    On all the SBC platforms other than the SBC 7000, an automatic switchover happens at the end of upgrade from pre-5.0 releases.

  13. Verify the Live Software Upgrade status is in UpgradeDone state and both primary and secondary upgrade status reflect upgraded state. Use the following CLI command.

    Example
    admin@WFDSBC01a> show table system softwareUpgradeStatus
    state					upgradeDone;
    previousState			upgrading;
    upgradeStartTime		"Fri Aug 3 11:44:40 2016";
    revertStartTime			n/a;
    package					/opt/sonus/external/sbc-V05.01.00-R000.x86_64.tar.gz;
    rpmName					/opt/sonus/staging/sbc-V05.01.00-R000.x86_64.rpm;
    upgradeScript			/opt/sonus/staging/sbxUpgrade.pl;
    revertScript			/opt/sonus/sbxRevert.pl;
    reason					successfulCompletion;
    oldRelease				V05.00.02R000;
    newRelease				V05.01.00R000;
    primaryUpgradeStatus	upgraded;
    secondaryUpgradeStatus	upgraded;
  14. Verify the SBC server status using the following CLI command.

    Example
    admin@WFDSBC01a> show table system serverStatus
    																		MGMT																				
    										PLATFORM		APPLICATION   	REDUNDANCY						APPLICATION UP		LAST RESTART					
    NAME      HW TYPE SERIAL NUM PART NUM  VERSION			VERSION      	ROLE		UP TIME				TIME				REASON					SYNC STATUS		
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    WFDSBC01a SBC 5200 2044090074 821-00430 V05.01.00R000 	V05.01.00R000 	active		0 Days	15:32:47	0 Days 15:31:04		softwareUpgradeOrRevert	syncCompleted
    WFDSBC01b SBC 5200 2052090007 821-00430 V05.01.00R000 	V05.01.00R000 	standby		0 Days	15:32:47	0 Days 15:31:04		softwareUpgradeOrRevert	syncCompleted

 

The LSWU procedure takes approximately 1.5 hours to complete on both the servers.

Upgrade logs can be found at /opt/sonus/staging/upgrade.out

Once the upgrade is successful, clear the browser cache.

  • No labels