In this section:
Overview
This feature supports upgrades and revert from SBC 07.00.00S406, 07.00.00S407, 07.02.00S400, 07.02.00S401 and 07.02.03S40X to SBC 09.00.00R000 on AWS.
Note
You must accomplish the following:
- Update the SBC instance user-data on the prior release before attempting upgrades.
- Update the HFE.sh script manually during this upgrade.
This upgrade procedure supports an SBC HA or SBC HA with HFE upgrade.
Currently, upgrades are not supported in GCP.
Due to enforced security features (admin ssh key requirement), and cgroup support, upgrading from the prior release is impacted. Ribbon requires updating SBC instance user-data in prior releases before attempting an upgrade.
Refer to Linuxadmin sudo Permissions for SBC SWe in AWS for more information about ssh key requirements.
Refer to Implement C-group Support for Third-Party Software Installations for more details about Linux cgroup support. If the user wishes to use this feature after the upgrade, the user-data parameters ThirdPartyCpuAlloc and ThirdPartyMemAlloc must be set to a value other than zero(0) prior to upgrade.
After user-data updates are complete, perform the normal Replacement Upgrade/Revert of the SBC instance in AWS in accordance with Replacement Upgrade for AWS.
HA SBC Upgrade
HA SBC Pre-Upgrade Steps
To update the user-data to include admin ssh keys and 3rd Party cgroup information for an HA SBC Pair, complete the following procedure.
Update Standby SBC user-data
Log into the standby SBC management IP as user linuxadmin.
sudo to root and verify that this unit has a "current host role" indicating standby using the swinfo command.
linuxadmin@vsbc2:~$ sudo su [root@vsbcSystem-vsbc2 linuxadmin]# swinfo =================================================== SERVER: vsbc2 OS: V06.00.00-S406 SonusDB: V07.00.00-S406 EMA: V07.00.00-S406 SBC: V07.00.00-S406 SBC Type: isbc Management mode: xxx Build Number: xxx =================================================== Installed host role: standby Current host role: standby =================================================== =================================================== SERVER: vsbc1 OS: V06.00.00-S406 SonusDB: V07.00.00-S406 EMA: V07.00.00-S406 SBC: V07.00.00-S406 SBC Type: isbc Management mode: xxx Build Number: xxx =================================================== Installed host role: active Current host role: active ===================================================
Exit standby unit.
Log into the active unit as admin.
Ensure the current role active SBC instance sync status shows syncCompleted and app IP and versions are correct.
Verify sync statusadmin@vsbc1> show table system rgStatus ACTUAL CE ASSIGNED CURRENT NODE SERVICE INSTANCE RG NAME NAME ROLE ROLE ID ID SYNC STATUS USING METAVARS OF APP VERSION ------------------------------------------------------------------------------------------------------------------------------ vsbc1-172.31.11.73 vsbc1 active standby 1 1 unprotectedRunningStandby vsbc1-172.31.11.73 V07.00.00S406 vsbc2-172.31.11.101 vsbc2 standby active 2 0 syncCompleted vsbc2-172.31.11.101 V07.00.00S406- Log onto AWS.
Click the Services drop-down list.
The Services list is displayed.Click EC2 from Management Tools section.
To stop the Unit
- Login to the standby unit as linuxadmin and sudo to root using (sudo su -)
- Stop the instance using the command "shutdown -h now".
Using the left navigation panel of the AWS EC2 dashboard, navigate to INSTANCES > Instances.
Locate the standby Instance in the list. (for example, if using EIP for management IP, enter the following into the instances search bar type "Public IP : <standby management ip>" and hit enter to quickly find the instance)
Once the Instance State shows stopped, proceed to the next step.
To update user data- Right click on the Instance on the AWS Dashboard and choose Instance Settings > View/Change Userdata.
Update the user data to include entries for "AdminSshKey", "ThirdPartyCpuAlloc", and "ThirdPartyMemAlloc" in accordance with the example below:
NoteRefer to Linuxadmin sudo Permissions for SBC SWe in AWS for details on generating an ssh key for use with "AdminSshKey".
HA user-data{ "ALT_Mgt0_00": "LOGICAL_MGMT_IP", "ALT_Pkt0_00": "VIP1", "ALT_Pkt1_00": "VIP2", "AdminSshKey": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCJnrFMr/RXJD3rVLMLdkJBYau+lWQ+F55Xj+KjunVBtw/zXURV38QIQ1zCw/GDO2CZTSyehUeiV0pi2moUs0ZiK6/TdWTzcOP3RCUhNI26sBFv/Tk5MdaojSqUc2NMpS/c1ESCmaUMBv4F7PfeHt0f3PqpUsxvKeNQQuEZyXjFEwAUdbkCMEptgaroYwuEz4SpFCfNBh0obUSoX5FNiNO/OyXcR8poVH0UhFim0Rdneo7VEH5FeqdkdGyZcTFs7A7aWpBRY3N8KUwklmNSWdDZ9//epEwgaF3m5U7XMd4M9zHURF1uQ/Nc+aiyVId9Mje2EU+nh6npaw/tEOPUiC1v", "CEName": "ISBC90R0SBC01", "CERole": "ACTIVE", "ClusterIp": "172.31.11.32", "HFE": "172.31.10.161", "IAM_ROLE": "SWe", "NodeName": "MA-90R0-91-Upgrade-HFEHA", "PeerCEHa0IPv4Address": "172.31.11.32", "PeerCEName": "ISBC90R0SBC02", "ReverseNatPkt0": "True", "ReverseNatPkt1": "False", "SbcHaMode": "1to1", "SbcPersonalityType": "isbc", "SortHfeEip": "True", "SystemName": "ISBC90R0SBC", "TemplateName": "AWS_HA_template.json", "TemplateVersion": "V09.00.00R000", "ThirdPartyCpuAlloc": "0", "ThirdPartyMemAlloc": "0" }Click save to save the user data.
To Re-Start unit
Again, select the desired instance.
Right click or use the Actions pull-down to choose InstanceState > Start.
- Click Yes, Start when prompted for confirmation.
Wait for the instance to run with 2/2 Status Check showing "success".
Log into this "current host role" standby instance as linuxadmin and use the swinfo tool to wait for the system to recover as standby. This will take approximately 10 minutes.
swinfo to check for standby system recoverylinuxadmin@vsbc2:~$ sudo su [root@vsbcSystem-vsbc2 linuxadmin]# swinfo =================================================== SERVER: vsbc2 OS: V06.00.00-S406 SonusDB: V07.00.00-S406 EMA: V07.00.00-S406 SBC: V07.00.00-S406 SBC Type: isbc Management mode: xxx Build Number: xxx =================================================== Installed host role: standby Current host role: standby =================================================== =================================================== SERVER: vsbc1 OS: V06.00.00-S406 SonusDB: V07.00.00-S406 EMA: V07.00.00-S406 SBC: V07.00.00-S406 SBC Type: isbc Management mode: xxx Build Number: xxx =================================================== Installed host role: active Current host role: active ===================================================
Log into the active SBC as admin and wait for the Current role Active instance syncStatus to show syncCompleted.
Verify sync statusadmin@vsbc1> admin@vsbc1> show table system rgStatus ACTUAL CE ASSIGNED CURRENT NODE SERVICE INSTANCE RG NAME NAME ROLE ROLE ID ID SYNC STATUS USING METAVARS OF APP VERSION ------------------------------------------------------------------------------------------------------------------------------ vsbc1-172.31.11.73 vsbc1 active standby 1 1 unprotectedRunningStandby vsbc1-172.31.11.73 V07.00.00S406 vsbc2-172.31.11.101 vsbc2 standby active 2 0 syncCompleted vsbc2-172.31.11.101 V07.00.00S406
To update formerly active user-data- Repeat steps 9-22 for the active unit.
HA SBC Upgrade Steps
Once the SBC 07.02.00S401 pre-upgrade steps are completed successfully, perform the upgrade at Replacement Upgrade for AWS.
If you deployed with HFE, proceed to Upgrade HFE Node for AWS.
Overview
Content Tools