Request System - CLI

Load the specified node-locked license file stored in the SBC 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:

• 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: Ribbon recommends backing up current encrypted parameters in plaintext, if possible. Ribbon 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).

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 SBC SWe.

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

Use this control to securely erase all persistent CSPs from the system. The SBC server reboots after confirmation.

adManualSync 
 

<serverName>

The unique name of the server.

Use this command to force the termination of a fixed set of application processes with accompanying core dumps for troubleshooting purposes. By default, a full dump is performed if no option is specified.

Before the command executes, the user is prompted to confirm or cancel the operation. If canceled, no further action is taken, and application operation is not affected.

• coreDumpType– Choose an option below:
  • full (default) – Full set of processes to dump (see Table 2 below).
  • partial – Partial set of processes to dump (see Table 3 below).

Use this object to remove the specified coredump from the chosen server.

• coredumpFileName <filename> – The name of the coredump file.

Use this control to start a software upgrade on the specified server.

• integrityCheck – Use this flag to specify whether or not to perform an integrity check (signature validation) against SBC software updates and patches as they are uploaded to the SBCsystem.
  • perform (default)
  • skip 
• package – Name of the new package.
• rpmName – Name of the rpm/package, if different from the file name of the .tar.gz.
• versionCheck– Use this flag to perform/skip version checking during software upgrades.
  • perform (default)
  • skip

CamProcess

ChmProcess

CpxAppProc

DiamProcess

DnsProcess

DsProcess

EmaProcess

EnmProcessMain

FmMasterProcess

IkeProcess

ImProcess

IpmProcess

PathchkProcess

PesProcess

PipeProcess

PrsProcess

RtmProcess

SamProcess

ScmProcess_0

ScmProcess_1

ScmProcess_2

ScmProcess_3

ScpaProcess

SmProcess

SsaProcess

SsreqProcess

Process

PrsProcess

RtmProcess

SamProcess

ScmProcess_0

ScmProcess_1

ScmProcess_2

ScmProcess_3

SmProcess