When you deploy SBC nodes as a cluster, you have a choice of two cluster configuration models: OAM Node and Direct Single. Both models involve cluster management capabilities provided by the Insight EMS. Refer to Configuring SBC SWe Cloud Deployments for an overview of the models. Select a configuration management model before you deploy to ensure you populate the parameters the model requires.
The following sections describe parameters required by each configuration model. The required input could be specified directly in the Heat template or supplied when you instantiate.
For N:1 HA distributed deployments, use the OAM node configuration model. In this model, the cluster includes a 1:1 HA pair of dedicated Operations, Administration, and Maintenance (OAM) nodes to configure the SBC nodes within the cluster. The EMS provides storage of a configuration history.
Create an SBC cluster configuration in the EMS before you deploy the OAM nodes so that nodes can register properly. In the EMS, specify the cluster "Configuration Type" as "OAM." Refer to Creating an SBC SWe Cluster in EMS documentation for more details on creating an SBC cluster.
When instantiating the OAM nodes:
After deploying the OAM nodes, instantiate the SBC nodes in the cluster with the following parameters:
For standalone or 1:1 HA deployments, use the Direct Single configuration model. In this model the active SBC node is used to configure. Configuration changes are synchronized from the active to the standby node, if one is present. The EMS provides storage of a configuration history.
Create the SBC cluster configuration in the EMS before you deploy the SBC node(s), so that the nodes can register properly. In the EMS, specify the cluster "Configuration Type" as "Direct Single." Refer to Creating an SBC SWe Cluster in EMS documentation for more details on creating an SBC cluster.
When instantiating SBC nodes to use Direct Single configuration: