Page History

Add_workflow_for_techpubs

AUTH2	UserResourceIdentifier{userKey=8a00a0c87e188912017e4c24a00e0016, userName='null'}
AUTH1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTH	SBX-128576
REV5	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6	UserResourceIdentifier{userKey=8a00a0c87e188912017e4c24a00e00168a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3	UserResourceIdentifier{userKey=8a00a0c86573c09001658fb5ccb800158a00a0c880e94aad0181077fa2530009, userName='null'}
REV1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc4107b48a00a0c880e94aad0181077fa2530009, userName='null'}

Internal_display_only

server	Ribbon JIRA
serverId	d45d42c2-4546-3f1b-bbde-ff79196e8c48
key	SBX-131520

Internal_display_only

Panel

In this section:

Table of Contents

maxLevel	4
minLevel	2

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:

SSH access to VMware ESXi for root user is enabled.
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.

Info

title	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

Download the OVA packagePackage
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:
  Code Block
  scp sbc-V11.01.00R000-connexip-os_11.00.00-R000_12_amd64.ova root@172.19.201.11:/vmfs/volumes/datastore1/
Check the sync status
Login to Confd CLI on the active SBC SWe using ‘admin’ user and check the sync status:
Code Block
ssh admin@<active_SBC_mgmt_ip> admin@vsbc1> show table system syncStatus
Info
title Note
Verify that all sync statuses are marked as 'syncCompleted' before proceeding.
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.

Upgrade the Standby SBC SWe to new version

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:

Code Block
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

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)

Code Block
cd /vmfs/volumes/datastore1/SBC2 mv SBC2.vmdk SBC2.vmdk_backup mv SBC2-flat.vmdk SBC2-flat.vmdk_backup

Save the SBC SWe configuration

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

Save the instance-specific configuration of the VM:

Code Block
/opt/sonus/sbx/scripts/saveConfig_fe.sh

Info

title	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.

Shut down the VM
1. Shut down

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)

Code Block
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

Info

title	Note

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

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.

Code Block
vmkfstools -X <Size_in_GB>G SBC2.vmdk

Code Block

title	Example: New size is 65 GB

vmkfstools -X 65G SBC2.vmdk

Info

title	Note

Match the new root disk size with the existing one.

Power on the Standby SBC SWe VM from the VMware ESXi console
1. Select the the VM and click Power on.
Validate the Standby SBC SWe Upgrade
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.
Login to the VMware ESXi host via a web browser
Login to the SBC SWe VM Console as ‘linuxadmin’ and change to ‘root’ user using ‘sudo su –‘

Check the SBC SWe version:

Code Block
swinfo

Check the Sync status

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

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

Info

title	Note

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

Shut down the Active SBC VM

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

Upgrade the Active SBC SWe to a the new version
1. Login into the VMware ESXi server using SSH and as the ‘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 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 using as the 'root' user .and run:
  Code Block
  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 for the Active SBC SWe.
  (In this example, the SBC SWe VM name is ‘SBC2SBC1’. Replace it with the name of your VM name, if different)
  Code Block
  title 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 ‘SBC2SBC1’. Replace it with the name of your VM name, if different)
  Code Block
  title 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
  Info
  title 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.
  Code Block
  vmkfstools -X <Size_in_GB>G SBC1.vmdk
  Code Block
  title Example: New size is 65 GB
  vmkfstools -X 65G SBC2SBC1.vmdk
  Info
  title Note
  Match the new root disk size with the existing one.
Power on the Active SBC SWe VM from the VMware ESXi console
1. Select the VM and click Power on.
Validate the
Active
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
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
  Run the swinfo command to check the SBC SWe version
  :
  .
  Code Block
  swinfo

SBC SWe Rollback

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

Start

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.
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 to 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 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)
  Code Block
  title 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
Power on the VM
1. Power on both the active and standby SBC SWe VM from the VMware ESXi console by selecting the VMs VM and clicking Power on.
Validate the SBC SWe Rollbackrollback
1. Once the SBC SWe boots up after the a 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 Run the swinfo command to check the SBC SWe version:
    Code Blockswinfo
    .

Space shortcuts

Page tree

Versions Compared

Old Version 1

New Version Current

Key

Overview

Scope

Prerequisites

SBC SWe Upgrade

SBC SWe Rollback