SBC SWe Configuration Management in Direct Single Mode

SBC SWe 1:1 HA cluster deployments can be configured in the EMS to use the Direct Single configuration model described in this topic. 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 Configuration Model

The Direct Single configuration model applies to deployments in which there is a single active SBC node, such as standalone or 1:1 HA deployments. A Direct Single deployment must be instantiated with the SBC HA mode specified as "1to1." For this small type of deployment, the SBC node itself provides the northbound interfaces for the VNF while the EMS continues to provide a repository to store the configuration history. In 1:1 HA deployments, the active node replicates configuration changes to the backup node.

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 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. The active SBC node 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)