In this section:

Related articles:

SBC SWe clusters support 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 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.

OAM Node Configuration Model

For N:1 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 SWe cluster.

When instantiating the OAM nodes:

  • Set the parameter “CEMode” to “oam”
  • Set the HA mode (“SbcHaMode”) to “Nto1”
  • Set the SBC “personality” to match the SBC nodes in the cluster.
  • Specify the "Cluster/VNF Identifier" you configured in EMS as the OAM node cluster ID (cluster_id), and specify the EMS IP addresses for your EMS deployment.
  • Record the metavariable name you use for the Mgt0 IP address and plan to reuse it in the SBC node template so that both types of nodes get their IP addresses from the same network.

After deploying the OAM nodes, instantiate the SBC nodes in the cluster with the following parameters:

  • Set the SBC HA mode (“SbcHaMode”) to “Nto1”
  • Specify the "Cluster/VNF Identifier" you configured in EMS as the SBC node cluster ID (cluster_id), and specify the EMS IP addresses for your EMS deployment.
  • Specify the IP addresses for the OAM nodes (“oam_ip_1” and “oam_ip_2”).
  • Specify the same Mgt0 IP address metavariable name you used for the OAM node to ensure both types of nodes get their IP addresses from the same network.
Note

For large deployments including multiple N:1 redundancy groups within a cluster, you can use the same OAM nodes to manage more than one redundancy group. To use the same OAM nodes, specify the same OAM IP addresses when you instantiate the SBC nodes in the additional group.

Note

To use the Link Detection Group (LDG) capability in deployments with OAM nodes, the OAM node management interface should be configured to be the same as its managed SBC nodes, but the packet (pkt) interfaces should be configured to be different. Refer to Link Detection Group - CLI for more information on LDG configuration.

Direct Single Configuration Model

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 SWe cluster.

When instantiating SBC nodes to use Direct Single configuration:

  • Set the SBC HA mode (“SbcHaMode”) to “1to1”
  • Specify the "Cluster/VNF Identifier" you configured in EMS as the cluster ID (cluster_id), and specify the EMS IP addresses for your EMS deployment.