Upgrading M-SBC in N:1 Redundancy Group

In this section:

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 Salesforce 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 Glance Image.

Check the Status of the Instances

In an M-SBC Redundancy Group, ensure all the five instances (4:1), the SBC Configurator instance, and EMS is 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.

M-SBC Insatnces in an RG

Identify the Standby Instance

It is recommended to note down the IP addresses and ports (packet and management) of your standby instance while you created the RG.

In case you do not have the information readily available, to identify the standby instance, perform the following steps:

Log on to console as application admin on any of the instances.

Execute the the following command and check the values of the parameters assignedRole and currentRole. For the standby instance, the currentRole value must be standby.

> show status system rgStatus
rgStatus vsbc1-192.168.2.3 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          6;
    serviceId       5;
    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          4;
    serviceId       3;
    syncStatus      syncCompleted;
    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          5;
    serviceId       4;
    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          1;
    serviceId       0;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.7;
    appVersion      V06.02.01A013;
}

From the output, check the ha-net IP of the standby instance.
From the OpneStack dashboard, note the Management IP of the standby instance by comparing the ha-net IP.

Upgrade Process

Note

The configured 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.

On OpenStack, navigate to Project > Compute > Instances. The Instances window is displayed.
From the drop-down list corresponding to the standby instance, select the option Rebuild Instance.

Selecting Rebuild Instance Option

The Rebuild Instance window is displayed.
Click Rebuild Instance to rebuild the instance with the upgraded image details.

Rebuild Instance

The status of the Task column is displayed as Rebuilding.

Rebuilding Process
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.
Once the rebuilds are completed, all the instances will be running with the upgraded image details.

Rebuilding Process Completed for All the Instances

Post-Upgrade Monitoring

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

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

Execute the following command:

> show status system rgStatus
rgStatus vsbc1-192.168.2.3 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          4;
    serviceId       3;
    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          1;
    serviceId       0;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.4;
    appVersion      V06.02.01A022;
}
rgStatus vsbc1-192.168.2.5 {
    actualCeName    vsbc1;
    assignedRole    active;
    currentRole     active;
    nodeId          5;
    serviceId       4;
    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          6;
    serviceId       5;
    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          3;
    serviceId       2;
    syncStatus      syncCompleted;
    usingMetavarsOf vsbc1-192.168.2.7;
    appVersion      V06.02.01A022;
}

Execute the following command to check the sync status:

> show status system syncStatus
syncStatus "Metavar Data" {
    status syncCompleted;
}
syncStatus "Call/Registration Data" {
    status syncCompleted;
}