Page History

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

Identify the Currently Running 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 To identify the currently running standby instance, perform the following steps:

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

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

   Code Block

   > show status system rgStatus rgStatus vsbc1-192.168.2.3 { actualCeName vsbc1; assignedRole active; currentRole active; nodeId 61; serviceId 50; 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 42; serviceId 31; syncStatus syncCompletedunprotectedRunningStandby; 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 54; serviceId 43; 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 15; serviceId 04; syncStatus syncCompleted; usingMetavarsOf vsbc1-192.168.2.7; appVersion V06.02.01A013; }

3. From the output of the standby instance, check the IP address, mentioned in the "Instance Rg Name". It corresponds to the ha-net IP address of that instance. For example, in the above output, IP address "192.168.2.4" corresponds to ha-net IP for the standby instance with Instance Rg Name: vsbc1-192.168.2.4.

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

Anchor
Upgrade Process Upgrade Process

Upgrade Process

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
   0 Figure 1 Selecting Rebuild Instance Option

   
   The Rebuild Instance window is displayed.

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

   Caption
   0 Figure 1 Rebuild Instance

   
   The status of the Task column is displayed as Rebuilding.

   Caption
   0 Figure 1 Rebuilding Process

   
   Ensure to proceed with the rebuilding of the rest of the instances only when the rgstatus shows syncStatus as unprotectedRunningStandby.


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, the rgStatus must show syncStatus as syncCompleted.

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

   Caption
   0 Figure 1 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:

1. Log on to CLI of any of the upgraded 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 41; serviceId 30; 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 12; serviceId 01; syncStatus syncCompletedunprotectedRunningStandby; usingMetavarsOf vsbc1-192.168.2.4; appVersion V06.02.01A022; } rgStatus vsbc1-192.168.2.5 { actualCeName vsbc1; assignedRole active; currentRole active; nodeId 53; serviceId 42; 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 64; serviceId 53; 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 35; serviceId 24; syncStatus syncCompleted; usingMetavarsOf vsbc1-192.168.2.7; appVersion V06.02.01A022; }

   Execute the following command to check the sync status:

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