Page History

This section describes the upgrading 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 file 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 (RG), ensure all the five instances (4:1), configurator 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 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 To identify the standby instance, perform the following steps:

1. Log

   in as root user to the instance

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

2. Execute the the following command getUserData and check the value values of the parameter CERole Caption

   0	Figure
   1	getUserData Command Showing the Instance Status

   Image Removedparameters assignedRole and currentRole. For the 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 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; }

3. From the output, check the ha-net IP of the standby instance.

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

Anchor
Upgrade Process Upgrade Process

Upgrade Process

Repeat the above steps for each instance until you identify the standby instance.

Perform the following steps to upgrade.

Selecting the Image

To select an image:

1. On the 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
   Image Added

   
   The status of the Task column is displayed .

1. as Rebuilding.

   Caption
   0 Figure 1 Rebuilding Process
   Image Added

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

   Caption
   0 Figure 1 Rebuilding Process Completed for All the Instances
   Image Added

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:

   Code Block

   > 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; }

3. 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; }