Page History

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

OAM Node Configuration

When an SBC cluster is operating in OAM configuration mode, the active OAM node holds the active configuration for the cluster and is responsible for sharing this configuration with the SBC nodes in the cluster. When you need to update the configuration of the cluster, you make the configuration changes on the active OAM node using either the CLI or the SBC Configuration Manager GUI. Once you save and activate your configuration changes, the OAM node notifies the SBC nodes within the cluster of the change. The SBC nodes collect the configuration change list from the OAM node and apply the changes to their local configuration. The OAM node also saves the configuration revision to the configuration history stored on the EMS.

As you make configuration changes, the OAM node maintains a record of any interim “commit” commands you issue in the CLI or save actions you request on individual pages in the SBC Configuration Manager GUI. However, it does not update the configuration database, notify the nodes to pick up changes, or save the configuration revision on the EMS until you issue an explicit request to save and activate the change. In the CLI, this requires issuing the saveAndActivate command. In the GUI, you must click the Save button in the top bar of the SBC Configuration Manager window to save and activate your changes. Refer to Accessing Configuration Interfaces for SBC SWe Clusters for details on using both SBC Configuration Manager and the SBC CLI.

Node-level Data and Configuration

In an SBC cluster deployment, most configuration settings are common across nodes and are part of the homogeneous configuration that the OAM node propagates to the nodes. However when necessary, you can perform actions or retrieve operational data from individual nodes. A limited number of configurations can also be set on an individual node. To facilitate these node-specific interactions, the SBC configuration model includes a “node” branch when a cluster is operating in OAM configuration mode. The node branch is accessible through either CLI or in the SBC Configuration Manager GUI. Refer to

Node-level Data and Configuration (OAM Mode)

Configuration History 

Within the EMS Cluster Management GUI, you can use the cluster configuration history to review the set of configuration changes applied with each save and activate action. It also enables reverting the cluster configuration to a prior revision. Refer to

Reviewing Configuration Changes and Reverting to a Prior Configuration (OAM Mode)