Page History

When an SBC SWe cluster is operating in Direct Single configuration mode, the active SBC node saves configuration revisions on the EMS. A new revision number is defined after you explicitly save and activate a set of configuration changes. You have the option to restore the cluster configuration back to a prior revision level, when necessary. 

Restoring a Prior Configuration using EMS

From the EMS, you can review the a list of stored revisions. Each revision is identified by a revision number and a timestamp when the configuration was created. You have the option to restore the cluster configuration back to a prior revision level, when necessary. Restoring a prior configuration requires the SBC nodes to restart. 
Note that if revision you specify to restore was created with a different software release, the nodes do not restart automatically. If you are migrating an older revision to a newer software version, you can restart manually to complete the restore process. If you are preparing to upgrade/downgrade, you can rebuild with the software that is at the same release level of the specified revision.

Prerequisite - EMS

Before performing a restore operation, ensure that the SBC node that has the "primary" role also has its management redundancy role specified as “active.” If the primary node has the role of "standby," you must perform a switchover so that the primary node becomes active.

1. Log onto the EMS.
2. Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters on the EMS.
3. Click the radio button adjacent to the name of the cluster. The Details tab for the selected cluster opens by default. 

4. Click the Configurations tab. 

5. Click Edit Configuration to launch the SBC Configuration Manager.
6. Navigate to: All > System > ServerAdmin The Server Admin window opens.
   Check the output to identify which node has the Role of Primary.
7. Navigate to: All > System > ServerStatus The Server Status window opens.
   Check the output to identify which node has the Mgmt Redundancy Role of Active.
8. Continue with the restore procedure if the redundancy role of the primary node is "active." Otherwise, use the switchover command to switch the redundancy roles of the nodes: 
   1. Navigate to All > System > Admin The Admin window opens.
   2. Select the node in the Admin List.
   3. Scroll down to the Admin Commands section.
   4. Select Switchover in the Commands list and click Select.
   5. Recheck the Server Admin and Server Status windows to ensure that the primary node has the active redundancy role.

Restore Configuration Procedure - EMS

Prior to executing a configuration restore on the EMS, you must stop the SBC application on the standby node. After the restore operation is complete you must start the SBC application again on the standby node. Use the EMA GUI to stop and start the standby node.

1. On the standby SBC node, log into the EMA.
2. Navigate to the platform management controls: Administration > System Administration > Platform Management
   The Platform and SBC Application Controls window opens.
3. Click Stop SBC Application at the top of the Status section.
4. Log onto the EMS.
5. Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters on the EMS.
6. Click the radio button adjacent to the name of the cluster. The Details tab for the selected cluster opens by default. 

7. Click the Configuration History tab. A list of the stored configuration revisions opens. 

   Caption
   0 Figure 1 Cluster Configuration History

8. Click the Restore icon adjacent to a revision to revert the cluster to the configuration that was in place when the selected revision was saved and activated. The active node downloads the selected configuration revision and reboots. If there is a standby node,

9. After the active node

   replicates the configuration to it along with a command to reboot. The active node saves the restored configuration revision back to the EMS and increments the revision number.
   Note that if the specified revision was created with a different software release, the nodes do not restart automatically. If you are migrating an older revision to a newer software version, you can restart manually to complete the restore process. If you are preparing to upgrade/downgrade, you can rebuild with the software that is at the same release level of the specified revision.

1. completes rebooting and initializing, return to the Platform and SBC Application Controls window in the EMA of the standby node and click Start SBC Application.

Once the standby node restarts, the restore configuration procedure is complete

.

Restoring a Prior Configuration using CLI

The CLI request command's restoreRevision parameter reverts the configuration on managed SBC nodes to a specified prior configuration revision stored on the OAM node. Similar to when a revert is triggered from the EMS, restoring a prior configuration requires the SBC nodes to restart. 
Note that if the specified revision you specify to restore was created with a different software release, the nodes do not restart automatically. If you are migrating an older revision to a newer software version, you can restart manually to complete the restore process. If you are preparing to upgrade/downgrade, you can rebuild with the software that is at the same release level of the specified revision.

The basic command syntax is shown below. 

> request system admin <SYSTEM NAME> restoreRevision revision <revision number>

Prerequisite - CLI

Before performing a restore operation, ensure that the SBC node that has the "primary" role also has its management redundancy role specified as “active.” If the primary node has the role of "standby," you must perform a switchover so that the primary node becomes active.

1. Log into one of the nodes and execute the following command and check the output to identify which node has the "ROLE" of "primary."
   show table system serverAdmin
2. Execute the following command and check the output to determine the "MGMT REDUNDANCY ROLE" of the primary node:
   show table system serverStatus
3. Continue with the restore procedure if the redundancy role of the primary node is "active." Otherwise, execute the following command to switch the redundancy roles of the nodes:
   request system admin <SYSTEM NAME> switchover
   Repeat the show table system commands to confirm that the primary node has the active redundancy role.

Restore Configuration Procedure - CLI

Prior to executing the restore command on the active node, you must stop the SBC application on the standby node. After the restore operation is complete you must start the SBC application again on the standby node. Use the EMA GUI to stop and start the standby node.

1. On the standby SBC node, log into the EMA.
2. Navigate to the platform management controls: Administration > System Administration > Platform Management
   The Platform and SBC Application Controls window opens.
3. Click Stop SBC Application at the top of the Status section.
4. From the CLI of the active node, execute the restore command:
   

   request system admin <SYSTEM NAME> restoreRevision revision <revision number>
   where <revision number> identifies the number of the revision you want to restore. The active node reboots as part of the restore process.

5. After the active node completes rebooting and initializing,return to the Platform and SBC Application Controls window in the EMA of the standby node and click Start SBC Application.

Once the standby node restarts, the restore configuration procedure is complete.