DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.


In this section:

Related articles:

Similar to other types of SBC Core deployments, you can configure and manage SBC SWe deployed in an OpenStack cloud by directly accessing its CLI or EMA UI. However, in virtualized environments, you can also deploy SBC nodes as clusters. An SBC cluster can contain one to many nodes but, regardless of number, the cluster presents the nodes as a single, logical SBC service.

To present the combined node capabilities in this way, clustered nodes are configured with a common, homogeneous configuration. SBC SWe supports two configuration models to support different types of SBC deployments: OAM and Direct Single. You select the configuration type for the cluster when you create the cluster configuration in the Insight EMS. For both models, the Insight EMS provides cluster management including a storage repository for cluster configurations. This repository function enables reverting a cluster to a prior configuration, or copying a configuration to a new cluster. Refer to Creating an SBC SWe Cluster for more information on cluster configuration in the EMS.

Note

In prior releases, a designated “Headend” SBC was used to configure SBC SWe clusters. Beginning with SBC release 8.0, the OAM node and Direct Single configuration models replace the Headend model. To enable migration to one of the new models, Insight EMS 12.x continues to support the Headend configuration model for SBC clusters on prior releases. However SBC SWe clusters on release 8.0 or later must use either the OAM node or Direct Single configuration model.


OAM Node Configuration Model

The OAM node configuration model incorporates a 1:1 HA pair of dedicated Operations, Administration, and Maintenance (OAM) nodes to configure and manage SBC nodes in N:1 deployments. In an N:1 deployment, multiple nodes (up to 4) are active at the same time and the active nodes are backed up by a single backup node. An OAM Node deployment must be instantiated with the SBC HA mode specified as "Nto1." The OAM nodes must be deployed in 'Nto1' mode with N=1.

SBC Clusters with OAM Nodes


The OAM node provides the northbound interface for the VNF, including SSH/CLI, NetConf, and REST interfaces. You use the OAM node interfaces to configure the cluster. The OAM node holds the active cluster configuration and is responsible for disseminating the cluster configuration to the SBC nodes within the cluster. Although the nodes register with the EMS, the SBC nodes within the VNF get their configuration updates only from the OAM node.

Refer to SBC SWe Configuration Management Using OAM Nodes.


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.

Refer to SBC SWe Configuration Management in Direct Single Mode.