In this section:



Overview

Using the OVA package, this procedure is used to perform an HA SBC SWe upgrade on VMware vCenter. 

Scope

This procedure only applies to upgrading an SBC SWe HA using the OVA package on VMware vCenter.

Prerequisites

The following are the prerequisites:

  1. SSH access to VMware ESXi servers (managed by vCenter) for root users should be enabled.
  2. A new OVA package for SBC SWe must be used for the upgrade.

SBC SWe Upgrade 

Using the OVA package, follow the steps to upgrade the SBC SWe HA on VMware vCenter.


Action
1

Download the OVA Package to the Hosts

Download the new OVA package and upload it to multiple VMware ESXi hosts (managed by vCenter) on which the SBC HA is installed. 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,
  • 172.19.201.11 is the IP for VMware ESXi server, and
  • 'datastore1' is the datastore name for this VMware ESXi server,

...then use scp to upload to VMware ESXi server as:
scp sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova root@172.19.201.11:/vmfs/volumes/datastore1/


Repeat the process for the other VMware ESXi host where the peer SBC is present for HA.

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).
2

Check for sync status.

  1. Log on to the Confd CLI on the active SBC SWe using the ‘admin’ user and password

  2. Check the sync status:

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

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

3

Shut down the standby SBC VM console by selecting the VM and then clicking Shut down.

4

Upgrade the Standby SBC SWe to the New Version.

  1. Log on to the VMware ESXi server using SSH and ‘root’ user where standby SBC SWe is present and extract the VMDK image from the OVA package using  the tar command.
    For example, using 172.19.201.12 as the IP for VMware ESXi server, OVA package 'sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova and datastore name 'datastore2' for this VMware ESXi server, SSH to VMware ESXi server as root user and run:

    Example:
    ssh root@172.19.201.12
cd /vmfs/volumes/datastore2/
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. Back up the root disk of the standby SBC SWe.

    Example:
    cd /vmfs/volumes/datastore2/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.

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


    The command takes time to process the disk's cloning; ensure you wait for the control to be returned before proceeding.

  4. Expand the new root disk to a size greater than 35GB using the following command:

    vmkfstools -X <Size_in_GB>G SBC2.vmdk

     Use the same disk size for the new root disk as the existing root disk.

5

Power on the standby SBC SWe VM from the VMware vCenter console by selecting the VM and clicking Power on.

6

After powering it on during the SBC SWe bootup, the SBC application comes up with the upgraded version, and the configuration is automatically restored from the active SBC SWe.

Validate the standby SBC SWe Upgrade.

  1. Login to VMware vCenter UI.
  2. Log in to 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.
7

Check for sync status.

Login to Confd CLI on active SBC SWe using the ‘admin’ user and password  and run the below command to check the sync status:

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

Ensure all sync statuses are marked as 'syncCompleted' before proceeding.

8

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

9

Upgrade the active SBC SWe to the new version.

  1. Log in to the VMware ESXi server using SSH and the ‘root’ user where active SBC SWe is present.

  2. Extract the VMDK image from the OVA package using the 'tar' command (if not already extracted):
    For example, using172.19.201.11 as the IP for VMware ESXi server, the OVA package 'sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova' and 'datastore1' as the datastore name for this VMware ESXi server, SSH to VMware ESXi server using 'root' user and run:

    Example:
    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

  3. Take a backup of the old root disk for active SBC SWe.
    For example, using an SBC SWe VM name of ‘SBC1’, then take the backup of the old SBC SWe root disk:

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

    Replace 'SBC1' with the VM name if your VM name is different.

  4. Make compatible root disk from new VMDK image using ‘vmkfstools’.
    For example, using the SBC SWe VM name ‘SBC1’, run the commands:
    (Replace 'SBC1' with the name of the VM if the VM name is 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

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

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

    vmkfstools -X <Size_in_GB>G SBC1.vmdk

For example, to expand a new root disk to size 65GB, use the following:

vmkfstools -X 65G SBC1.vmdk

NOTE: Use the same disk size for the new root disk as the existing root disk.
    vmkfstools -X 65G SBC1.vmdk

    Use the same disk size for the new root disk as the existing root disk.

10

Power on the active SBC SWe VM from the VMware vCenter console by selecting the VM and clicking Power on.

11

Validate the active SBC SWe Upgrade.

On active SBC SWe boot up after power on, the SBC application comes up with an upgraded version. The configuration is automatically restored from other SBC SWe (currently running in an active role). To check the SBC SWe version, follow the below steps:

  1. Log in to VMware vCenter UI and then log in to SBC SWe VM Console as ‘linuxadmin.'

  2. Change to ‘root’ user using ‘sudo su –‘. 

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

SBC SWe Rollback

Use the following steps to roll back an SBC SWe HA on VMware vCenter using the OVA package.


Action
1

Shut down both active and standby SBC SWe VMs from the VMware vCenter console by selecting each VM and clicking Shut down.

2

Roll back SBC SWe to the old version.

Log in to the VMware ESXi server using SSH and ‘root’ user where active SBC SWe is present and restore the disk for active to the backed up SBC SWe root disk.

For example, using the following configurations, restore the disk to the backed-up SBC SWe root disk, SSH to VMware ESXi server using the 'root' user and run the commands below

  • 172.19.201.11 IP as the VMware ESXi server
  • SBC SWe VM name of ‘SBC1’
  • 'datastore1' as the datastore name for this VMware ESXi server, 

(Replace 'SBC1' with the name of the VM in the below commands if your VM name is 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

Repeat this step for the standby SBC SWe.

3

Power on active and standby SBC SWe VMs from the VMware vCenter console by selecting each VM and clicking Power on.

4

Validate the SBC SWe Rollback.

Once the SBC SWe boots up after a power-on, the SBC SWe application comes up to the previous version on both the active and standby VMs. 

  1. Login to VMware vCenter UI
  2. Log in to 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.