Panel |
---|
borderColor | green |
---|
bgColor | transparent |
---|
borderWidth | 2 |
---|
|
Additional sections: |
...
...
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.
Caption |
---|
0 | Figure |
---|
1 | All - System - Admin |
---|
|
...
|
Image Modified |
To Edit Admin Settings
To edit
...
...
settings, click the radio button next to the
...
...
Caption |
---|
0 | Figure |
---|
1 | All - System - Admin Highlighted |
---|
|
|
Image Removed
The Edit Selected Admin window is displayed
...
...
Edit Selected Admin Window |
|
...
Image Added |
...
...
Use the following table to edit the settings as needed, then click Save.
...
...
...
Parameter | Description |
---|
Name | Specifies the name of the system. | Actual System Name | Indicates the system name assigned by the user. Note: If a system name is not assigned, this field displays the |
|
...
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 configuration is synchronized between active and standby s.
- Distributed - Is supported in SWe Cloud deployments where up to N active 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 initial configuration and delta configuration is managed by the EMS.
| Cluster ID | An unique alpha-numeric string for identifying the cluster to which the instance belongs. | Location | Specifies the physical location of the |
|
...
system. | Contact | Specifies the contact information |
|
...
for the system. | Local Authentication Enabled | Specifies |
|
...
that Confd CLI user information stored locally can be used for authentication. Options are: | External Authentication Enabled | Specifies |
|
...
that Confd CLI user information stored on a remote Radius Server can be used for authentication. Options are: | Default Account Local Only | Specifies whether the default admin user must be locally authenticated. Options are: The option can only be set to True when the options that enable/disable local authentication on the SBC generally, Local Authentication Enabled and External Authentication Enabled, are also set to True. If both local and external (RADIUS) authentication are enabled on the SBC then the method for authentication of the default admin user is governed by this option. | 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 EMS PM data collection intervals for the |
|
...
...
- the interval size, and
- Not less than the
|
|
...
- interval size multiplied by the
|
|
...
| Util Monitors Stats Num of Past Interval | Specifies the number of past intervals |
|
...
of the system resource monitoring statisticsto save. | 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 one of the following DSP |
|
...
mismatch conditions: - 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.
- 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
|
|
...
...
- 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. |
|
...
...
- active 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). | 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 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: |
|
...
...
| Ssh Public Key Authentication Enabled | If set to True and the SSH keys are populated, SSH users can log into their servers without the need to enter their passwords. | Ssh Max Auth Tries | Specifies the maximum number of times SSH users can attempt authentication before an account is locked. The valid range is 2 to 6. The default value is 6. |
|
Admin Commands
...
...
Admin commands to perform system administration actions such as restart and regenerating SSH encryption keys. A partial list of the commands appears in the following figure.
...
Image Removed
The following options are displayed:
...
Image Added |
Select one of the commands and click Select. A pop-up window opens where you can specify any required command options and initiate the selected command. Some commands are only available in cloud-based deployments.
The commands are:
Include Page |
---|
| GRHA_not_in_SWe_Cloud |
---|
| GRHA_not_in_SWe_Cloud |
---|
|
...
|
Parameter | Description |
---|
Delete Config Store File | Use to delete a configuration file on an external cloud object store service. | Re Generate Ssh Rsa Keys |
|
...
Use this command to regenerate all SSH keys. | Re Key Confd Encryption Key |
|
...
Use this command to trigger encryption keys used by the system configuration database to be regenerated. Note: Sonus recommends backing up current encrypted parameters in |
|
...
plain text, 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. In the pop-up window, specify the following: 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. | Reset Software Upgrade State | Use this command to reset the selected system's software upgrade state and clean up all the previous upgrade files. Select one of the following options in the pop-up window: - Forced - continue reset even in the middle of software upgrade.
- Normal (default) - do not continue reset if in the middle of software upgrade.
Warning: This command should only be run when directed by Ribbon Technical Support. | Remove Saved Config | Use this command to remove a saved configuration file |
|
...
...
- File Name – Specify filename of configuration to remove from the system.
|
|
...
Retrieve Config Store File | Use this command to retrieve a configuration file from an external cloud object store service to the active configuration. | Save Config Store File | Use this command to save the current configuration to an external cloud object store service. | Set Config Store Parameters | Use this command to set the parameters used to access an external cloud object store service. | Restart | Use this command to restart |
|
...
a server/CE. | Set Ha Config | Use this |
|
...
...
the for Geographical Redundancy High Availability (GRHA) mode when active and standby servers are located in two different data centers to protect |
|
...
s against data center and network failures. To configure/change just one setting, use |
|
...
the Current Value option for the other setting. |
|
...
Note |
---|
GRHA mode is only applicable to the platforms. |
In the pop-up window, specify the following: |
|
...
- Select the bond monitoring type for GRHA mode.
|
|
...
...
...
...
- Leader Election – Select the leader election algorithm type to use for GRHA mode.
|
|
...
...
...
...
...
...
Use this command to restart the applications on the system without rebooting the server(s). | Switchover |
|
...
Use 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 |
|
...
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.
| Zeroize Persistent Keys | Use this control to securely erase all persistent CSPs from the system. |
|
...
The server reboots after confirmation. |
|