In this section:
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.
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
Go to the
Use the following procedure to use the SBC CLI to make configuration changes on an SBC SWe cluster.
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
request system admin <system name> saveAndActivate
<system name>
is the system name for the deployment.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
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"