Parameter | Description |
|---|
adManualSync
| This is a request to sync with AD Server to fetch subscriber data. This is an optional parameter. |
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. |
license loadLicenseFile | Load the specified node-locked license file stored in the directory /opt/sonus/external. 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: |
loadConfig
| Load saved configuration and restart the system without rebooting the servers. 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. |
reenableOSaccount | Use this command to re-enable an OS account for a specific user. userName <user name> - User name of account to re-enable.
|
reGenerateSshRsaKeys | Use this control to regenerate all SSH keys. |
reKeyConfdEncryptionKeys | Use this control to regenerate system configuration database encryption keys. NOTE: recommends backing up current encrypted parameters in plaintext, if possible. further recommends performing a full configuration backup immediately after this activity has successfully completed. |
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. |
saveAndActivate | Save and activate cluster configuration. Applies only to SBC SWe clusters operating in OAM or Direct Single configuration mode. Saves the configuration to EMS. Activates the configuration on the managed VMs, if a cluster is using OAM configuration mode. Refer to Modifying SBC Cluster Configuration. |
saveConfig
| Save the current configuration. fileNameSuffix – Use this parameter to specify the filename suffix to use when saving the configuration.
|
setHaConfig | 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-connectnetwork-connect
leaderElection – Select the leader election algorithm type to use for GRHA mode.currentValue enhancedstandard
References: 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. |
verifyDatabaseIntegrity | Use this command to verify that the policy and configuration databases on the active server are in sync and that the policy databases on the active and standby servers are in sync. Because these commands take a few seconds to execute, it is not advisable to constantly run these commands on systems. 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.
|
zeroizePersistenKeys | Use this control to securely erase all persistent CSPs from the system. The server reboots after confirmation. |
searchAdData | Searches the local AD database |
adAttributeIdentifier | AD Attribute Identifier |
searchString | A request to Search String |