System - Admin

Specifies the name of the SBC system.

Identifies the high-availability (HA) mode for the system.

• haMode1to1 - Is the traditional HA/redundancy model (1:1 scenario) where one active instance is backed up by one standby instance. In 1:1 HA mode mode, the SBC configuration is synchronized between active and standby SBCs.
• haModeNto1 - Is supported in SBC SWe cluster deployments where up to N active SBC instances are backed up by a single standby instance (N:1). In this mode, a 1:1 HA pair of dedicated Operations, Administration, and Maintenance (OAM) nodes is deployed to configure and manage SBC nodes. The SBC instances in such deployments have homogeneous configuration. The active OAM node holds the active configuration for the cluster and is responsible for sharing this configuration with the SBC nodes in the cluster.

Specifies the unique alpha-numeric string for identifying the cluster to which the instance belongs as specified in userdata (applies only to SWe N:1 HA and cloud-based systems that are deployed as clusters that register with RAMP).

A user-editable field to specify the physical location of the SBC system.

A user-editable field to specify contact information for the SBC system.

Specifies the external authentication type. 

• Ldap
• Radius (default)
• Tacacs Plus

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 you use RAMP in your network, configure RAMP 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.

Refer to Ribbon Application Management Platform Documentation for configuration details.

Specifies the action to take for one of the following DSP mismatch conditions:

1. Mismatch in DSP card installation across any/all slot locations: Cards must match by slot location. For any mismatched slots, DSP capacity is not used when Preserve Redundancy is configured (and card dried up if calls were already in place when the mismatch occurred), or 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 instance automatically triggers a graceful dry-up in an attempt to align DSP hardware capabilities. Once the dry-up completes, the active SBC uses 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 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 instance are not protected during switchover (that is, partial redundancy).

Enable to swap the System Name for the Server Name of traps and stats that only have a System Name (and no Server Name).

• Disabled (default)
• Enabled

Use this command to trigger encryption keys used by the system configuration database to be regenerated.

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

Use to save and activate cluster configuration. This parameter applies only to SBC SWe clusters operating in OAM or Direct Single configuration mode.

• Saves the configuration to RAMP.
• Activates the configuration on the managed VMs if the cluster is using OAM configuration mode.

Use this 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. In the pop-up window, specify the following:

• 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:

• Refer to 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.

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 run these commands repeatedly on the system. In the pop-up window, specify the following:

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

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