You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

In this section:

Overview

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

Scope

This procedure only applies to upgrading a HA 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 HA 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 new OVA package and upload it to 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. Check the sync status

    1. Login to Confd CLI on the active SBC SWe using ‘admin’ user and check the sync status:

      ssh admin@<active_SBC_mgmt_ip>
admin@vsbc1> show table system syncStatus
      Note

      Verify that all sync statuses are marked as 'syncCompleted' before proceeding.

  3. Shut down the Standby SBC VM

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

  4. Upgrade the Standby SBC SWe to new version

    1. From the Standby SBC SWe, login to the VMware ESXi server using SSH and ‘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 '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 Standby SBC SWe root disk.
      (In this example, the SBC SWe VM name is ‘SBC2’. Replace it with your VM name, if different)

      cd /vmfs/volumes/datastore1/SBC2
mv SBC2.vmdk SBC2.vmdk_backup
mv SBC2-flat.vmdk SBC2-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 ‘SBC2’. Replace it with your VM name, if different)

      cd /vmfs/volumes/datastore1/SBC2
vmkfstools -i /vmfs/volumes/datastore1/sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.vmdk SBC2.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 SBC2.vmdk
      Example: New size is 65 GB
      vmkfstools -X 65G SBC2.vmdk
      Note

      Match the new root disk size with the existing one.

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

    1. Select the the VM and click Power on.

  6. Validate the Standby SBC SWe Upgrade

    1. During the Standby SBC SWe boot up after power on, the SBC application shows the upgraded version and the configuration is automatically restored from the Active SBC SWe.

      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. Check the SBC SWe version:

        swinfo

  7. Check the Sync status

    1. Login to Confd CLI on the Active SBC SWe using ‘admin’ user and check the sync status:

      ssh admin@<active_SBC_mgmt_ip>
admin@vsbc1> show table system syncStatus
      Note

      Verify that all sync statuses are marked as 'syncCompleted' before proceeding.

  8. Shut down the Active SBC VM

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

  9. Upgrade the Active SBC SWe to a new version

    1. Login into VMware ESXi server using SSH and ‘root’ user where the Active SBC SWe is present and extract the VMDK image from the OVA package using the 'tar' command (if not already extracted):
      For example, if 172.19.201.11 is the IP for VMware ESXi server and the OVA package is 'sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova', then SSH to VMware ESXi server using 'root' user.

      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 root disk for the Active SBC SWe.
      (In this example, the SBC SWe VM name is ‘SBC2’. Replace it with the name of your VM name, if different)

      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 ‘SBC2’. Replace it with the name of your VM name, if different)

      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 SBC2.vmdk
      Note

      Match the new root disk size with the existing one.

  10. Power on the Active SBC VM from the VMware ESXi console

    1. Select the VM and click Power on.
  11. Validate the Active SBC SWe upgrade

    1. During the SBC SWe bootup after a power on, the SBC application comes up with the upgraded version and the configuration is automatically restored from other SBC SWe (which is currently running in the Active role).

      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. Check the SBC SWe version:

        swinfo

SBC SWe Rollback

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

  1. Shut down the VM

    1. Shut down both the active and standby SBC SWe VM from the 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 for both the active and standby from the backed up SBC SWe root disk.
      For example, if 172.19.201.11 is the IP address for the VMware ESXi server and the SBC SWe VM name is ‘SBC1’, then SSH to the VMware ESXi server using 'root' user and restore the disk to 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)

      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 both the active and standby SBC SWe VM from the VMware ESXi console by selecting the VMs and clicking Power on.

  4. Validate the SBC SWe Rollback

    1. Once the SBC SWe boots up after the power-on, the SBC SWe application comes up on both the active and standby VMs 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. Check the SBC SWe version:

        swinfo
  • No labels