Versions Compared

Old Version 5

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 6

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1
REV5
REV6
REV3
REV1

 

Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

Info
titleNote:

Prior releases supported the use of a dedicated SBC Configurator cluster to configure other SBC SWe clusters. This approach is replaced by using one of the SBC nodes within the cluster, referred to as the "Head End" SBC, to configure the other nodes. While the SBC Configurator currently remains supported for backward compatibility, it will be deprecated in a subsequent release. It is strongly recommended that you adopt the Head End SBC configuration model. Refer to Configuring an SBC SWe Cluster using the EMS.

 

This section describes the upgrade procedure of M-SBC instances in N:1 Redundancy Group (RG).

Prerequisite

Perform the following activities prior to upgrading the M-SBC in an RG.

Download the Software Image

Download the required .QCOW2 and .md5 files from the Customer Portal.

Upload the Software Image to OpenStack

To upload the .QCOW2 file to the OpenStack, navigate to Project > Compute > Images. For more information, refer to Creating a Glance Image.

Check the Status of the Instances

In an M-SBC Redundancy Group, ensure all the five instances (4:1) , and the SBC Configurator instance, and EMS is are up and running.

To check the instances, navigate to Project > Compute > Instances. The Instances window is displayed. The Instances window displays the status of the current image.

Caption
0Figure
1M-SBC Instances in an RG

Identify the Assigned Standby Instance

To identify the assigned standby instance, perform the following steps:

  1. Log on to CLI of any of the instances as admin user. Execute the following command and check the value of the parameter assignedRole.  

    Code Block
    > show status system rgStatus
rgStatus vsbc1-192.168.2.3 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          1;
    serviceId       0;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.3;
    appVersion      V06.02.01A013;
}
rgStatus vsbc1-192.168.2.4 {
    actualCeName    vsbc1;
    assignedRole    standby;
    currentRole     standby;
    nodeId          2;
    serviceId       1;
    syncStatus      unprotectedRunningStandby;
    usingMetavarsOf vsbc1-192.168.2.4;
    appVersion      V06.02.01A013;
}
rgStatus vsbc1-192.168.2.5 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          3;
    serviceId       2;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.5;
    appVersion      V06.02.01A013;
}
rgStatus vsbc1-192.168.2.6 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          4;
    serviceId       3;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.6;
    appVersion      V06.02.01A013;
}
rgStatus vsbc1-192.168.2.7 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          5;
    serviceId       4;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.7;
    appVersion      V06.02.01A013;
}

Anchor
Upgrade Process
Upgrade Process
Upgrade Process

Info
titleNote
  • The assignedRole standby instance must be upgraded first, followed by the active instances.
  • Only one instance must be upgraded at a time.

Perform the following steps to upgrade.

  1. On OpenStack, navigate to Project > Compute > Instances. The Instances window is displayed.

  2. Anchor
    Rebuild
    Rebuild
    From the drop-down list corresponding to the standby instance, select the option Rebuild Instance.
    Caption
    0Figure
    1Selecting Rebuild Instance Option


    The Rebuild Instance window is displayed.

  3. Click Rebuild Instance to rebuild the instance with the upgraded image details.

    Caption
    0Figure
    1Rebuild Instance


    The status of the Task column is displayed as Rebuilding.
    Caption
    0Figure
    1Rebuilding Process

  4. Repeat the steps (1 to 3 from the Upgrading M-SBC in N:1 Redundancy Group section) to upgrade the active instances one by one. Before upgrading an instance,
    check syncStatus field in rgStatus output to ensure that all the currently active instances are in syncCompleted state. The standby instance displays syncStatus as unprotectedRunningStandby. For more information, see section Upgrading M-SBC in N:1 Redundancy Group.

    Once the rebuilds are completed, all the instances will be running with the upgraded image details.

    Caption
    0Figure
    1Rebuilding Process Completed for All the Instances

Anchor
Post-Upgrade Monitoring
Post-Upgrade Monitoring
Post-Upgrade Monitoring

To verify if the instances are up and running with the upgraded software image:

  1. Log on to CLI of any of the instances as admin user.

  2. Execute the following command and check the appVersion field for each of the instances. Check syncStatus field in rgStatus output to ensure that all the currently active instances are in syncCompleted state. The standby instance displays syncStatus as unprotectedRunningStandby.

    Code Block
    > show status system rgStatus
rgStatus vsbc1-192.168.2.3 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          1;
    serviceId       0;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.3;
    appVersion      V06.02.01A022;
}
rgStatus vsbc1-192.168.2.4 {
    actualCeName    vsbc1;
    assignedRole    standby;
    currentRole     standby;
    nodeId          2;
    serviceId       1;
    syncStatus      unprotectedRunningStandby;
    usingMetavarsOf vsbc1-192.168.2.4;
    appVersion      V06.02.01A022;
}
rgStatus vsbc1-192.168.2.5 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          3;
    serviceId       2;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.5;
    appVersion      V06.02.01A022;
}
rgStatus vsbc1-192.168.2.6 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          4;
    serviceId       3;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.6;
    appVersion      V06.02.01A022;
}
rgStatus vsbc1-192.168.2.7 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          5;
    serviceId       4;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.7;
    appVersion      V06.02.01A022;
}
Info
titleNote
  • Upgrading a Redundancy Group impacts the service provided by all the instances of the group.
  • The upgrade process of a Redundancy Group is completed only after all the instances of the group are upgraded to the same build.
  • If the upgrade fails for any of the instances, you must revert back all the instances of the group to the previous build using the Rebuild Instance process.

 

Pagebreak