Parameter | Description |
---|
Name | 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 | 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 ID | Identifies the unique alpha-numeric string for identifying the cluster to which the instance belongs. |
Location | Specifies the physical location of the SBC system. |
Contact | 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. Note: 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: - 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.
- 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 | 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 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: |
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. |