You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
The Admin object allows you to configure the system administration related parameters in the
Unable to show "metadata-from": No such page "_space_variables"
. You can configure audit log state, system location, IP version used, and other parameters.
To View Admin
On the
Unable to show "metadata-from": No such page "_space_variables"
main screen, go to
All >
System >
Admin.
The Admin window is displayed.
To Edit Admin
To edit any of the Admin in the list, click the radio button next to the specific Admin name.
All - System - Admin Highlighted
The Edit Selected Admin window is displayed.
All - System - Admin Edit Window
The following fields are displayed:
All - System - Admin parameters
Parameter | Description |
---|
Name
| Specifies the name of the Unable to show "metadata-from": No such page "_space_variables" 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 | This parameter specifies whether the instances are managed either manually, or through EMS/VNFM. Two modes for managing the HA/Redundancy of Unable to show "metadata-from": No such page "_space_variables" SWe Cloud NFV are supported:Centralized (default) - Use this mode for traditional HA/redundancy model (1:1 scenario) where one active instance is backed up by one standby instance. In Centralized mode, the Unable to show "metadata-from": No such page "_space_variables" configuration is synchronized between active and standby Unable to show "metadata-from": No such page "_space_variables" s. The Centralized mode is preferred for deployments where the scale/sessions requirements are low.Distributed - Use this mode for Unable to show "metadata-from": No such page "_space_variables" SWe Cloud deployments where up to N active Unable to show "metadata-from": No such page "_space_variables" 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 are not synchronized. The instances in such deployments also have homogeneous configuration. The microservices based Distributed-Unable to show "metadata-from": No such page "_space_variables" deployment is ideal for Communications Service Providers (CSPs) with large scale/sessions requirements. The Distributed mode is preferred in such deployments, as the lifecycle of the instances (instance spin-off, initial configuration, delta configuration, and instance termination) are managed by the EMS/VNFM and Configurator.
|
Cluster ID | An unique alpha-numeric string for identifying the cluster to which the instance belongs. |
Location
| Specifies the physical location of the Unable to show "metadata-from": No such page "_space_variables" system. |
Contact
| Specifies the contact information of the Unable to show "metadata-from": No such page "_space_variables" system. |
Local Authentication Enabled
| Specifies the confd CLI user information stored locally can be used for authentication. |
External Authentication Enabled
| Specifies the confd CLI user information stored on remote Radius Server 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 EMS PM data collection intervals for the Unable to show "metadata-from": No such page "_space_variables" to be both: - Equal to or greater than the
Unable to show "metadata-from": No such page "_space_variables" interval size, and - Not less than the
Unable to show "metadata-from": No such page "_space_variables" interval size multiplied by the Unable to show "metadata-from": No such page "_space_variables" number of intervals.
See Insight User Guide for configuration details. |
Util Monitors Stats Num of Past Interval
| Specifies the number of past intervals 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 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 slot, 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 as lot 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 automatically triggers a graceful dry-up in an attempt to align DSP hardware capabilities. Once dry-up completes, the Active Unable to show "metadata-from": No such page "_space_variables" 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 completes. Preserve Capacity : The Active Unable to show "metadata-from": No such page "_space_variables" 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 Active are not protected during switchover (i.e. partial redundancy). |
Cli Set Warning Support
| Specifies whether to enable warning prompts configured for the Set commands or not. The options are: Disabled Enabled (default)
|
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. |
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
Admin Commands
Specifies all the admin commands used and its purpose.
All - System - Admin Commands
The following options are displayed:
Admin Commands parameters
Parameter | Description |
---|
Delete Config Store File | Delete a configuration file on an external cloud object store service. |
Re Generate Ssh Rsa Keys | Specifies that it causes regeneration of all SSH keys. |
Re Key Confd Encryption Key
| Specifies that it causes encryption keys used by the system configuration database to be regenerated. 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
| Remove the saved configuration from the system. File Name – Specify filename of configuration to remove from the system.
|
Retrieve Config Store File | Retrieve a configuration file from an external cloud object store service to the active configuration. |
Save Config Store File | Save the current configuration to an external cloud object store service. |
Set Config Store Parameters | Set the parameters used to access an external cloud object store service. |
Restart | This command restarts a server/CE. |
Set Ha Config | Use this action command to configure the Unable to show "metadata-from": No such page "_space_variables" for Geographical Redundancy High Availability (GRHA) mode when active and standby servers are located in two different data centers to protect Unable to show "metadata-from": No such page "_space_variables" s against data center and network failures. To configure/change just one setting, use 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: |
Soft Reset | 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. |
Verify Database Integrity | Use this command to verify that the Unable to show "metadata-from": No such page "_space_variables" 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.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 Unable to show "metadata-from": No such page "_space_variables" server reboots after confirmation. |