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

Compare with Current View Page History

« Previous Version 2 Next »

In this section:

Overview

The SBC on AWS supports upgrades and reverts from the following releases to 12.01.xx. 

Upgrade from SBC VersionUpgrade Method
09.02.00R002Manual (offline) - Volume-based upgrade
09.02.01R000Manual (offline) - Volume-based upgrade
09.02.03R000Manual (offline) - Volume-based upgrade - instances launched with IAC


Offline upgrades are service-impacting.


Due to enforced security features (admin ssh key requirement), and cgroup support, Ribbon requires updating SBC instance user-data in prior releases before attempting an upgrade.

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.

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 first on the standby SBC, and then on the formerly active SBC.

Update Standby SBC user-data

  1. Log onto the standby SBC management IP as user linuxadmin.

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

  3. Exit standby unit.

  4. Log into the active unit as admin.

  5. Ensure the current role active SBC instance sync status shows syncCompleted and app IP and versions are correct.

    Verify sync status
    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
  6. Log onto AWS.

  7. Click the Services drop-down list.
    The Services list is displayed.

  8. Click EC2 from Management Tools section.

    To stop the Unit

  9. Login to the standby unit as linuxadmin and sudo to root using (sudo su -)
  10. Stop the instance using the command "shutdown -h now".

  11. Using the left navigation panel of the AWS EC2 dashboard, navigate to INSTANCES > Instances.

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

  13. Once the Instance State shows stopped, proceed to the next step.


    To update user data

  14. Right click on the Instance on the AWS Dashboard and choose Instance Settings > View/Change Userdata.

  15. Update the user data to include entries for "AdminSshKey", "ThirdPartyCpuAlloc",  and "ThirdPartyMemAlloc" in accordance with the example below:

    Note

     Refer 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"
}

  16. Click save to save the user data.

    To Re-Start unit

  17. Again, select the desired instance.

  18. Right click or use the Actions pull-down to choose InstanceState > Start.

  19. Click Yes, Start when prompted for confirmation. 

  20. Wait for the instance to run with 2/2 Status Check showing "success". 

  21. 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 recovery
    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
===================================================

  22. Log into the active SBC as admin and wait for the Current role Active instance syncStatus to show syncCompleted.

    Verify sync status
    admin@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


Update Formerly Active SBC user-data

Repeat the previous procedure on the formerly active SBC.

HA SBC Upgrade Steps

Once the 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.

  • No labels