In this section:

Related articles:

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. Refer to SBC SWe Configuration Management for an overview of these models. 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.


Note

When you deploy OAM as a 1:1 system, changes made on the Active node are replicated to the Standby for data redundancy. To ensure data consistency, if the OAM Standby is not available, changes are not permitted on the OAM Active.

If configuration changes are required on SBC nodes while the Standby is not available, you can make changes locally on the SBC nodes; however, these changes are temporary and get overwritten when, for example, the SBC reboots and re-syncs with the OAM node.


Note

The "loadConfig", "saveConfig", and "Backup/Restore" operations are not supported on SBC SWe cloud platforms. 

To revert an SBC SWe cloud platform back to a previous configuration, use the following pages instead:

To make configuration changes on an SBC SWe cluster, you can either access the SBC Configuration Manager GUI from the Insight EMS, or use the CLI. The following procedures apply for SBC SWe clusters in either OAM configuration mode or Direct Single configuration mode.

Configuring a Cluster using the SBC Configuration Manager

The following procedure describes how to access the SBC Configuration Manager GUI from the EMS to make configuration changes on an SBC SWe cluster.

  1. Log on to the EMS.

  2. Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters created on the EMS.

    EMS Cluster/VNF List

  3. Click the radio button adjacent to the name of the cluster you want to configure. The Details tab for the selected cluster opens by default. 

  4. Click the Configurations tab. 

    Cluster Configurations Tab



  5. Click Edit Configuration. The SBC Configuration Manager opens in a separate window where you can make configuration changes. Depending on the SBC cluster configuration mode, the SBC Configuration Manager opens against the cluster's active OAM node or the active SBC node, as appropriate. See the EMA User Guide for information on using the GUI to configure the SBC. 

    SBC Configuration Manager Window

  6. Once you have completed making configuration changes, click Apply Saved Changes and Close at the top-right of the SBC Configuration Manager window. When prompted, confirm that you want to save and activate your configuration changes.

    The SBC Configuration Manager window closes. For clusters in OAM configuration mode, the OAM node notifies the SBC nodes of the configuration change and saves the updated configuration and change list back to the EMS. For clusters in Direct Single configuration mode, the active SBC node replicates configuration changes to the standby node, if one is present, and saves the updated configuration back to the EMS. For both types of clusters, the list of configuration revisions found on the Configuration History tab is updated to include the new configuration revision. 

Note

Alternatively, you can log directly into EMA on the active OAM node to configure the cluster using the EMA GUI. Refer to Logging Into EMA for details. The OAM node still notifies the SBC nodes of the configuration change and saves the updated configuration and change list back to the EMS.

Configuring a Cluster using the SBC CLI

The following procedure describes how to use the SBC CLI to make configuration changes on an SBC SWe cluster.

  1. For clusters in OAM configuration mode, log into the command line of the active OAM node. 

    For clusters in Direct Single configuration mode, log into the command line of the active SBC node. Refer to Logging Into the CLI for more information.

    If you are unsure of the IP address of the active node, access the EMS Cluster Management/View Node Status window to check the current role assignments using the path: Network > Cluster Management > View Node Status

    EMS Cluster Management/View Node Status Window

  2. Refer to the CLI Reference Guide for information on using the CLI to configure the SBC.
  3. After you complete and commit your configuration changes, issue the following command to save and activate the changes on the cluster:
    request system admin <system name> saveAndActivate
    where <system name> is the system name for the deployment.
    The saveAndActivate command is available in both system-level and configure modes of the SBC CLI.

For clusters in OAM configuration mode, the OAM node notifies the SBC nodes of the configuration change and saves the updated configuration and change list back to the EMS. For clusters in Direct Single configuration mode, the active SBC node replicates configuration changes to the standby node, if one is present, and saves the updated configuration back to the EMS.

Tip

To determine the system name to use with the saveAndActivate command, issue the command: show status system admin ?
The system name appears under the heading "Possible completions"