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. 

EMS Procedure

From the EMS, you can review the 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 revert restore the cluster configuration back to a prior revision level, when necessary.

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 Configuration History tab. A list of the stored configuration revisions opens. 

   Caption
   0 Figure 1 Cluster Configuration History

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

Restoring a Prior Configuration

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 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 command syntax is shown below.

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