Page History

adManualSync 

discardCandidateConfiguration

Use to discard candidate configuration changes that have been committed on the OAM node, but not yet activated on the managed SBC nodes with the saveAndActivate command. This command also restarts the OAM nodes, although it does not impact the managed SBC nodes. Applies only to SBC SWe cluster deployments operating in OAM configuration mode.

Load the specified node-locked license file stored in the

• bundleName <license bundle name> – The bundle name to use for the license installation.
• fileName <license filename> – The name of the license file to install.

References:

• Show Table System
• Node-Locked Licensing

loadConfig

Load saved configuration and restart the system without rebooting the servers.

• allowOldVersion – This option is only intended for use to override checks for older releases which do not identify their version. In this case, the follow error results. Follow the instructions given:
  
  "There is no version identifier on the saved file. Use the allowOldVersion parameter only if you are sure the version of the saved configuration file is compatible with the running software version."
  
  • no
  • yes

• filename – Enter the configuration file to load.

NOTE: In a redundant system, using loadConfig restarts both CEs

NOTE: If "reason Configuration file version not compatible with current software version. matrixFileNotAvailable" error is returned, the lswuMatrixSBX5000.bin/lswuMatrixSBX5000.txt file is missing from the/opt/sonus directory. You must must restore these files from the release package of the currently running software with the name pattern of "sbc-V0X.YY.ZZRQQQ.x86_64.tar.gz". Unzip and untar the current release's tar.gz file in that directory, return to the CLI and perform the command again.

Use this command to re-enable an OS account for a specific user.

• userName <user name> - User name of account to re-enable.

Use this control to regenerate system configuration database encryption keys.

NOTE:

removeSavedConfig

Remove the saved configuration from the system.

• fileName – Specify filename of configuration to remove from the system.

restart

Restart system (all CEs).

restoreRevision

Use this command along with a specific, prior configuration revision number to revert to that configuration. The OAM nodes and the SBC nodes automatically restart when you restore a prior configuration.  

• revision <revision number>

saveConfig

Save the current configuration.

• fileNameSuffix – Use this parameter to specify the filename suffix to use when saving the configuration.

Use this action command to configure SBC for Geographical Redundancy High Availability (GRHA) mode when active and standby servers are located in two different data centers to protect SBCs against data center and network failures. To configure/change just one setting, use currentValue option for the other setting.

• bondMonitoring – Select the bond monitoring type for GRHA mode.
  • currentValue 
  • direct-connect
  • network-connect
• leaderElection – Select the leader election algorithm type to use for GRHA mode.
  • currentValue 
  • enhanced
  • standard

References:

• Refer to SBC Core Redundancy for feature details.
• Refer to Show Table System or Show Status System for statistics details
• Refer to Enabling Geographical Redundancy HA Mode best practice for configuration details.

NOTE: Bond monitoring is not applicable to the

softReset

Restart the applications on the system without rebooting the server(s).

switchover

Perform a switchover of the management applications and restart all applications on currently active server.

Use this command to verify that the

• activeAndStandbyPolicy – Check if policy databases on the active and standby servers are in sync.
• activeConfigAndActivePolicy – Check if the policy and configuration databases on the active server are in sync.
• all – Perform both of the above checks.

To view the results of the above checks, use the 'show table system databaseIntegrity' command. Refer to Show Table System for details.

viewConfigurationChanges

The behavior of this request command depends on whether you provide an optional revision number. Applies only to SBC SWe cluster deployments operating in OAM configuration mode.

Issue this request command without specifying a revision number to list the candidate configuration changes that have been committed on the OAM node, but not yet activated on the managed SBC nodes with the saveAndActivate command.

Specify a revision number to list the configuration changes associated with the specified revision.

• revision <revision number>

If the revision number refers to a configuration that was part of restore operation, no changes are shown.

Note that viewing of configuration related to lawful intercept (LI) is restricted to authorized users and therefore output is filtered accordingly. LI-related changes are not present in the output shown to users that lack LI privileges. Similarly, users with only LI privileges can see only LI-related configuration changes.


Use this control to securely erase all persistent CSPs from the system. The