Skip to end of metadata
Go to start of metadata



Use the Admin window to configure system administration-related parameters that apply to the SBC system as a whole. 

To View Admin Settings

On the SBC main screen, go to All > System > Admin.

The Admin window is displayed.

Figure : All - System - Admin


To Edit Admin Settings

To edit the Admin settings, click the radio button next to the system name. The Edit Selected Admin window is displayed.

Figure : All - System - Admin Edit Window


Use the following table to edit the settings as needed, then click Save.

Table : Admin Parameters




Specifies the name of the SBC system.

Actual System Name

Indicates the system name assigned by user.

Note: If a system name is not assigned, this field displays the default system name.

Mgmt Mode

Availability: Since 6.2.1

Identifies whether the instances are managed manually or through the EMS.

For SBC SWe cloud deployments, two modes are supported:

  • Centralized (default) - Is the traditional HA/redundancy model (1:1 scenario) where one active instance is backed up by one standby instance. In Centralized mode, the SBC configuration is synchronized between active and standby SBCs.
  • Distributed - Is supported in SBC SWe Cloud deployments where up to N active SBC instances are backed up by a single standby instance (N:1). In this mode, each node is configured separately, and the configuration on active and standby instances is not synchronized. The instances in such deployments also have homogeneous configuration. In Distributed mode the lifecycle of the instances (instance spin-off, initial configuration,  delta configuration, and instance termination) is managed by the EMS and Configurator.
Cluster IDIdentifies the unique alpha-numeric string for identifying the cluster to which the instance belongs.


Specifies the physical location of the SBC system.


Specifies the contact information for the SBC system.

Local Authentication Enabled

Specifies whether user information stored locally can be used for authentication.

External Authentication Enabled

Specifies whether user information stored on a remote RADIUS server can be used for authentication.

Util Monitor Stats Interval

Specifies the time interval for system resource monitoring statistics. The value ranges from 5 to 60 minutes and the default value is 15 minutes.


If using the EMS in your network, configure the EMS PM data collection intervals for the SBC to be both:

  • Equal to or greater than the SBC interval size, and
  • Not less than the SBC interval size multiplied by the SBC number of intervals.

See the Insight User Guide for configuration details.

Util Monitors Stats Num of Past Interval

Specifies the number of past intervals of data that is saved by the system resource monitoring statistics.

Audit Log State

Specifies the state of the management audit log. The options are:

  • Disabled
  • Enabled (default)

Dsp Mismatch Action

Specifies the action to take for when the following DSP mismatch conditions occur:

  1. Mismatch in DSP card installation across any/all slot locations: Cards must match by slot location. For any mismatched slot, the DSP capacity is not used when Preserve Redundancy is configured (and calls on the card dry up if calls were already in place when the mismatch occurred), or the card is left unprotected when Preserve Capacity is configured.
  2. Mismatch in DSP card type within a slot location: Card installations must match by type – DSP25 (higher capacity) or DSP20 (lower capacity). Same rules as above apply.

The options are:

  • Preserve Redundancy (default): The active node automatically triggers a graceful dry-up in an attempt to align the DSP hardware capabilities. Once the dry-up process completes, the active node SBC uses the protected, matching DSP capacity to preserve redundancy.

Note: During the dry-up period, active calls using the higher capacity DSPs are not protected in the event that a switchover occurs before the dry-up process completes.

  • Preserve Capacity: The Active SBC continues to use the extra DSP capacity, as needed, assuming appropriate session licenses are in place; partial redundancy is in effect.

Note: If a switchover occurs, calls using the higher capacity DSPs on the active are not protected during switchover (partial redundancy).

Cli Set Warning Support

Specifies whether or not to enable warning prompts configured for the Set commands. The options are:

  • Disabled
  • Enabled (default)
Verify Auto Index

Availability: Since 6.2.2

Set this value to True to specify that the SBC should check before it adds a new entry to a configuration table that has an Auto Index column to that the newly assigned Auto Index value does not already exist in that table. The transaction fails if the configuration database (CDB) already uses that Auto Index number. Provisioning can be slow when this check is enabled since the CDB is queried for each item that uses an Auto Index number. Therefore this option should only be set to True when directed by Technical Support. The options are:

  • False (default)
  • True
SSH Public Key Authentication Enabled

If set to True and the SSH keys are populated, SSH users can log into the server without the need to enter their passwords.

  • False (default)
  • True

Admin Commands

Use the Commands drop-down list to perform administrative actions.

Figure : All - System - Admin Commands


The following options are displayed:


Geographical Redundancy High Availability (GRHA) is not supported on SBC SWe Cloud.

Table : Admin Commands parameters



Delete Config Store FileUse this command to delete a configuration file on an external cloud object store service.
Re Generate Ssh Rsa KeysUse this command to regenerate all SSH keys.

Re Key Confd Encryption Key

Use this command to regenerate encryption keys used by the system configuration database.

Note: Sonus recommends backing up current encrypted parameters in plaintext, if possible.  Sonus further recommends performing a full configuration backup immediately after this activity has successfully completed.

Reenable OS Account

Use this command as an admin user of a system (hardware server/SWe Cloud instance) to re-enable an OS account for a specific user. The CLI equivalent of this action command is request system admin <system name> reenableOsAccount userName <user name>.

For more information, refer to the Configure Accounts sub-section of the page Users and Application Management - Application Management.

Remove Instance From Group

Use this command to remove an instance from a Redundancy Group.

Note: This action command is applicable only for SBC SWe Cloud deployments.

Remove Saved Config

Use this command to remove a saved configuration file from the system.

  • File Name Specify filename of configuration to remove from the system.
Retrieve Config Store FileUse this command to retrieve a configuration file from an external cloud object store service as the active configuration.
Save Config Store FileUse this command to save the current configuration to an external cloud object store service.
Set Config Store ParametersUse this command to set the parameters used to access an external cloud object store service.
RestartUse this command to restart the server/CE.
Set Ha Config

Use this action command to configure the 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 the Current Value option for the other setting.

  • Bond Monitoring – Select the bond monitoring type for GRHA mode.
    • Current Value 
    • Direct-connect
    • Network-connect
  • Leader Election – Select the leader election algorithm type to use for GRHA mode.
    • Current Value 
    • Enhanced
    • Standard

Refer to the following pages:

Soft ResetUse this command to restart the applications on the system without rebooting the server(s).
SwitchoverUse this command to perform a switchover of the management applications and restart all applications on currently active server.
Verify Database Integrity

Use this command to verify that the SBC policy and configuration databases on the active server are in sync or that the policy databases on the active and standby servers are in sync. Because these commands take a few seconds to execute, do not run these commands repeatedly.

  • Active And Standby Policy – Check if policy databases on the active and standby servers are in sync.
  • Active Config And Active Policy – Check if the policy and configuration databases on the active server are in sync.
  • All – Perform both of the above checks.

Zeroize Persistent Keys

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