Page tree
Skip to end of metadata
Go to start of metadata

In this section:

Use these steps to upgrade your SBC 5xx0 system from release 2.0.8-R0 to 3.0.5-R0.

In this MOP, the nodes are designated as:

  • Initial active server = node A
  • Initial standby server = node B

Upgrade Sequence

In an HA configuration, the SBC 5xx0 upgrade sequence entails first upgrading the standby node, and then upgrading the active node as described in the sequence below.

Before starting this upgrade, ensure both SBC nodes are fully operational with no outstanding alarms.

The following steps are accomplished with this upgrade procedure:

  1. Save configuration and copy to PC or a server
  2. Copy over crontab and scripts, if applicable
  3. Obtain BMC Firmware
  4. Upgrade the BMC on node B (1.14.0 -> 2.1.7-R0)
  5. Upgrade the BIOS on node B (1.6.3 -> 2.0.0-R0)
  6. Upgrade the OS on node B (1.7.5 -> 1.8.6-R0)
  7. Switchover/Failover from node A to node B
  8. Upgrade the BMC on the node A (1.14.0 -> 2.1.7-R0)
  9. Upgrade the BIOS on node A (1.6.3 -> 2.0.0-R0)
  10. Upgrade the OS on the node A (1.7.5 -> 1.8.6-R0)
  11. Upgrade SBC 5xx0 Application Software using LSWU

Table : Approximate Upgrade Time Per Server

BMC Upgrade

10 minutes

BIOS Upgrade

45 minutes

OS Upgrade

20 minutes

Application Upgrade (LSWU)

15 minutes

Upgrading BMC, BIOS and OS

  1. Save your configuration and copy it to a PC or server.
  2. Copy over crontab and scripts, if applicable.

Perform an orderly shutdown the server from BMC GUI, and then upgrade the BMC. Since BMC is reset after the upgrade, you need to log out and log in again.

Obtain BMC Firmware Image

Download software bundle from the Sonus SalesForce Customer Portal and copy it to the local folder of your desktop, laptop or any Linux server.

  • FIRMWARE-bmc5X00_V2.1.7-R0-bios5X00_V2.0.0-R0.tar.gz
  • FIRMWARE-bmc5X00_V2.1.7-R0-bios5X00_V2.0.0-R0.tar.gz.md5

Untar the following files required to upgrade the BMC firmware:

  • bmc5X00_V2.1.7-R0.rom (BMC firmware image)
  • bmc5X00_V2.1.7-R0.rom.md5sum (md5 associated with the BMC image)
  • BMC-Release-Notes.doc

To determine the exact versions, refer to the associated SBC 5x00 3.0.5Rx Patch Release Notes.

Upgrade the BMC Firmware on Node B

Perform one of the procedures below, depending upon your current BMC firmware version:

  1. If your BMC firmware version is lower than 02.01.07, use the procedure "Upgrade BMC Firmware to Version 02.01.07" on page 2 4 to upgrade node B BMC firmware.
  2. If your BMC firmware version is 02.01.07 or greater, use the procedure ""Verify BMC Firmware 02.01.07 Version" on page 2 12".

Upgrade BMC Firmware to Version 02.01.07

  1. From a Web browser, enter the BMC IP address:

    https://<BMC_IP_address> 

    The BMC login dialog displays.

     

  2. Login to the BMC.
    1. Default username: root
    2. Default password: superuser

      Figure : SBC 5x00 BMC Login Window

  3. On the BMC main screen, click Remote Control tab. The Remote Control screen displays similar to the figure below.

    Figure : Remote Control Screen

  4. Choose Server Power Control from the navigation pane or click Power Control to open the 'Power Control and Status' screen as shown below .

    Figure : Power Control and Status Screen

  5. Select Power Off Server Orderly Shutdown option and click Perform Action, as shown in the above figure.

    This action only powers off the host side of the ConnexIP; the BMC is still up.

  6. Click the Maintenance tab in the BMC GUI to enter the Maintenance screen as depicted below.

    Figure : Maintenance Screen

  7. SSH login to BMC, and remove one of the Kernel modules which handles the I2C bus. At the Linux command prompt, execute the following command to prevent the sensor scanning code from communicating with the I2C bus:

    rmmod i2c-aspeed 
  8. Click Enter Update Mode and the Update Mode confirmation dialog box displays, as shown in the figure below.

    Figure : Update Mode Confirmation Dialog Box

  9. Click OK. The Firmware Upload screen displays as shown below.

    Figure : Firmware Upload Screen

  10. Click Choose File
  11. From the Open dialog, browse to and select the firmware image and click Open.
  12. The chosen file displays next to the Choose File button similar to below. Click Upload Firmware to upload the selected BMC image file.

    Figure : Uploading BMC Firmware Image

  13. Click OK on the image verification dialog as shown below.

    Figure : Image Verification Dialog

  14. Verify whether the Existing Version and New Version fields in Firmware Verification section are different as depicted below . If the versions are different, continue with the Start Upgrade task or click Cancel.

    Figure : Firmware Verification

    The above figure only displays the firmware version up to two decimal places. To see the complete version information, see "Upgrading SBC 5x00 Application Software using LSWU" on page 2 – 25.

  15. Click Start Upgrade. When prompted with a warning dialog, click OK to continue.

    Figure : Warning Dialog

    Once the upgrade process starts, do not close the screen.

  16. The firmware upgrade process takes a few minutes. The upgrade progress displays in the Flash Status screen.

    Figure : Flash Status Screen

  17. Once the firmware upgrade completes, a confirmation screen displays similar to below.

    Figure : Firmware Upgrade Completed

    BMC automatically reboots once the upgrade completes.

  18. Verify BMC version by launching the remote console and entering the command.

    # swinfo 

    Information similar to the following displays:

    =================================================== 
    SERVER:<node A>
    BMC:v1.14.0
    BIOS:v1.6.3
    ConnexIP OS:01.07.05
    SonusDB:sonusdb-V02.00.08-R000
    EMA:ema-V02.00.08-R000
    SBX:sbx-V02.00.08-R000
    =================================================== 
    Installed host role: active
    Current host role: active
    ===================================================
    =================================================== 
    SERVER:<node B>
    BMC:v2.1.7
    BIOS:v1.6.3
    ConnexIP OS:01.07.05
    SonusDB:sonusdb-V02.00.08-R000
    EMA:ema-V02.00.08-R000
    SBX:sbx-V02.00.08-R000
    =================================================== 
    Installed host role: standby
    Current host role: standby
    =================================================== 

    The swinfo command provides the information on the software version of BMC, BIOS, ConnexIP 5200 OS and NBS5200 application. Compare these results to the latest release notes to determine if any components require updating.

  19. Once the BMC upgrade process is complete, execute one of the following commands at the Linux command prompt to verify if the BMC is operating properly:

    ipmitool fru print

    --or--

    hwinfo
  20. Continue to "Obtain BIOS Firmware Image" on page 2 – 13 to upgrade BIOS to V02.00.00- R000 on node B.

    This will take about 45 minutes.

Verify BMC Firmware 02.01.07 Version

If you have already upgraded to SBC 5x00 3.0.x releases and your BMC firmware version is 02.01.07, perform the following steps:

  1. SSH login to SBC 5x00 and execute the following command to verify if the BMC is operating properly:

    ipmitool fru print

     

    1. If the BMC is operating properly, results display similar to below:

      FRU Device Description: Builtin FRU Device (ID 0) Chassis Type: Rack Mount Chassis
      Chassis Part Number: 821-00465
      Chassis Serial: 4150110127
      Chassis Extra: C20B
      Board Mfg: Sonus Networks Inc. Board Product: SBS100E
      Board Serial: 4150110127
      
      <shortened for brevity>  

      Depending on how the chassis is populated, "Device not present" entries may display.

    2. If the BMC is not operating properly, the following details display:

      FRU Device Description : Builtin FRU Device (ID 0) Device not present (Unknown (0x81))
      FRU Device Description : FRU PS_TOP (ID 2) Device not present
      (Unknown (0x81))
      FRU Device Description : FRU PS_BOT (ID 1) Device not present
      (Unknown (0x81))
      
      <shortened for brevity> 
  2. If the BMC is not operating properly, perform the following steps:
    1. Using BMC power control, perform a controlled shut-down.
    2. Remove the power supply completely from the SBC, and wait for 10 seconds.
    3. Reinsert the power supply., and power ON the SBC.
    4. Once the host processor restarts, execute the ipmitool fru print command at the Linux prompt to verify if the BMC is operating properly.

Obtain BIOS Firmware Image

Download software bundle from the Sonus SalesForce Customer Portal and copy it to the local folder of your desktop, laptop or any Linux server.

  • FIRMWARE-bmc5X00_V2.1.7-R0-bios5X00_V2.0.0-R0.tar.gz
  • FIRMWARE-bmc5X00_V2.1.7-R0-bios5X00_V2.0.0-R0.tar.gz.md5

Untar the following files required to upgrade the BIOS firmware:

  • bios5X00_V2.0.0R0.rom (BIOS firmware image)
  • bios5X00_V2.0.0R0.rom.md5sum (md5 associated with the BIOS image)
  • AfuE64.efi (BIOS update tool)
  • updateBIOS.nsh (BIOS update script)
  • BIOS-Release-Notes.doc

To determine the exact versions, refer to the associated SBC 5x00 3.0.5Rx Patch Release Notes.

Upgrade the BIOS Firmware on Node B

The following procedure describes how to upgrade the BIOS firmware on node B by launching the host remote console on the PC. To use this procedure for node A, simply replace references to "B" to "A" where appropriate.

  1. Locate the BIOS update software from a local folder of your PC and secure copy (or use other file transfer tool) to ConnexIP BIOS directory using the following command.

    % scp -P 2024 <filename> root@<node B>:/bios 

    The following filenames are required to upgrade the BIOS firmware.

    • bios5X00_V2.0.0R0.rom
    • bios5X00_V2.0.0R0.rom.md5sum
    • AfuE64.efi
    • updateBIOS.nsh
  2. Validate the md5 checksum of the BIOS firmware image using the following steps:
    1. Login to the BMC and launch the BMC remote console.

    2. Access the BIOS directory using the following command:

      # cd /bios
    3. Display the expected sum for the BIOS firmware image, contained in the bios5X00_V2.0.0R0.rom.md5sum file using the cat command. For example:

      # cat bios5X00_V2.0.0-R0.rom.md5sum

      This displays the md5 checksum,91db9add662d39bfed9b0b3d11d0cd2d, and the BIOS firmware image name, bios5X00_v2.0.0-R0.rom.

    4. Calculate the md5 checksum of the BIOS firmware image you copied to the /bios directory using the md5sum command. For example:

      # md5sum bios5X00_v2.0.0-R0.rom

      This displays the checksum value of the BIOS firmware image.

    5. Verify that the md5 checksum found in bios5X00_v2.0.0-R0.rom.md5sum file matches the md5 checksum calculated using the md5sum command in the previous step. 
    6. If the md5 checksums match, proceed to the next step. Otherwise, return to Step 1 and copy the BIOS update software to the ConnexIP BIOS directory. Then re-attempt to vaIidate the md5 checksum as described in Step 2. If the md5 checksums still do not match, please contact Sonus Technical Assistance Center for assistance.

      If the md5 checksums do not match, discontinue the upgrade. Otherwise your SBC may become inoperative and require Sonus Technical Assistance Center intervention to return it to a functional state.
  3. From the BMC GUI (https://<BMC_IP_address>) Remote Control tab, choose Server Power Control from the navigation pane or click Power Control to open the "Power Control and Status" screen as shown below.

    Figure : Power Control and Status Screen

  4. Open the BMC remote console.
    1. From Remote Control screen, click Console Redirection. The Console Redirection screen displays.
    2. From Console Redirection screen, click Java Console. The JViewer window displays. Leave this window open.

      Depending upon your web browser, a dialog similar to below may display to confirm opening the jviewer.jnlp file. Accept default settings and click OK.

      Figure : Opening JViewer.jnlp File

  5. Select Power Off Server - Orderly Shutdown radio button and click Perform Action (see Figure 13) .

    This action will only power off the host side of the ConnexIP; the BMC is still up.

  6. Return to the Power Control and Status screen, and then select Power On Server option and click Perform Action as shown below. The server begins to boot up.

    Figure : Power On Server

  7. As soon as the BIOS banner displays in JViewer window similar to the below example , press <F2> to enter into the BIOS configuration screen.

    Figure : BIOS Banner

  8. Once the BIOS configuration screen displays, use the left arrow key to navigate to the left and display Save & Exit menu as shown below. Select Built-in EFI Shell option in Boot Override menu and press <Enter>.

    Figure : BIOS Configuration screen - Save & Exit

  9. Enter fs0: in EFI shell, which mounts the hard disk to the server as shown below.

    Figure : Mounting the Hard Disk

  10.   Perform the upgrade in the shell as shown below .

    fs0:\> updateBIOS.nsh bios5X00_v2.0.0.rom 

    Figure : Upgrading BIOS from Hard Disk

    Power must remain connected to the server during the upgrade process. Also, do not reboot the server during the upgrade.

  11. Once the upgrade completes, enter reset -s to reboot the server.

    Figure : Using 'reset -s' Command

    After issuing reset –s, if the host boots back to the EFI shell instead of booting SBC OS and starting the application, return to the BIOS setup and check the disk boot priority. If necessary, change the boot priority by setting the disk (SSD) as the first choice. Then save and exit from the BIOS setup.

  12. To verify the BIOS version by launching the remote console and entering the command.

    # swinfo
  13. Upgrade ConnexIP OS to V01.08.06-R000 on node B. Reference: 550-05645 SBC 5x00 3.0.1 Software Installation and Upgrade Guide, "Upgrading the ConnexIP OS through the Remote Console".

Upgrade ConnexIP OS on Node B via the Remote Console 

This procedure performs an incremental OS upgrade preserving all existing system configurations and settings. The internal SSD drive is not re-imaged. During the upgrade, you will download the ConnexIP OS upgrade package from the SalesForce web portal to your local computer or server, and then upload the file to the SBC 5x00 host and perform the upgrade using the OpenJDK Remote Console.

Download ConnexIP OS bundle from the Sonus SalesForce Customer Portal and copy it to the local folder of your desktop, laptop or any Linux server.

  • CONNEX_OS-01.08.06-R000.tar.gz
  • CONNEX_OS-01.08.06-R000.tar.gz.md5

Untar the following files required to upgrade the ConnexIP OS:

  • connexip-os_01.08.06-R000.amd64.deb (ConnexIP OS upgrade package)
  • connexip-os_01.08.06-R000.amd64.md5 (md5 associated with ConnexIP OS upgrade package)

To determine the exact versions, refer to the associated SBC 5x00 3.0.5Rx Patch Release Notes.

The following procedure describes how to upgrade the ConnexIP OS using ConnexIP OS upgrade package on node B: To use this procedure for node A, simply replace references to "B" to "A" where appropriate.

  1. Download the latest version of .deb and .md5 files from the SalesForce website to a local folder of your PC.
  2. Secure copy the files from your local PC or server to SBC 5x00 (or use a file transfer utility such as FileZilla) using the following commands:

    % scp -P 2024 connexip-os_01.08.06-R000_amd64.deb root@<node B>:/opt/sonus/external
    % scp -P 2024 connexip-os_01.08.06-R000_amd64.md5 root@<node B>:/opt/sonus/external  
  3. Launch the remote console.
  4. Stop the application on the standby server using the following command:

    # service sbx stop  
  5. To verify the application is stopped, use the command:

    # service sbx status 
  6. Verify if sonusdb-V03.00.05-R000.x86_64.md5 and sonusdb-V03.00.05-R000.x86_64.rpm are under /opt/sonus directory:

    # cd /opt/sonus
    # ls 
    Example:
    [root@<node B> linuxadmin]# cd /opt/sonus
    [root@<node B> sonus]# ls
    appInstall-V02.00.08-R000.sh    sbc-V03.00.05-R000.x86_64.rpm 
    bin                             sbx
    checkDiskUsage.sh               sbx.conf 
    cnxipm                          sbx.conf.orig 
    cps                             sbxInstall.sh 
    diags                           sbx.prev
    ema                             sbxRevert.pl 
    ema-V03.00.05-R000.x86_64.rpm   sbxUpdate.sh 
    etc                             sbxUpgrade.pl
    external                        sbxUpgradeRevertUtils.pl 
    lib                             securelink
    liblswuPreConfigure.so          sonusdb-V02.00.08-R000.x86_64.md5 
    lswuMatrixSBX5000.bin           sonusdb-V02.00.08-R000.x86_64.rpm 
    lswuMatrixSBX5000.txt           sonusUtils.sh
    lswuSBX5000.txt                 staging 
    openclovisVar.prev              tailf.prev 
    preInstallCheck.sh              usr 
    ReleaseInfo 
    [root@<node B> sonus]#  
  7. Once the application is stopped, upgrade the OS on the standby server using the following command:

    # dpkg –x /opt/sonus/external/connexip-os_01.08.06-R000_amd64.deb /
    # cd /tmp/connex-install
    # sh /tmp/connexip–install/postInstall.sh 

    When prompted to reboot the system, type y.

     

  8. After the server has rebooted, verify the installed OS version using one of the following commands:

    # cat /etc/connexip_os_version

    --or--

    # swinfo -l
    =================================================== 
    SERVER:         Bison2
    BMC:            v2.1.7
    BIOS:           v2.0.0
    ConnexIP OS:    01.08.06-R000
    SonusDB:        sonusdb-V02.00.08-R000
    EMA:            ema-V02.00.08-R000
    SBX:            sbx-V02.00.08-R000
    =================================================== 
    Installed host role:    standby
    Current host role:      standby
    =================================================== 



  9. Wait for the system to fully synchronize. To verify system synchronization status, use the following CLI command:

     > show table system syncStatus

    Verify all status is "syncCompleted":

    > admin@<node B>> show table system syncStatus
    SYNC MODULE              STATUS
    -------------------------------------- 
    Policy Data              syncCompleted 
    Disk Mirroring           syncCompleted 
    Configuration Data       syncCompleted 
    Call/Registration Data   syncCompleted
  10. This completes Stage 1 of the BMC, BIOS and OS upgrade on node B.

    [root@<node B> ~]# swinfo
    =================================================== 
    SERVER:<node B>
    BMC:            v2.1.7
    BIOS:           v2.0.0
    ConnexIP OS:    01.08.06-R000
    SonusDB:        sonusdb-V02.00.08-R000
    EMA:            ema-V02.00.08-R000
    SBX:            sbx-V02.00.08-R000
    =================================================== 
    Installed host role:   standby
    Currenthost role:      standby 
    =================================================== 

    In the following steps, perform a switchover from A to B in preparation of upgrading node A.

  11. Verify that node B is up and in sync with node A. Perform a switchover from A to B with CLI command. Now A becomes standby, and B changes to active.

    > show table system syncStatus
    > request system admin <sys_name> switchover  
  12. If the upgrade is performed using remote access over SecureLink, the SecureLink configuration is not carried forward. After the OS upgrade completes, login to the Platform Manager and reconfigure SecureLink before continuing this MOP.

    See WBA Bulletin-13-19072 "Securelink configuration after OS upgrade" for details.

Upgrade BMC, BIOS and ConnexIP OS on Node A

Accomplish the following steps to upgrade the BMC and BIOS firmware, and the OS software on node A.

  1. Upgrade BMC on node A to V02.01.07-R000 using the procedure "Upgrade the BMC Firmware on Node B", and replacing reference to "node B" to "node A", as appropriate.
  2. Upgrade BIOS on node A to V02.00.00-R000 using the procedure "Upgrade the BIOS Firmware on Node B" , and replacing reference to "node B" to "node A", as appropriate.
  3. Upgrade ConnexIP OS on node A to V01.08.06-R000 using the procedure "Upgrade ConnexIP OS on Node B via the Remote Console", and replacing reference to "node B" to "node A", as appropriate.
  4.    At this point, the upgrades of BMC, BIOS and OS are complete on both nodes.

    [root@<node A> ~]# swinfo
    =================================================== 
    SERVER:<node A>
    BMC:               v2.1.7
    BIOS:              v2.0.0
    ConnexIP OS:       01.08.06-R000
    SonusDB:           sonusdb-V02.00.08-R000
    EMA:               ema-V02.00.08-R000
    SBX:               sbx-V02.00.08-R000
    =================================================== 
    Installed host role:    active
    Currenthost role:       standby
    ===================================================
  5. If the upgrade is performed using remote access over SecureLink, the SecureLink configuration is not carried forward. After the OS upgrade completes, login to the Platform Manager and reconfigure SecureLink before continuing this MOP.

    See WBA Bulletin-13-19072 "Securelink configuration after OS upgrade" for details.

Upgrading SBC 5x00 Application Software using LSWU

A Live Software Upgrade (LSWU) allows you to upgrade the SBC 5x00 application software without dropping active calls. This approach does not interrupt service when upgrading or patching on an HA-enabled environment, and reduces the maintenance window associated with the upgrade activity. This approach is recommended for redundant or High Availability SBC 5x00 systems.

LSWU will be performed on node A first since it is the current standby server.

Before continuing, please refer to WBA Warning-00019559 "During SBC UPGRADE/LSWU a Daughter Board Status query via CLI/EMA/EMS/third Party SNMP tool could result in UPGRADE failure.

Prerequisites

  1. Accomplish "Upgrading BMC, BIOS and OS" procedures in this chapter before starting the application upgrade.
  2. Save the existing configuration.
    1. Login to the SBC 5000 Series CLI of active server (node B). Execute the following command to save the SBC 5000 Series configuration.

      > request system admin <node B> saveConfig
      This command will save the current configuration. Do you want to continue (yes/no) yes
      Proceeding 
      result success
      reason Configuration Saved as /var/log/sonus/sbx/config/config_<sys_name>_20110824_021127.tar.gz 

      (This command saves the current configuration to a time-stamped zipped tar file located in /var/log/sonus/sbx/config directory of SBC 5000 series active server.

    2. Login to any server and copy the configuration file from target system to any temporary directory on the server. Execute the following command from the server:

      % sftp -oPort=2024 sftpadmin@<node B>:/var/log/sonus/sbx/ config/config_<node B>_20110824_021127.tar.gz /home/ bob/SBC 5000 Series/config
      
      sftpadmin@<node B>'s password: <sftpadmin>
      
      Fetching /var/log/sonus/sbx/config/ config_Hackos_Irving_20130117_050320.tar.gz to config_Hackos_Irving_20130117_050320.tar.gz 
  3. Put the CLI in exclusive mode to stop other users from making changes during LSWU:

    > configure exclusive 
  4. Check that the SBC 5x00 system is running in redundant mode. Verify the system server and sync status by using the following CLI commands:

    > show table system serverStatus
    > show table system syncStatus 


    Example 1:

    > admin@<node B>> show table system serverStatus
                                                                             MGMT
                                               PLATFORM       APPLICATION    REDUNDANCY
    NAME      HW TYPE   SERIAL NUM  PART NUM   VERSION        VERSION        ROLE
    -----------------------------------------------------------------------------------------
    <node A>  SBC 5x00  2044090074  821-00430  V08.00.00A110  V02.00.08R000  active
    <node B>  SBC 5x00  2052090007  821-00430  V08.00.00A110  V02.00.08R000  standby 


    Example 2:

    > admin@<node B>> show table system syncStatus
    SYNC MODULE             STATUS
    ------------------------------------- 
    Policy Data             syncCompleted 
    Disk Mirroring          syncCompleted 
    Configuration Data      syncCompleted 
    Call/Registration Data  syncCompleted 
  5. Verify that at least one management port is active on each server using the following CLI command:

    > show table system ethernetPort mgmtPortStatus 


    Example:

    > admin@<node B>> show table system ethernetPort mgmtPortStatus
    CE PORT IF
    NAME NAME INDEXMAC ADDRESS LINK STATE
    -------------------------------------------------------------
    SBC01a mgt0 1 0:10:6b:2e:e6:9e admnEnabledPortUp
    SBC01a mgt1 2 0:10:6b:2e:e6:9f admnEnabledPortUp
    SBC01b mgt0 3 0:10:6b:2e:e5:ea admnEnabledPortUp
    SBC01b mgt1 4 0:10:6b:2e:e5:eb admnEnabledPortUp
  6. From Linux prompt, check if cron jobs are running in the background. These activities must be halted before initiating LSWU.

    # crontab -l 

Transfer Package to Target Servers

  1. Download the following SBC application bundle from the SalesForce Customer Portalto your local PC or server.
    1. APP_SBC-V03.00.05R000.tar.gz
    2. APP_SBC-V03.00.05R000.tar.gz.md5
  2. Transfer the files to the ConnexIP host at: /opt/sonus/external

    % scp -P 2024 APP_SBC-V03.00.05-R000.tar.gz root@<node A>:/opt/sonus/external 
    % scp -P 2024 APP_SBC-V03.00.05-R000.tar.gz.md5 root@<node A>:/opt/sonus/external 
    This must be done on both the active and standby server.
  3. Execute the following untar command to untar the files listed below which are required to upgrade the SBC 5x00 application.

    tar –zxvf sbc-V03.00.05-R000.x86_64.tar.gz 
    1. appInstall-V03.00.05-R000.sh (SBC application installation script)

    2. sbc-V03.00.05-R000.x86_64.tar.gz (SBC application installation image)

    3. sbc-V03.00.05-R000.x86_64.md5 (md5 associated with the application installation image)

    4. sonusdb-V03.00.05-R000.x86_64.rpm (DB installation image)

    5. sonusdb-V03.00.05-R000.x86_64.md5 (md5 associated with the DB installation image)
      (To determine the exact versions, refer to the associated SBC 5x00 3.0.5Rx Patch Release Notes.)

  4. Verify the tar file via a md5 using a checksum command:

    md5sum sbc-V03.00.05-R000.x86_64.tar.gz | diff - sbc- V03.01.05-Rx.x86_64.md5

    (no output displays)

     

Live Software Upgrade of Application

Since the 2.0.8R0 to 3.0.5R0 upgrade is not in the upgrade path, use "versionCheck skip" option in the CLI command for this release.

The show table/status addressContext <name> zone <name> and show table/status global callRouting CLI commands are not supported during LSWU process. Instead, use the commands:

> show status system
> show table system
> show table global call*
> show table/system oam


Accomplish the following steps to perform the Live Software Upgrade (LSWU):

  1. Login to the CLI.
  2. Verify primary and secondary software upgrade status is "committed" as shown in the example below:

    > show table system softwareUpgradeStatus
    state                  upgradeDone;
    previousState          upgrading;
    upgradeStartTime       "Wed Jan 16 22:32:50 2013";
    revertStartTime         n/a;
    package                 /opt/sonus/external/sbc-V02.00.11-R000.x86_64.tar.gz;
    rpmName                 /opt/sonus/staging/sbc-V02.00.11-R000.x86_64.rpm;
    upgradeScript           /opt/sonus/staging/sbxUpgrade.pl;
    revertScript            /opt/sonus/sbxRevert.pl;
    reason                  successfulCompletion;
    cemodeAtStart           dualCe;
    oldRelease              V02.00.10R000;
    newRelease              V02.00.11R000;
    activeCeAtStart         BATSBC01b;
    modelChange             false;
    primaryUpgradeStatus    committed;     <---------------
    secondaryUpgradeStatus  committed;     <---------------
  3. At the CLI prompt, start the LSWU process from node B (current active) to upgrade node A using the following command. Respond "yes" when prompted.

    > request system serverAdmin <node A> startSoftwareUpgrade package sbc- V03.00.05-R000.x86_64.tar.gz versionCheck skip
    This command will start live software upgrade. Do you want to proceed (yes/no) yes 

    (the package name does not contain the package path).

  4. Monitor LSWU status as follows:
    1. To monitor overall system status:

      > show table system softwareUpgradeStatus 
    2. To monitor individual server status:

      > show table system serverSoftwareUpgradeStatus 
    3. To monitor current server status:

      > show table system serverStatus 

      Upgrade logs can be found at: /opt/sonus/staging/upgrade.out on the server that is being upgraded.
      Once the secondaryUpgradeStatus state changes to 'Upgraded', proceed with node B upgrade. The following step causes an automatic switchover whereby the active role is assigned back to node A.

       

  5. Upgrade node B using the following command on CLI.

    > request system serverAdmin <node B> startSoftwareUpgrade package sbc- V03.00.05-R000.x86_64.tar.gz versionCheck skip 
  6. Logon to the CLI on node A to monitor progress.
  7. After the upgrade completes and node B is in sync with node A, an automatic switchover occurs again, and the active role is assigned back to node B.
  8. Wait for the system to fully synchronize before continuing. To verify system synchronization status, use the following command:

    > show table system syncStatus 

    Verify all status is "syncCompleted". For example:

    > admin@<node B>> show table system syncStatus
    SYNC MODULE            STATUS
    -------------------------------------
    Policy Data            syncCompleted
    Disk Mirroring         syncCompleted
    Configuration Data     syncCompleted
    Call/Registration Data syncCompleted 
  9. Login to CLI of node B and commit the software upgrade using the command.

    > request system admin <sys_name> commitSoftwareUpgrade 

    ( This makes the software upgrade persistent across server reboots.)

    Rebooting the upgraded server before issuing “commitSoftwareUpgrade” command automatically reverts the software back to the previous release.

    During the upgrade, configuration changes are not allowed.

  10. After node A is in sync with node B, perform a switchover from B to A so node A becomes active.

    > request system admin <sys_name> switchover
    [root@<node A> ~]# swinfo
    ===================================================
    SERVER: <node A>
    BMC: v2.1.7
    BIOS: v2.0.0
    OS: 01.08.06-R000
    SonusDB: sonusdb-V02.00.08-R000
    EMA: ema-V03.00.05-R000
    SBC: sbc-V03.00.05-R000
    ===================================================
    Installed host role: active
    Current host role: active
    ===================================================
    ===================================================
    SERVER: <node B>
    BMC: v2.1.7
    BIOS: v2.0.0
    OS: 01.08.06-R000
    SonusDB: sonusdb-V02.00.08-R000
    EMA: ema-V03.00.05-R000
    SBC: sbc-V03.00.05-R000
    ===================================================
    Installed host role: standby
    Current host role: standby
    ===================================================

 

The upgrade from 2.0.8-R0 to 3.0.5-R0 is complete.

Proceed to 3.1.6Rx Stage 2 - Upgrade to 3.1.6Rx to upgrade the system to 3.1.6-Rx.

 

 

  • No labels