In this section:

Overview

Use this procedure to perform a standalone SBC SWe upgrade on VMware ESXi using the OVA package. 

Scope

This procedure only applies to upgrading a Standalone SBC SWe when it is installed with an OVA package on the VMware ESXi.

Prerequisites

Verify the following prior to starting the upgrade:

  1. SSH access to VMware ESXi for root user is enabled.
  2. The new OVA package is available for use in upgrading the SBC SWe.

SBC SWe Upgrade

Use the following steps to perform a standalone SBC SWe upgrade on VMware ESXi using an OVA package.

Options
  • You may use the hostname.domain_name, if configured, instead of the IP address during the upgrade.
  • You may use other file transfer tools instead of 'scp' to upload the package to the VMware ESXi datastore (For example, WinSCP on Windows).

Start

  1. Download the OVA Package

    1. Download the new OVA package and upload it to the VMware ESXi host.
      For example, if sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova is the new OVA package for the SBC SWe upgrade and 172.19.201.11 is the IP address of the VMware ESXi server, use scp to upload the package to the VMware ESXi server:

      scp sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova root@172.19.201.11:/vmfs/volumes/datastore1/ 

       

  2. Save the SBC SWe configuration

    1. Login to the VMware ESXi host via a web browser

    2. Login to the SBC SWe VM Console as ‘linuxadmin’ user and change to ‘root’ user using ‘sudo su –‘.

    3. Save the instance-specific configuration of the VM:

      /opt/sonus/sbx/scripts/saveConfig_fe.sh
      Note

      This script backs up the configuration and relevant files, and then saves the backup on the DRBD disk under the /home/sftproot/evlog/backup directory.

      Ribbon recommends to also copy the backup directory (/home/sftproot/evlog/backup) to an external location outside of the VM using 'scp' for any disaster recovery measures, if needed.

  3. Shut down the VM

    1. Shut down SBC SWe VM from the VMware ESXi console by selecting the VM and clicking on Shut down.

  4. Upgrade the SBC SWe to the new version

    1. Login into the VMware ESXi server using SSH as the ‘root’ user and extract the VMDK image from the OVA package using the 'tar' command.
      For example, if 172.19.201.11 is the IP address for the VMware ESXi server and the OVA package is 'sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova' , then SSH to the VMware ESXi server as the 'root' user and run:

      ssh root@172.19.201.11
cd /vmfs/volumes/datastore1/
tar xvf sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.vmdk

    2. Take a backup of the previous SBC SWe root disk.
      (In this example, the SBC SWe VM name is ‘SBC1’. Replace it with your VM name, if different)

      Example:
      cd /vmfs/volumes/datastore1/SBC1  
mv SBC1.vmdk SBC1.vmdk_backup
mv SBC1-flat.vmdk SBC1-flat.vmdk_backup

    3. Make a compatible root disk from the new VMDK image using ‘vmkfstools’.
      (In this example, the SBC SWe VM name is ‘SBC1’. Replace it with your VM name, if different)

      Example:
      cd /vmfs/volumes/datastore1/SBC1
vmkfstools -i /vmfs/volumes/datastore1/sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.vmdk SBC1.vmdk -d thin
      Note

      The above command takes a minute or so to clone the disk. Wait for the control to return before proceeding.

    4. Expand the new root disk to a size greater than 35 GB, where <Size_in_GB> is the new size of the disk, in GB.

      vmkfstools -X <Size_in_GB>G SBC1.vmdk
      Example: New size is 65 GB
      vmkfstools -X 65G SBC1.vmdk
      Note

      Match the new root disk size with the existing one.

  5. Power on the SBC SWe VM from the VMware ESXi console

    1. Select the VM and click Power on.

  6. Validate the SBC SWe upgrade
    During the SBC SWe bootup after a power on, the SBC application comes up with the upgraded version and the configuration saved as part of step 2c above is automatically restored.

    1. Login to the VMware ESXi host via a web browser
    2. Login to the SBC SWe VM Console as ‘linuxadmin’ and change to ‘root’ user using ‘sudo su –‘.

    3. Run the swinfo command to check the SBC SWe version.

SBC SWe Rollback

Use the following procedure to perform a standalone SBC SWe rollback on the VMware ESXi using an OVA package.

Start

  1. Shut down the VM

    1. Shut down SBC SWe VM from VMware ESXi console by selecting the VM and clicking Shut down.

  2. Roll back the SBC SWe to the previous version

    1. Login into the VMware ESXi server using SSH and ‘root’ user and restore the disk to the backed up SBC SWe root disk.
      For example, if 172.19.201.11 is the IP address for VMware ESXi server and the SBC SWe VM name is ‘SBC1’, then SSH to VMware ESXi server using 'root' user and restore the disk from the backed up SBC SWe root disk.
      (In this example, the SBC SWe VM name is ‘SBC1’. Replace it with your VM name, if different)

      Example:
      ssh root@172.19.201.11
cd /vmfs/volumes/datastore1/SBC1  
mv -f SBC1.vmdk_backup SBC1.vmdk
mv -f SBC1-flat.vmdk_backup SBC1-flat.vmdk

  3. Power on the VM

    1. Power on the SBC SWe VM from the VMware ESXi console by selecting the VM and clicking Power on.

  4. Validate the SBC SWe rollback

    1. Once the SBC SWe boots up after a power-on, the SBC SWe application comes up on the previous version.

      1. Login to the VMware ESXi host via a web browser.

      2. Login to the SBC SWe VM Console as ‘linuxadmin’ and change to ‘root’ user using ‘sudo su –‘.

      3. Run the swinfo command to check the SBC SWe version.