Page History

SBC SWe 1:1 HA cluster deployments can be configured in the EMS to use either the Direct Single configuration model described in this topic, or the OAM node model. For . For more information on deployment requirements, refer to Specifying Cluster Configuration Mode Parameters in Heat Deployments if you deploy using Heat templates, or refer to Instantiating SBC SWe on OpenStack using VNFM if you deploy using VNFM.  Refer to Creating an SBC Cluster for more information on cluster configuration in the EMS.

Direct Single Mode Configuration

When an SBC cluster is operating in Direct Single configuration mode, the active SBC node holds the active configuration for the cluster and it replicates changes to the standby node, if one is present. To update the cluster configuration, make changes on the active SBC node using either the CLI or the SBC Configuration Manager GUI. Refer to Modifying SBC Cluster Configuration for details on using these methods to configure the cluster. The changes you commit through CLI or save in SBC Configuration Manager take effect on the active node immediately.

To subsequently save and activate configuration changes in the configuration revision on the EMS using the CLI, issue a saveAndActivate command. In the GUI, click the Save button in the top bar of the SBC Configuration Manager window. Refer to Accessing Configuration Interfaces for SBC SWe Clusters for details on using either the SBC Configuration Manager or the SBC CLI to configure the cluster. Once you save and activate your configuration changes, the The active SBC node also saves the configuration revision to the configuration history list stored on the EMS. 

Configuration History 

Within the EMS Cluster Management GUI, you can use the cluster configuration history to revert the cluster configuration to a prior revision. Refer to Reverting Configuration Changes (Direct Single Mode)