Page History
Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Internal_display_only | ||||||
---|---|---|---|---|---|---|
|
Internal_display_only |
---|
Panel | ||||||
---|---|---|---|---|---|---|
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:
- 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 | ||
---|---|---|
| ||
|
Start
Download the OVA packagePackage
Download the new OVA package and upload it to the VMware ESXi host.
For example, ifsbc-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
- Shut down the standby SBC SWe VM from the VMware ESXi console by selecting the VM and clicking Shut down.
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
- Shut down
Power on the Standby SBC SWe VM from the VMware ESXi console
- 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 –
‘ - 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
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
Take a backup of the previous SBC SWe root disk for the Active SBC SWe.
(In this example, the SBC SWe VM name is ‘SBC2
SBC1
’. 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
Make a compatible root disk from the new VMDK image using ‘
vmkfstools
’.
(In this example, the SBC SWe VM name is ‘SBC2
SBC1
’. 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.
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
- Select the VM and click Power on.
Validate the
ActiveSBC SWe upgrade
from other SBC SWe (which is currently running in the Active role)
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.
- 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
Run the
:swinfo
command to check the SBC SWe version.
Code Block swinfo
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 |
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 | ||
---|---|---|
| ||
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 | ||
---|---|---|
| ||
vmkfstools -X 65G SBC2.vmdk |
Info | ||
---|---|---|
| ||
Match the new root disk size with the existing one. |
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 | ||
---|---|---|
| ||
Verify that all sync statuses are marked as ' |
Shut down the Active SBC VM
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
- 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
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
- 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
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.
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 Run the
swinfo
command to check the SBC SWe version: swinfoCode Block .