Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-117541
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}



Multiexcerpt include
MultiExcerptNameOAM 1:1 restriction
PageWithExcerptSBC SWe Configuration Management Using OAM Nodes

Include Page
_SWe_unsupported_Backup/Restore_loadConfig/saveConfig
_SWe_unsupported_Backup/Restore_loadConfig/saveConfig

To make configuration changes on an SBC SWe cluster, you can either access the SBC Configuration Manager GUI from

Spacevars
0model3
, 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

Spacevars
0model3
pages to create and/or configure SBC Clusters from the SBC Configuration Manager. 


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

    Spacevars
    0model3
    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

Spacevars
0model3
. 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
Spacevars
0model3
.

Tip
titleTip

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"