Modifying SBC Cluster Configuration

To make configuration changes on an SBC SWe cluster, you can either access the SBC Configuration Manager GUI from RAMP, or use the SBC 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

Go to the RAMP pages to create and/or configure SBC Clusters from the SBC Configuration Manager. 

• Create SBC Clusters
• Manage Clusters

Configuring a Cluster using the SBC CLI

Use the following procedure 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 CLI for more information.
   
   If you are unsure of the IP address of the active node, access the RAMP Cluster Management/View Node Status window to check the current role assignments using the path: Network > Cluster Management > View Node Status
   

   
   
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 RAMP. 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 RAMP.