You can configure SBC SWe 1:1 HA cluster deployments from the
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
Create SBC Clusters for more information on cluster configuration in
.
Multiexcerpt include |
---|
MultiExcerptName | DirectSingleOverview |
---|
PageWithExcerpt | SBXDOC121:SBC SWe Configuration Management |
---|
|
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
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
.
Configuration History
Within the
Cluster Management, you can use the cluster configuration history to revert the cluster configuration to a prior revision. Refer to
Reverting Direct Single Mode Configuration Changes.