CloudEngine 9800, 8800, and 6800 V300R024C00 Command Reference
Configuration File Management Configuration Commands
- abort
- abort trial
- apply-command-group
- clear configuration candidate
- clear configuration commit label
- clear configuration commit oldest
- collect diagnostic information(user view)
- command group
- commit (All views except the user view)
- commit label
- compare configuration
- configuration check local-user disable
- configuration checkpoint auto-save disable
- configuration current backup-to-file
- configuration current backup-to-server monthly
- configuration exclusive
- configuration exclusive by-user-name
- configuration exclusive timeout
- configuration file auto-save
- configuration file auto-save backup-to-server
- configuration re-authentication enable
- configuration save-policy interrupt-allowed
- display command-group applied
- display configuration apply-command-group fail-result
- display configuration candidate
- display configuration candidate (All views except the user view)
- display configuration changes
- display configuration commit
- display configuration commit list
- display configuration exclusive by-user-name
- display configuration exclusive user
- display configuration recover-result
- display configuration replace failed
- display configuration replace file
- display configuration rollback result
- display configuration sessions
- display configuration trial status
- display current-configuration (All views)
- display current-configuration inheritance
- display saved-configuration configuration
- display saved-configuration time
- display this inheritance
- end-group
- load configuration replace
- refresh configuration candidate
- reset default-configuration
- reset saved-configuration
- rollback configuration
- save
- set configuration appdata auto-check enable
- set configuration commit
- set configuration operation cpu-limit
- set save-configuration checkpoint daily
- startup default-configuration
- startup
abort
Function
The abort command gives up existing configurations and exits the configuration template view.
abort trial
Parameters
| Parameter | Description | Value |
|---|---|---|
| session session-id |
Specifies the ID of a session for which the trial running of the configuration is to be disabled. |
The value is an integer ranging from 0 to 65535. |
| persist persistId |
Specifies a persistence ID for a configuration trial run. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII characters excluding spaces. If double quotation marks are used around the tag name, spaces are allowed in the tag name. The value cannot start with a digit and cannot be a hyphen (-). |
Usage Guidelines
Usage Scenario
In two-phase validation mode, you can run the commit trial command to enable configuration trial run after a configuration command is configured. You can also specify the time parameter in the commit trial command to set the timeout period of the trial run. After the trial run times out, the system configuration is automatically rolled back to the state before the trial run. Before the trial run times out, you can run the abort trial command to stop the trial run and roll back the system configuration to the state before the trial run. You can also specify the session parameter in the abort trial command to specify a session to end the trial run initiated by the session. You can specify the persistId parameter to end the persistent configuration trial run.
Prerequisites
The commit trial command has been run for a configuration.
Configuration Impact
After the trial running of the configuration is disabled, the system configuration rolls back to the configuration state before the trial running.
Precautions
The abort trial command must be run in the two-phase configuration validation mode.
Example
<HUAWEI> system-view [~HUAWEI] sysname rollback [*HUAWEI] commit trial 120 Committing..done. Info: The system enters the trial configuration mode. The system will revert to previous configuration if the trial configuration is not confirmed in 120 seconds. [*rollback] abort trial Warning: The trial configuration will be rolled back. Continue? [Y/N]:y
<HUAWEI> system-view [~HUAWEI] sysname hello [*HUAWEI] commit trial Info: The system enters the trial configuration mode. The system will revert to previous configuration if the trial configuration is not confirmed in 600 seconds. [~hello] abort trial session ? 392 Session in trial configuration mode [~hello] abort trial session 392 Warning: The trial configuration will be rolled back. Continue? [Y/N]:Y Info: The trial configuration rollback succeeded. [~HUAWEI]
<HUAWEI> system-view [~HUAWEI] sysname hello [*HUAWEI] commit trial persist abcid Info: The system enters the trial configuration mode. The system will revert to previous configuration if the trial configuration is not confirmed in 600 seconds. [~hello] abort trial persist abcid Warning: The trial configuration will be rolled back. Continue? [Y/N]:Y Info: The trial configuration rollback succeeded. [~HUAWEI]
apply-command-group
Function
The apply-command-group command applies configurations in a specified configuration template in a specified view.
The undo apply-command-group command cancels the application of the configuration template.
By default, configurations in a configuration template are not applied.
Parameters
| Parameter | Description | Value |
|---|---|---|
| group-name |
Specifies the name of a configuration template. |
The value is a string of 1 to 32 case-insensitive characters. The name contains English letters, digits, hyphens (-), and underscores (_). The name must start with a letter and cannot contain special characters or blank space. |
Usage Guidelines
Usage Scenario
After creating a configuration template, you can run this command to apply the configurations in the configuration template.
- If this command is run in a specified service view, the device delivers the configurations only to the specified service view instance.
- Multiple configuration templates can be applied to the same service view instance.
- Multiple configuration templates can be applied at the same time.
- The configurations in the configuration template cannot be applied to the null interface view.
Prerequisites
Configuration templates have been configured using the command group command.
Precautions
Configuration priority:
- The priority of the user configuration is higher than that of the configuration template. The priority of the configuration template is higher than that of the default configuration. When the template configuration takes effect due to user configuration changes, a message is displayed on the CLI. This message is not displayed on non-CLIs.
- A configuration template in an existing view takes precedence over that in a parent view.
- If multiple configuration templates are applied in the same view, the priorities of the configuration templates depend on the sequence in which templates are applied using the apply-command-group command. The configuration template that is applied first has a higher priority than the configuration template that is applied later.
- The configuration template mechanism does not support the check of dependency between configurations.
- When a template is applied or modified, configurations within the template, configurations between templates, and non-template configurations may fail due to the dependency sequence of command lines.
- When the configuration changes, if the service association configuration changes between the configurations in the template, between templates, and non-template configurations, the template configuration that has taken effect may not meet the expectation.
- If the message "Warning: Some commands execute failed. Please use 'display configuration apply-command-group fail-result' to check the result." is displayed after you run the command, run the corresponding command as prompted to check whether the configuration meets the expectation.
Example
<HUAWEI> system-view [~HUAWEI] command group g1 [~HUAWEI-group-g1] end-group Warning: The configuration in the view of the current group will be committed. Are you sure you want to continue? [Y/N]:y [~HUAWEI] interface LoopBack 2 [*HUAWEI-LoopBack2] commit [~HUAWEI-LoopBack2] apply-command-group g1 Warning: The template configurations will be applied to the matched view. Are you sure you want to continue? [Y/N]:y
clear configuration candidate
Usage Guidelines
Usage Scenario
To clear a configuration that has not been committed in the two-phase configuration validation mode, you can run the clear configuration candidate command.
Prerequisites
A configuration is edited in two-phase configuration validation mode.
Configuration Impact
The uncommitted configuration will be deleted, and the system view will be displayed.
clear configuration commit label
Function
The clear configuration commit label command deletes a configuration rollback point with a specified user label.
Parameters
| Parameter | Description | Value |
|---|---|---|
| label-name |
Specifies a user label for a configuration rollback point. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII character except for the space. However, the string can contain spaces if it is enclosed with double quotation marks (" "). The string cannot start with a digit or be a hyphen (-). The value of this parameter must be an existing configuration rollback point on the device. Otherwise, the command cannot be executed. |
Usage Guidelines
Usage Scenario
To delete a useless configuration rollback point with a specified label, run the clear configuration commit command. The system can generate a maximum of 20 configuration rollback points with a specified label, 10 scheduled configuration rollback points, and 1 historical scheduled configuration rollback point. If a configuration rollback point is no longer used, run this command to delete the configuration rollback point to reduce the amount of information cached in the system.
Precautions
After a configuration rollback point is deleted, system configurations cannot be rolled back to what they were at this configuration rollback point by running rollback commands.
Run the display configuration commit list and display configuration changes commands to display information about the configuration rollback point. Checking the command output helps prevent misoperations.clear configuration commit oldest
Function
The clear configuration commit oldest command deletes the earliest generated list of configuration rollback points.
Parameters
| Parameter | Description | Value |
|---|---|---|
| number-of-commits |
Specifies the number of configuration rollback points to be deleted in the earliest generated list. |
The value is an integer ranging from 1 to 80. |
Usage Guidelines
Usage Scenario
- If the earliest configuration rollback points are no longer required, run the clear configuration commit oldest command to delete one or more of the earliest configuration rollback points. The configuration helps reclaim system resources.
- This command is not used to reduce the number of configuration rollback points in the earliest generated list under normal circumstances. If the number of configuration rollback points reaches the upper limit (80) in a list and subsequent configuration rollback points are generated, the earliest configuration rollback points are deleted automatically.
- When you run this command to delete a configuration rollback point with a label, only the commit point is deleted, but the label is not deleted. The configuration point can be managed only by label, and the commit point has been cleared. After this operation is complete, the configuration rollback points with labels become discontinuous configuration rollback points. When you run the display configuration commit list command to view the configuration rollback points, the commit IDs of the discontinuous configuration rollback points are marked with asterisks (*).
Follow-up Procedure
Run the display configuration commit list command to check that the earliest configuration rollback points have been deleted.
Precautions
After a configuration rollback point is deleted, system configurations cannot be rolled back to what they were at this configuration rollback point by running rollback commands.
Run the display configuration commit list and display configuration changes commands to display information about the configuration rollback point. Checking the command output helps prevent misoperations.collect diagnostic information(user view)
Parameters
| Parameter | Description | Value |
|---|---|---|
| slot slot-id |
Specifies a slot ID. |
The value is a string of 1 to 31 case-sensitive characters. It cannot contain spaces. |
Usage Guidelines
Usage Scenario
You can run this command to save the system log information to the current log directory.
When a fault occurs in the system, you can run this command and locate the fault based on the saved log information.Precautions
If another user is collecting the information at the same time, the current user needs to try again later. Logs whose file name length exceeds 64 characters are not collected. If the diagnostic_information directory exists in the user operation directory, the diagnostic_information directory will be deleted after this command is executed.
command group
Function
The command group command creates a configuration template and displays the configuration template view.
The undo command group command deletes a specified configuration template.
By default, no configuration template is created.
Parameters
| Parameter | Description | Value |
|---|---|---|
| group-name |
Specifies the name of a configuration template. |
The value is a string of 1 to 32 case-insensitive characters, including letters, digits, hyphens (-), and underscores (_). It must start with a letter and cannot contain special characters. Spaces are not supported. |
Usage Guidelines
Usage Scenario
- Configurations in different views may be repeated. In this case, you can create a configuration template, add configurations to the configuration template, and apply the configuration template in the corresponding view to simplify the configuration.
- After creating a configuration template, you need to enter the corresponding service view to configure the template. The service view instance supports regular expressions, and the regular expressions of instance parameters must be included in angle brackets (<>).
Precautions
- This command is a one-phase command and takes effect immediately after being delivered.
- If a configuration template is being applied, it cannot be deleted.
- After entering the configuration template view, run the end-group or abort command to exit the configuration template view.
- If an IPv4 or IPv6 address contains redundant 0s, the command cannot be delivered. For example, if the IPv4 address is 1.1.1.01 and the IPv6 address is 2001:db8:1::01, an error is reported.
Example
<HUAWEI> system-view [~HUAWEI] command group g1 [~HUAWEI-group-g1] interface <Loopback[1-9]$> [~HUAWEI-group-g1-<Loopback[1-9] $>]igmp static-group 10.1.1.1 [~HUAWEI-group-g1-<Loopback[1-9] $>]quit [~HUAWEI-group-g1] end-group Warning: The configuration in the view of the current group will be committed. Are you sure you want to continue? [Y/N]:y [~HUAWEI]
commit (All views except the user view)
Parameters
| Parameter | Description | Value |
|---|---|---|
| trial time |
Specifies the timeout period for the trial running of a configuration. |
The value is an integer ranging from 60 to 65535, in seconds. The default value is 600 seconds. |
| label label |
Specifies a user label for a configuration rollback point. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII character except for the space. However, the string can contain spaces if it is enclosed with double quotation marks (" "). The string cannot start with a digit or be a hyphen (-). |
| persist persistId |
Specifies a persistence ID for a configuration trial run. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII characters excluding spaces. If double quotation marks are used around the tag name, spaces are allowed in the tag name. |
| description description |
Specifies information about a configuration rollback point. |
The value is a string of 1 to 60 case-sensitive ASCII characters, spaces supported. |
Usage Guidelines
Usage Scenario
- To add a description for the committed configuration to provide guidance and help for subsequent configuration rollback, run the commit description command in two-phase validation mode. You can run the display configuration commit list verbose command to view the generated description.
- You can use the trial keyword to configure the trial run function. This function enables a trial run of new functions and services on the live network to improve network reliability. The time parameter specifies the timeout period of the trial run. During the trial run, you can run the commit command to make the configuration in trial running state take effect. When the trial run time exceeds the specified timeout period, the system automatically rolls back the configuration in the trial running state and restores the system to the status before the configuration. If you want the configuration in the trial run state to take effect, reconfigure the configuration and commit it. During the trial run, you can run the commit trial command to refresh the trial run time.
- If you are not sure about the configuration impact or want to observe the configuration effect after the configuration, you are advised to run the commit trial command. After confirming that the configuration has achieved the expected effect, reconfigure and commit the configuration to ensure operation security on the live network.
- If persistId is specified during the configuration trial run, the persistent trial run does not terminate when the session ends. You can run the commit persist \ command to confirm the configuration of persistent trial running.
- In two-phase validation mode, if a user has uncommitted configurations, the configurations are marked with asterisks (*) in the corresponding view. If all configurations have been committed, ~ is displayed in the corresponding view except the user view.
Prerequisites
The system view for the two-phase configuration validation mode has been displayed using the system-view command, and the configuration has been modified.
Configuration Impact
After the commit command is run, the changes in system configurations take effect. The changes include only configuration changes committed after the two-phase configuration validation mode is configured.
Precautions
- Trial run of configurations applies to the two-phase configuration validation mode only.
- After the commit trial command is executed to configure the trial run function, only the current trial running user can modify configurations. Other users cannot modify configurations during the trial run.
- When multiple users commit configurations at the same time, some users may fail to commit configurations due to configuration locking.
Example
<HUAWEI> system-view [~HUAWEI] sysname ROLLBACK [*HUAWEI] commit description This is a new name [~ROLLBACK] display configuration commit list verbose 1) CommitId: 1000000114 Label: - User: Huawei User-Intf: VTY 0 Type: CLI TimeStamp: 2012-07-03 20:20:40 Description: This is a new name 2) CommitId: 1000000113 Label: - User: root User-Intf: VTY 0 Type: CLI TimeStamp: 2012-06-30 15:17:09 Description: 3) CommitId: 1000000112 Label: - User: SNMP_User User-Intf: Type: SNMP TimeStamp: 2012-06-30 15:16:56 Description:
<HUAWEI> system-view [~HUAWEI] sysname DeviceA [*HUAWEI] commit trial persist abcid Info: The system enters the trial configuration mode. The system will revert to previous configuration if the trial configuration is not confirmed in 600 seconds. [~DeviceA]
<HUAWEI> system-view [~HUAWEI] sysname ROLLBACK [*HUAWEI] commit trial 120 Info: The system enters the trial configuration mode. The system will revert to previous configuration if the trial configuration is not confirmed in 120 seconds. [~ROLLBACK]
<HUAWEI> system-view [~HUAWEI] sysname HUAWEIA [*HUAWEI] commit label a123 [~HUAWEI]
commit label
Parameters
| Parameter | Description | Value |
|---|---|---|
| label |
Specifies a user label for a configuration rollback point. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII character except for the space. However, the string can contain spaces if it is enclosed with double quotation marks (" "). The string cannot start with a digit or be a hyphen (-). |
| description description |
Specifies information about a configuration rollback point. |
The value is a string of 1 to 60 case-sensitive ASCII characters, spaces supported. |
Usage Guidelines
Usage Scenario
To add a description for the committed configuration, run the commit label description command. The description provides guidance and help for configuration rollback. All the generated description information can be viewed using the display configuration commit list verbose command.
compare configuration
Function
The compare configuration command compares whether the current configurations are identical with the next startup configuration file or the specified configuration file.
Parameters
| Parameter | Description | Value |
|---|---|---|
| configuration-file |
Indicates the name of the configuration file to be compared with the current configurations. If this parameter is not specified, the next startup configuration file is compared with the current configurations by default. |
The value is a string of 5 to 64 characters without spaces. |
Usage Guidelines
Usage Scenario
After a series of operations are performed, you can run the compare configuration command to compare whether the current configurations are identical with the next startup or a specified configuration file from the first line. The command output helps decide whether to save and set the current configurations as the next startup configuration file.
The command output respectively displays nine lines of the current configurations and the next startup or a specified configuration file from the line that contains differences. If the lines from the differences to the end of the configuration file are less than nine, the command displays the content till the end of the configuration file.Precautions
The filename extension of the configuration file must be .cfg or .zip.
After this command is run once, only the first difference between the two configuration files is displayed. To compare all differences, modify the difference recognized to be the same and run the compare configuration command repeatedly.Example
<HUAWEI> compare configuration
Building configuration...
Warning: The current configuration is not the same as the next startup configuration file. There may be several differences, and the following are some configurations beginning from the first:
====== Current configuration line 13 ======
local-user newuser password irreversible-cipher $1a${EEb6TTv$H$@*AZK.okDUWG"QOxes+;qR)H#,(&8JA{&>6k<>8+$
local-user newuser service-type none
#
authentication-scheme default
#
authorization-scheme default
#
accounting-scheme default
#
====== Configuration file line 15 ======
authentication-scheme default
#
authorization-scheme default
#
accounting-scheme default
#
domain default
configuration check local-user disable
Function
The configuration check local-user disable command disables local user configuration check.
The undo configuration check local-user disable command enables local user configuration check.
By default, local user configuration check is enabled.
Usage Guidelines
- When you run the startup command to configure the configuration file for next startup, if the configuration file does not contain the configuration check local-user disable command, the system checks whether the configuration file contains local user configurations (such as the local login user name and password).
- If the specified configuration file does not contain local user configurations, the startup command fails to be delivered, and the configuration file for next startup fails to be configured.
- If the specified configuration file contains local user configurations, the startup command is successfully delivered, and the configuration file for next startup is successfully configured.
- When you run the startup command to configure the configuration file for next startup, if the configuration file contains the configuration check local-user disable command, the system does not check whether the configuration file contains local user configurations.
configuration checkpoint auto-save disable
Function
The configuration checkpoint auto-save disable command disables a device from automatically generating a configuration rollback point.
The undo configuration checkpoint auto-save disable command enables a device to automatically generate a configuration rollback point.
By default, a device is enabled to automatically generate a configuration rollback point.
Usage Guidelines
Usage Scenario
After configurations are committed on a device, the device automatically generates a configuration rollback point and allocates an ID to identify the rollback point. If you find that configurations are incorrect or a fault caused by configurations affects network running, you can roll the configurations back to a specified configuration rollback point in batches.
If you run the configuration checkpoint auto-save disable command and then the commit command, no configuration rollback point is automatically generated. However, if you run the undo configuration checkpoint auto-save disable command and then the commit command, a configuration rollback point is automatically generated.configuration current backup-to-file
Function
The configuration current backup-to-file command enables and sets the configuration for periodically backing up the configuration file. If interval and from are not specified, the system uses the default values. The default start time of the periodic backup is 05:00, and the default interval is one day.
The undo configuration current backup-to-file command disables the function of periodically backing up the configuration file.
By default, the period backup function is disabled.
Format
configuration current backup-to-file [ interval interval-time | from time ] *
undo configuration current backup-to-file
Parameters
| Parameter | Description | Value |
|---|---|---|
| interval interval-time |
Interval for periodic backup. |
The value is an integer ranging from 1 to 7, in days. |
| from time |
Start time of periodic backup. |
The value is time format, ranging from 00:00 to 23:59. |
Usage Guidelines
Usage Scenario
This function is disabled by default. After this function is enabled, if a configuration error occurs, you can use the local historical backup configuration file to roll back the configuration. The backup configuration file is automatically saved to the $_autobackup directory in the flash memory. The file name contains the time when the configuration file is saved. The default file name extension is .zip.
configuration current backup-to-server monthly
Function
The configuration current backup-to-server monthly command enables the function to upload a configuration file to the server on a specific date and time every month.
The undo configuration current backup-to-server monthly command disables this function.
By default, the function to upload a configuration file to the server on a specific date and time every month is disabled.
Format
configuration current backup-to-server monthly date date-value [ time time-value ]
undo configuration current backup-to-server monthly
Parameters
| Parameter | Description | Value |
|---|---|---|
| time time-value |
Specifies a time point. |
The value is expressed in the format of HH:MM:SS, where HH:MM:SS indicates a second-specific time point. HH ranges from 0 to 23, and MM and SS both range from 0 to 59. The default value is 00:00:00. |
| date date-value |
Specifies a date. |
The value is an integer ranging from 1 to 31. |
configuration exclusive
Function
The configuration exclusive command enables the configuration locking function that allows only one user to configure the system. During this period, all other users can only query configurations.
The undo configuration exclusive command disables the configuration locking function.
By default, the configuration locking function is disabled.
Usage Guidelines
Usage Scenario
The current device allows multiple users to log in and perform configurations. However, if multiple users who have logged in to the device concurrently perform configurations, configuration conflicts may occur, causing service exceptions. If a user needs to exclusively perform configurations, you can run the configuration exclusive command to lock the system configuration. You can run the display configuration exclusive user command to query information about the user who locks the configuration set.
Prerequisites
The configuration locking function is disabled for all users.
Configuration Impact
- After the configuration exclusive command is run, the current configuration data of the system is locked. In this case, the current user can perform and commit configurations, and other users can view, edit, maintain, or save configurations, but cannot commit configurations. You can run the display configuration exclusive user command to query the information about the user who locks the configuration set.
- After the undo configuration exclusive command is run, the current configuration data in the system is unlocked, and all users can perform configurations and commit configurations. Only the user who locks the configuration can unlock the configuration in the session where the lock command is executed. Other users and sessions cannot unlock the configuration.
- If no configuration update is triggered within the maximum interval allowed by the device when no configuration is delivered, the system automatically unlocks the configuration. The maximum interval when no configuration is delivered can be set using the configuration exclusive timeout command.
Precautions
Only one user can lock the configuration at a time. After the user logs out, the configuration is unlocked automatically.
configuration exclusive by-user-name
Function
The configuration exclusive by-user-name command configures a user who is allowed to modify configurations to lock system configurations.
The undo configuration exclusive by-user-name command configures a user who is allowed to modify configurations to unlock system configurations.
By default, the system configuration is not locked.
Format
configuration exclusive by-user-name user-name
undo configuration exclusive by-user-name user-name
Parameters
| Parameter | Description | Value |
|---|---|---|
| user-name |
Specifies the name of a user. |
The name is a string of 1 to 253 characters. |
Usage Guidelines
Usage Scenario
Multiple users can access a device and manage it. A user can be a controller or another type of user. If the configuration of a forwarder is modified by a non-controller user, the configurations of the controller and forwarder may be inconsistent. The configuration exclusive by-user-name command can be used to specify the controller to lock the system configuration of a forwarder to avoid the inconsistency.
When multiple users manage a device at the same time, you can specify a user to lock the device. Only this user can modify the device configuration, while others cannot.Configuration Impact
After the system configuration is locked by a user, only this user can perform configuration operations. Other users can view, edit, maintain, and save the configuration but cannot commit the configuration. If another user needs to commit the configuration, run the undo configuration exclusive by-user-name user-name command to unlock the configuration first.
When this command is run, ensure that the user-name value is that specified when the configuration exclusive by-user-name command is run.
Precautions
- Only one user can lock the system configuration at a time.
- The user that runs this command to lock the system configuration must be the same as the user-name in the configuration exclusive by-user-name user-name command.
- Only users of the management user level can lock and unlock the system configuration.
- The configuration exclusive by-user-name command locks the device configuration based on the user name. Only the same user name can be used to unlock the device configuration. After the user is logged out, the device configuration will not be unlocked automatically. The configuration exclusive command locks the device configuration based on the session. The device configuration can be unlocked only by the current session. After the session is logged out, the device configuration is unlocked automatically.
configuration exclusive timeout
Function
The configuration exclusive timeout command sets the timeout period before the system automatically unlocks the configuration set.
The undo configuration exclusive timeout command restores the default timeout period.
By default, the timeout period is 30 seconds.
Parameters
| Parameter | Description | Value |
|---|---|---|
| timeout-value |
Specifies the timeout period before the system automatically unlocks the configuration set. |
The value is an integer ranging from 1 to 7200, in seconds. |
Usage Guidelines
Running the configuration exclusive timeout command can set an allowable maximum period when no commands are delivered by the user that locks the configuration set. After the timeout period expires, the configuration set is automatically unlocked and other users can normally run commands.
configuration file auto-save
Function
The configuration file auto-save command configures the function of saving system configurations periodically.
The undo configuration file auto-save command cancels the function of saving system configurations periodically.
By default, scheduled saving of configurations is disabled.
Format
configuration file auto-save [ interval interval | delay delay-interval | cpu-limit cpu-usage ] *
configuration file auto-save { interval | delay | cpu-limit } default
undo configuration file auto-save
Parameters
| Parameter | Description | Value |
|---|---|---|
| interval interval |
Specifies the interval at which configurations are saved automatically. |
The value is an integer ranging from 30 to 43200, in minutes. The default value is 30. |
| delay delay-interval |
Specifies the delay time for backing up a configuration automatically after the configuration is changed. |
The value is an integer ranging from 1 to 60, in minutes. The default value is 5. |
| cpu-limit cpu-usage |
Specifies the maximum CPU usage. |
The value is an integer ranging from 1 to 100. The default value is 50. |
| default |
Restores the default values for the parameters of the automatic save function. |
- |
Usage Guidelines
Usage Scenario
If the configuration file auto-save command is not executed, the system does not enable the function of automatically saving configurations. After the function of periodically saving configurations is enabled, if the configurations or configuration file is changed, the system saves the configurations. Otherwise, the system does not save the configurations. If the system is configured to periodically save the configuration file to the server, the configuration file is also uploaded to the server.
To specify an interval at which configurations are saved, set the interval parameter.- cpu-limit: specifies the upper limit of the CPU usage when the system automatically saves the configurations. In this way, when the automatic configuration saving timer is triggered and the CPU usage of the device is detected to be higher than the upper threshold, the device will stop the current automatic configuration saving operation. By default, the upper threshold for CPU usage is 50% for the automatic configuration saving function.
- delay: The system waits a specified delay when configurations change before automatically saving configurations.
- If interval and delay are specified, the configuration saving operation is triggered by the parameter whose configuration time arrives first. When the configuration time of the other parameter arrives, the system checks the configuration again. If no change is found, the system does not save the configuration. If you run the undo configuration file auto-save command, the automatic configuration saving function is disabled. The configuration file auto-save { interval | delay | cpu-limit } default command restores the default values for the parameters of the automatic configuration saving function.
Configuration Impact
After the autosave function is configured, the system automatically saves configurations to the configuration file used for the next startup when the current running configuration is different from the next startup configuration file and the interval configured in the interval parameter expires, no matter whether the save operation has been manually saved.
Follow-up Procedure
Run the display saved-configuration configuration command, and view configuration information about the function of saving configurations periodically.
Precautions
In the following situations, the system cancels the scheduled configuration saving operation:
- The configuration file is being written.
- The device is being restored.
- The CPU usage exceeds the preset threshold.
When the configuration file for next startup is specified, automatic saving is disabled and the disabling duration is 30 minutes.
When the configuration is changed or the configuration file for next startup is specified, the configuration sequence number is changed and the configuration is automatically saved to the configuration file for next startup. When the automatic saving function is disabled, the configuration file auto-save delay default command cannot be used to enable the automatic saving function.Example
<HUAWEI> system-view [~HUAWEI] configuration file auto-save interval 600 delay 3 cpu-limit 60
<HUAWEI> system-view [~HUAWEI] configuration file auto-save interval 60
configuration file auto-save backup-to-server
Function
The configuration file auto-save backup-to-server server command configures the system to periodically save the configuration file to an IPv4 server.
The undo configuration file auto-save backup-to-server server command disables the system from periodically saving the configuration file to an IPv4 server.
The configuration file auto-save backup-to-server server ipv6 command configures the system to periodically save the configuration file to an IPv6 server.
The undo configuration file auto-save backup-to-server server ipv6 command disables the system from periodically saving the configuration file to an IPv6 server.
By default, the system does not periodically save configurations to a server.
Format
configuration file auto-save backup-to-server server server-ip [ vpn-instance vpn-instance-name ] transport-type { tftp | { ftp | sftp } [ port port-value ] user user-name password password } [ path folder ]
configuration file auto-save backup-to-server server server-ip [ vpn-instance vpn-instance-name ] transport-type { sftp [ port port-value ] user user-name password }
configuration file auto-save backup-to-server server server-ip [ vpn-instance vpn-instance-name ] path folder
configuration file auto-save backup-to-server server ipv6 server-ip [ vpn-instance vpn-instance-name ] transport-type { tftp | { ftp | sftp } [ port port-value ] user user-name password password } [ path folder ]
configuration file auto-save backup-to-server server ipv6 server-ip [ vpn-instance vpn-instance-name ] path folder
configuration file auto-save backup-to-server server ipv6 server-ip [ vpn-instance vpn-instance-name ] transport-type { sftp [ port port-value ] user user-name password }
undo configuration file auto-save backup-to-server server [ server-ip | server-ip vpn-instance vpn-instance-name | server-ip vpn-instance vpn-instance-name port port-value ]
undo configuration file auto-save backup-to-server server ipv6 [ server-ip | server-ip vpn-instance vpn-instance-name | server-ip vpn-instance vpn-instance-name port port-value ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance vpn-instance-name |
Specifies the name of a VPN instance. |
The value is a string of 1 to 31 case-sensitive characters. If spaces are used, the string must be enclosed in double quotation marks (" "). |
| transport-type |
Indicates the transmission mode. |
The value can be ftp, tftp, or sftp. |
| tftp |
Specifies the transmission mode is TFTP. |
- |
| ftp |
Specifies the transmission mode is FTP. |
- |
| sftp |
Specifies the transmission mode is SFTP. |
- |
| port port-value |
Specifies the port number used to send a configuration file to a server. |
The value is an integer ranging from 1 to 65535. |
| user user-name |
Specifies the name of the user that accesses the server using FTP or SFTP. |
The value is a string of 1 to 64 characters without spaces. Except the question mark (?) and space. However, when quotation marks (") are used around the password, spaces are allowed in the password. |
| password password |
Specifies the password of the user that accesses the server using FTP or SFTP. |
In the case of a password in plaintext, the value is a string of 1 to 255 case-sensitive characters without spaces. In the case of a ciphertext password, the value is a string of 20 to 432 case-sensitive characters without spaces. A 24-character ciphertext password configured in an earlier version is also supported in this version. Except the question mark (?) and space. However, when quotation marks (") are used around the password, spaces are allowed in the password. |
| path folder |
Specifies the path of the configuration file on the server. If this parameter is not configured, the root path of FTP, SFTP, or TFTP services is used by default. |
The value is a string of 1 to 64 case-sensitive characters. |
| server server-ip |
Specifies the IP address of the server to which the system periodically saves the configuration file. |
The IP address is in dotted decimal notation. |
| ipv6 server-ip |
Specifies the IPv6 address of the server to which the system periodically saves the configuration file. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
- To back up the configuration file, you can run this command to specify a server. The configuration file is automatically saved to the specified server, improving database security.
- The format of the configuration file backed up to the server is the same as that of the configuration file for next startup. If the configuration file for next startup is in .dat format, the generated configuration file is in .dat format. If the configuration file for next startup is in .cfg or .zip format, the generated configuration file is in .zip format. The configuration file backed up to the server is named in the format of date, time, and system name. The names of the configuration files backed up at different time are different and do not overwrite the previous backup files.
- You can run this command multiple times to configure multiple file servers.
Prerequisites
The configuration file auto-save command has been run to enable the automatic saving function, and FTP, SFTP, or TFTP has been enabled on the server.
The interval at which configurations are automatically saved depends on the interval configured using the configuration file auto-save command. Alternatively, run the configuration current backup-to-server monthly command to enable the function of monthly backing up configurations to the server. (Note that this function does not save the configuration file for the next startup and only uploads current configurations to the server.)Precautions
- The system supports a maximum of five servers. The servers are independent of each other. If the system fails to save configuration files to a server, the system reports traps to the NMS and records logs.
- When configuration files are being uploaded, the system does not save configurations to a server until the configuration files are uploaded.
- The time of the configuration file generated after this command is run is the UTC.
- After a bound VPN instance is deleted, the VPN configuration specified using the configuration file auto-save backup-to-server command will not be cleared, and the VPNID is restored to the default value. If the VPN instance with the same name as the deleted one is reconfigured, the VPNID will be refreshed.
- A device does not support a server with the same IP address but different VPN instances. To be specific, if multiple VPN instances have been configured for a server with a specific IP address, the device can send configuration files only to one VPN instance. For example, if the configuration file auto-save backup-to-server command is run twice to configure the system to save configuration files to different VPN instances of the same server, only the later configuration takes effect.
- When you run this command to save configuration files to a server, the system supports only the binary transmission mode. Therefore, the server must support the binary transmission mode.
- The configuration file auto-save backup-to-server server [ ipv6 ] server-ip [ vpn-instance vpn-instance-name ] transport-type { sftp [ port port-value ] user user-name password } is supported only in FIPS mode.
- The configuration file auto-save backup-to-server server [ ipv6 ] server-ip [ vpn-instance vpn-instance-name ] path folder command is supported only in FIPS mode.
- The specified path parameter folder can be a relative path or an absolute path. If the value is a relative path, the root path of the relative path is the root path of the FTP, SFTP, or TFTP server.
- The value of port-value must be the same as the port number of the FTP, SFTP, or TFTP server.
Example
<HUAWEI> system-view [~HUAWEI] configuration file auto-save backup-to-server server 10.1.1.1 transport-type ftp port 88 user huawei password YsHsjx_202206
<HUAWEI> system-view [~HUAWEI] configuration file auto-save backup-to-server server 10.1.1.1 transport-type tftp
<HUAWEI> system-view [~HUAWEI] configuration file auto-save backup-to-server server 10.1.1.1 transport-type ftp port 88 user huawei password YsHsjx_202206 path D:/FTP/TEST
configuration re-authentication enable
Function
The configuration re-authentication enable command enables secondary authentication for the execution of risky commands.
The undo configuration re-authentication enable command disables secondary authentication for risky command execution.
By default, secondary authentication is disabled.
Usage Guidelines
Usage Scenario
Misoperations of some commands cause the configurations of related features to be deleted, interrupting services and disconnecting the user network. To prevent misoperations, users need to perform secondary authentication to protect the system when running these commands.
Precautions
- To prevent some services from being unavailable due to misoperations, you are advised to enable secondary authentication for risky commands.
- Secondary authentication for risky commands takes effect only in the command line view.
Example
<HUAWEI> system-view [~HUAWEI] undo configuration re-authentication enable Info: This command is a high-risk command. Enter the login password of the current user again. Enter Password: [*HUAWEI]
<HUAWEI> system-view [~HUAWEI] configuration re-authentication enable
configuration save-policy interrupt-allowed
Function
The configuration save-policy interrupt-allowed command enables configuration saving interruption upon configuration committing and triggers the system to automatically save configurations.
The undo configuration save-policy interrupt-allowed command disables configuration saving interruption upon configuration committing and triggers the system to automatically save configurations.
By default, configuration committing will interrupt configuration saving, and the system is disabled from automatically saving configurations.
Usage Guidelines
Usage Scenario
After the configuration save-policy interrupt-allowed command is configured, if a user delivers configurations during configuration saving, configuration saving will be interrupted and fail, and configuration delivery will succeed. The system automatically saves the configurations five minutes later. If the saving time is too long, the configuration cannot be delivered. You can deliver the configuration that is interrupted before saving the configuration. During the saving process, this command cannot be delivered or take effect.
After the undo configuration save-policy interrupt-allowed command is configured, if a user delivers configurations during configuration saving, configuration saving will not be affected, and configuration delivery will fail.Precautions
- After the configuration saving is interrupted due to configuration committing, the system automatically saves the configurations 5 minutes later. If automatic or manual configuration saving is triggered within 5 minutes, the system does not automatically save the configurations 5 minutes after the interruption of configuration saving.
- The system may fail to save the configurations automatically. If the system restarts, the configurations added after the configurations are saved last time will be lost. Before restarting the device, manually save the configurations to ensure that the configurations are saved successfully.
- When the system automatically saves the configurations, if a user delivers configurations, the configuration saving will be interrupted again. After 5 minutes, the system saves the configurations again.
- The system may fail to automatically save configurations because the system is saving configurations or the disk space is insufficient.
- If you run the startup command to reset the configuration file for the next startup within 5 minutes after the configuration saving is interrupted due to configuration committing, the system does not automatically save the configurations 5 minutes later.
Example
<HUAWEI> system-view [~HUAWEI] undo configuration save-policy interrupt-allowed
<HUAWEI> system-view [~HUAWEI] configuration save-policy interrupt-allowed
display command-group applied
Function
The display command-group applied command displays the number and names of views to which a configuration template is applied.
Parameters
| Parameter | Description | Value |
|---|---|---|
| groupName |
Specifies the name of a configuration template. |
The value is a string of 1 to 32 case-insensitive characters. The name contains English letters, digits, hyphens (-), and underscores (_). The name must start with a letter and cannot contain special characters or blank space. |
Usage Guidelines
Usage Scenario
After the system starts to apply or cancel the application of the configurations in a configuration template, you can run this command to check the number and names of views to which the configuration template is applied.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] command group g1 [~HUAWEI-group-g1] end-group Warning: The configuration in the view of the current group will be committed. Are you sure you want to continue? [Y/N]:y [~HUAWEI] interface LoopBack 2 [*HUAWEI-LoopBack2] commit [~HUAWEI-LoopBack2] apply-command-group g1 Warning: The template configurations will be applied to the current view. Are you sure you want to continue? [Y/N]:y [~HUAWEI-LoopBack2] display command-group g1 applied View Number : 1 View List : interface LoopBack2
| Item | Description |
|---|---|
| View Number | Number of views to which the template is applied. |
| View List | List of views to which the template is applied. The views in braces are subviews. |
display configuration apply-command-group fail-result
Function
The display configuration apply-command-group fail-result command displays the causes of the latest five configuration template application failures.
Usage Guidelines
Usage Scenario
When the system starts to apply or cancel the application of the configurations in the configuration template, or edit the configuration template after applying the configuration template, some configurations may fail to be executed. As a result, the configuration template fails to be applied. You can run this command to view detailed information about the latest five application failures, including the command execution time, service view name, and specific command and template names.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] interface LoopBack 2 [*HUAWEI-LoopBack2] commit [~HUAWEI-LoopBack2] display configuration apply-command-group fail-result --------------------------------------------------------------------------- Time : 2018-03-13 08:35:41 View : Tunnel1 Operation : apply-command-group c Details : View : Tunnel1 Command : + mpls View : Tunnel1 Command : + mpls te --------------------------------------------------------------------------- Time : 2018-03-13 08:32:41 View : Tunnel1 Operation : undo apply-command-group a Details : View : Tunnel1 Command : + mpls View : Tunnel1 Command : + mpls te
| Item | Description |
|---|---|
| Time | Time when the configuration template application command is run. |
| View | View where the command failed to be run. |
| Operation | Operation performed when a template fails to be applied. |
| Details | Details when you apply or cancel the application of a configuration template.View where the command failed to be run. |
| Command | Command failed to be run. |
display configuration candidate
Function
The display configuration candidate command displays commands that have been configured but not submitted.
Usage Guidelines
Usage Scenario
This command can be used to display commands that have been configured but not submitted.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] user-interface vty 0 4 [~HUAWEI-ui-vty0-4] idle-timeout 1 30 [*HUAWEI-ui-vty0-4] display configuration candidate user-interface vty 0 4 idle-timeout 1 30
display configuration candidate (All views except the user view)
Function
The display configuration candidate changes command displays the difference between the candidate configuration and current running configuration.
The display configuration candidate merge command displays all configurations, including uncommitted and committed ones.
Usage Guidelines
Usage Scenario
Before committing configurations, you can run the display configuration candidate changes command to view the difference between the modified configuration and the current running configuration.
The display configuration candidate changes command displays the difference between the uncommitted configuration in the candidate database and the running configuration in the running database. If any difference exists, the command output is as follows:- Commands that exist in the candidate configuration rather than the current running configuration are prefixed with "+".
- Commands that exist in the current running configuration rather than the candidate configuration are prefixed with "-".
- If a command in the current running configuration is modified in the candidate configuration, two commands that are prefixed with "-" and "+", respectively, are displayed in sequence. To check whether the configuration to be committed is correct and whether it conflicts with the existing configurations, you can run the display configuration candidate merge command.
Precautions
This command applies only to the two-phase validation mode.
Before you run the commit command to commit a configuration, a configuration conflict occurs if the current running configuration is changed. In this case, run the refresh configuration candidate command to resolve the configuration conflict, and then run the display configuration candidate changes command to view the configuration difference.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] sftp server enable [*HUAWEI] display configuration candidate merge # sysname HUAWEI # interface 100GE1/0/1 # sftp server enable # user-interface con 0 set authentication password cipher $1d$a3XtEok2LJ$;&(SUt9vy0`JlWP6-z0<=01'5B+8NT8n9'<PL3oM$ history-command max-size 30 user-interface vty 0 4
<HUAWEI> system-view [~HUAWEI] display configuration candidate changes Building configuration # interface Tunnel1 - mtu 1400 + mtu 1300 # + interface Tunnel3 #
| Item | Description |
|---|---|
| Building configuration | Generation of differential configuration. |
| - | Deleted configuration. |
| + | Added configuration. |
display configuration changes
Function
The display configuration changes command displays the difference between a configuration file and the current running configuration file on the device.
The display configuration commit changes command displays configuration changes at specific configuration rollback points.
Format
display configuration commit changes [ at commit-id | since commit-id | last number-of-commits ]
display configuration changes [ running file file-name | file file-name running ]
display configuration changes { running label label | label label running }
display configuration commit changes latest-number-of-commits
Parameters
| Parameter | Description | Value |
|---|---|---|
| at commit-id |
Displays configuration changes at a configuration rollback point. |
The id is a string of 1 to 20 characters and generated by the system automatically. |
| since commit-id |
Displays configuration changes since the specified configuration rollback point was generated. |
The id is a string of 1 to 20 characters and generated by the system automatically. |
| last number-of-commits |
Specifies the number of the latest configuration rollback points. Configuration changes in these rollback points are displayed. |
The value is an integer ranging from 1 to 80. |
| running |
Displays the running configuration, that is, the configuration data in the running/ database. |
- |
| file file-name |
Specifies a configuration file. |
The name is a string of 5 to 64 characters in the format of .zip, .cfg, or .dat. |
| label label |
Specifies a label. |
The value is a string of 1 to 256 characters. |
| latest-number-of-commits |
The number of latest commit changes. |
The value is an integer ranging from 1 to 80. |
Usage Guidelines
Usage Scenario
- If a misoperation is performed or some configurations fail, the system must roll back to a specified historical configuration. In this case, you can run the display configuration commit changes command to check configuration changes at configuration rollback points.
- To view the difference between the current running configuration file and a specified configuration file, run the display configuration changes running file file-name command.
- To view the difference between a specified configuration file and the current running configuration file, run the display configuration changes file file-name running command.
- The display configuration changes running label label command displays the difference between the current configuration and the configuration of a specified user label.
- The display configuration changes label label running command displays the difference between the configuration of a specified user label and the current configuration.
- This command can only compare the current running configuration file with a configuration file. When you run this command, the first specified configuration file is called source configuration, and the later specified configuration file is called target configuration. If the target configuration is different from the source configuration, the difference is displayed based on the following rules:
- A command that exists in the target configuration rather than the source configuration is prefixed with "+".
- A command that exists in the source configuration rather than the target configuration is prefixed with "-".
- If a command is modified in the target configuration, the original command is prefixed with "-" and the new command is prefixed with "+".
- The display configuration commit changes latest-number-of-commits command displays information about the configuration changes of each of the recent configuration rollback points. Assume that the configuration rollback points are 1000000001, 1000000002, and 1000000003. The display configuration commit changes 3 command displays the configuration changes of each of these configuration rollback points 1000000001, 1000000002, and 1000000003.
- The display configuration commit changes last number-of-commits command displays the final differences between the recent configuration rollback points. Assume that the configuration rollback points are 1000000001, 1000000002, and 1000000003. The display configuration commit changes last 3 command displays the configuration changes of the configuration rollback points from 1000000001 to 1000000003.
Precautions
When a configuration difference comparison command is run, if repeated commands exist in the same view, the current command fails to be executed.
The specified configuration file specified by file-name must exist on the device.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration changes running file a.cfg
Building configuration
Warning: The specified configuration file is not the same as the current configuration. There are several differences as follow:
#
- sysname HUAWEI
<HUAWEI> display configuration changes running label a
2021-03-05 11:37:53.415
Building configuration
.
#
- sysname HUAWEI
#
+ sysname HUAWEI-A
#
<HUAWEI> display configuration commit changes last 2 with-tag
Building configuration
#
+ <cmd-script:vlan batch></cmd>vlan batch 1 to 1000
<view-entry></view>aaa
+ domain abc
#
<HUAWEI> display configuration commit changes since 1000000067
Building configuration...
#
- snmp-agent
#
- snmp-agent local-engineid 800007DB0338AB7F111100
#
- snmp-agent community write public mib-view abc
#
- snmp-agent community write private mib-view abc
#
<HUAWEI> display configuration commit changes
Building configuration
Commit changes of commitId 1000000114 2015-06-18 03:04:59
#
- sysname HUAWEI
#
+ sysname test
#
<HUAWEI> display configuration commit changes last 2
Building configuration...
#
- info-center logfile size 16
#
+ info-center logfile size 32
#
<HUAWEI> display configuration commit changes 2
Building configuration
Commit changes of commitId 1000000004 2021-03-29 09:03:52
#
+ acl number 3000
#
Commit changes of commitId 1000000003 2021-03-29 09:03:43
#
+ acl number 2000
#
<HUAWEI> display configuration changes
Warning: The current configuration is not the same as the next startup configuration file. There are several differences as follow:
Building configuration
#
aaa
+ local-user huawei password cipher @%@%ym<*-4`Hu=kF;b-%AiAF&C:1@%@%
+ local-user huawei service-type ftp
<HUAWEI> display configuration changes
Building configuration
Info: The current configuration is the same as the next startup configuration file.
| Item | Description |
|---|---|
| Building configuration | Building configuration. |
| - | Deleted configuration information. For the modified configuration, two records are displayed. One record is marked with "-", indicating that the old configuration is deleted. The other record is marked with "+", indicating that the new configuration is created. |
| + | Added configuration information. For the modified configuration, two records are displayed. One record is marked with "-", indicating that the old configuration is deleted. The other record is marked with "+", indicating that the new configuration is created. |
| Commit changes of commitId | Label of the configuration rollback point, which uniquely identifies the configuration rollback point. |
display configuration commit
Function
The display configuration commit command displays all configurations at a specified configuration rollback point.
The display configuration command displays configurations in a specified configuration file. The configuration file must be stored in the root directory of the MPU.
The display saved-configuration command displays the configuration file used for startup.
Format
display { saved-configuration [ last ] | configuration configuration-file }
display configuration commit at commit-id
Parameters
| Parameter | Description | Value |
|---|---|---|
| saved-configuration |
Displays the setting of the configuration file for the next startup. |
- |
| last |
Displays the system configurations saved last time. |
- |
| configuration |
Display parameter information about the configuration of the autosave function. |
- |
| configuration-file |
Specifies the name of a configuration file. The file must have been created. |
The name is a string of 5 to 64 characters in the format of *.zip, *.cfg or *.dat. |
| at commit-id |
Displays configuration changes at a configuration rollback point. |
The id is a string of 1 to 22 characters and generated by the system automatically. |
Usage Guidelines
Usage Scenario
- After a configuration command is successfully committed to the system, the system automatically generates a configuration rollback point to record the configuration change information and the all system configurations at the point. You can run the display configuration commit command to view all configurations at a specified configuration rollback point. If a fault occurs in the system, you can run the rollback configuration command to roll back the system to the configuration before the fault occurs.
- You can run the save configuration-file command to save the current configuration as a *.cfg, *.zip, or *.dat file. The *.cfg file is a text file and can be viewed by running the more command. The *.zip and *.dat files cannot be viewed by running this command. You can run the display configuration command to view the contents of the preceding three types of configuration files to check whether the configurations are correct.
- If the device does not work properly after being powered on, you can run the display saved-configuration command to check the startup configuration of the device.
- The display saved-configuration last command displays the system configuration saved last time.
- The display saved-configuration time command displays the time when the system automatically saves configurations last time.
Prerequisites
- You can run the display configuration commit list command to view information about configuration rollback points in the system.
- The specified configuration file has been created.
- Before viewing parameter settings of the automatic saving function, run the configuration file auto-save command.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration vrpcfg.cfg
#
info-center loghost source LoopBack0
info-center loghost 10.1.1.1
info-center loghost 10.1.1.2
#
sysname HUAWEI
#
user-interface maximum-vty 15
#
aaa
local-user admin1234 password cipher $1d$k4:o79a_DJ$dkxW!,\@7Cjr*k+Q}gb'{g{x)#wS1GjQST'EZ]/F$
local-user admin1234 service-type ssh
#
sftp server enable
ssh user admin1234
ssh user admin1234 authentication-type dsa
ssh user admin1234 assign dsa-key dsakey001
ssh user admin1234 service-type sftp
ssh user admin1234 sftp-directory flash:/
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
#
user-interface con 0
set authentication password cipher $1d$k4:o79a_DJ$dkxW!,\@7Cjr*k+Q}gb'{g{x)#wS1GjQST'EZ]/F$
history-command max-size 30
#
user-interface vty 0 14
user privilege level 3
idle-timeout 0 0
#
return
<HUAWEI> display saved-configuration
#
info-center loghost source LoopBack0
info-center loghost 10.1.1.1
info-center loghost 10.1.1.2
#
sysname HUAWEI
#
user-interface maximum-vty 15
#
aaa
local-user admin1234 password cipher $1d$k4:o79a_DJ$dkxW!,\@7Cjr*k+Q}gb'{g{x)#wS1GjQST'EZ]/F$
local-user admin1234 service-type ssh
#
sftp server enable
ssh user admin1234
ssh user admin1234 authentication-type dsa
ssh user admin1234 assign dsa-key dsakey001
ssh user admin1234 service-type sftp
ssh user admin1234 sftp-directory flash:/
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
#
user-interface con 0
set authentication password cipher $1d$k4:o79a_DJ$dkxW!,\@7Cjr*k+Q}gb'{g{x)#wS1GjQST'EZ]/F$
history-command max-size 30
#
user-interface vty 0 14
user privilege level 3
idle-timeout 0 0
#
return
<HUAWEI> display configuration commit at 1000000001
#
sysname HUAWEI
#
aaa
#
authentication-scheme default
#
authorization-scheme default
#
accounting-scheme default
#
domain default
#
domain default_admin
#
interface NULL0
#
#
user-interface con 0
#
display configuration commit list
Function
The display configuration commit list command displays the list of configuration rollback points.
Format
display configuration commit list [ number-of-commits ]
display configuration commit list verbose [ number-of-commits ]
display configuration commit list label
display configuration commit list verbose label
Parameters
| Parameter | Description | Value |
|---|---|---|
| number-of-commits |
Specifies the number of configuration rollback points to be displayed in the list of configuration rollback points. |
The value is an integer ranging from 1 to 100 and cannot exceed the total number of generated configuration rollback points on the device. |
| verbose |
Displays detailed information about the configuration rollback point list, including remarks. |
- |
| label |
Displays label of the configuration rollback point list. |
- |
Usage Guidelines
Usage Scenario
After the system configuration is complete, you can run the display configuration commit list command to check the configuration rollback point list.
The system displays configuration rollback points in reverse chronological order. The latest rollback point is displayed on the top.Follow-up Procedure
Identify the labels of rollback points in the list of rollback points so that you can perform future configuration rollbacks according to these labels.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [HUAWEI] sysname ROLLBACK [ROLLBACK] display configuration commit list verbose 1) CommitId: 1000052271 Label: - User: root123 User-Intf: VTY 3 Type: ROLLBACK TimeStamp: 2020-11-26 10:53:13 Description:
| Item | Description |
|---|---|
| CommitId | ID of the configuration rollback point. |
| Label | Label of the configuration rollback point, which uniquely identifies the configuration rollback point. |
| User | User name. |
| TimeStamp | Timestamp of the configuration rollback point. |
| Description | Remarks about a configuration rollback point. You can run the commit label <labelstring> [ description <descriptionstring> ] command to add description for a configuration rollback point. |
| User-Intf | Path type, such as CON1 and VTY1. |
| Type | Terminal type, for example, CLI, SNMP, NETCONF, ROLLBACK, RESTORE and SYSTEM.
|
display configuration exclusive by-user-name
Function
The display configuration exclusive by-user-name command displays lock information of the system configuration locked based on user name.
Usage Guidelines
Usage Scenario
To view system configuration lock information, run the display configuration exclusive by-user-name command. The command output includes the name of a user who locks or unlocks the system configuration, time when the system configuration is locked or unlocked, and lock ID.
If no system configuration is locked, no command output is displayed after the display configuration exclusive by-user-name command is run.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration exclusive by-user-name
Unlock User Name: root1234
Unlock Time: 2018-03-07 20:14:09+04:00 DST
<HUAWEI> display configuration exclusive by-user-name
Lock User Name: root123
Lock Time: 2018-03-07 20:13:31+04:00 DST
Identifier: 13
| Item | Description |
|---|---|
| Unlock User Name | Name of a user who unlocks the system configuration. |
| Unlock Time | Time when the system configuration is unlocked. |
| Lock User Name | Name of a user who locks the system configuration. |
| Lock Time | Time when the system configuration is locked. |
| Identifier | Lock ID, which is unique. |
display configuration exclusive user
Function
The display configuration exclusive user command displays information about the user that locks the configuration set.
Usage Guidelines
You can run the display configuration exclusive user command to query the user that obtains configuration access. If the configuration set is not locked, there is no display.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration exclusive user
User Index: 34
User Session Name: VTY 0
User Name: root
IP Address: 10.135.38.234
Locked Time: 2013-03-06 21:09:36
Last Configuration Time: 2013-03-06 21:09:36
The time out value of configuration right locked is: 30 second(s)
| Item | Description |
|---|---|
| User Index | Index of a user. |
| User Session Name | Session name of a user, ranging from VTY0 to VTY14. |
| User Name | User name of logging. |
| IP Address | IP address of a user, valid for VTY users only. |
| Locked Time | Time when the configuration set is locked. |
| Last Configuration Time | Time when the user runs the last command. |
| The time out value of configuration right locked is | Time when the configuration right is locked. |
display configuration recover-result
Function
The display configuration recover-result command displays information about configuration restoration after the upgrade.
Usage Guidelines
Usage Scenario
- After you run the startup saved-configuration command to specify the configuration file for the next startup and restart the device, run this command to check the configuration recovery result (success, failure, or partial failure) and failure cause.
- A maximum of 1000 records are displayed.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration recover-result
The current startup saved-configuration file is flash:/test.cfg.
The number of failed commands is 1.
Command : nat 1
View : system
Line : 63
Reason : Unknown command
Time : 2021-12-05 13:15:56
| Item | Description |
|---|---|
| The current startup saved-configuration file is | Indicates the configuration file saved during the current startup. |
| The number of failed commands is | Indicates the number of commands that fail to be executed. |
| Command | Command. |
| View | View. |
| Line | Line number. |
| Reason | Indicates the reasons. |
| Time | time. |
display configuration replace failed
Function
The display configuration replace failed command displays information about configuration replacement failures.
Usage Guidelines
Usage Scenario
If configuration replacement fails, run the display configuration replace failed command to view the detailed failure information.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration replace failed
Failed command(s):
Command : - interface a
View : system
Reason : Command not match
Command : + interface b
View : system
Reason : Command not match
| Item | Description |
|---|---|
| Failed command(s) | Information about the configuration replacement failure. |
| Command | Command that fails to be replaced. |
| View | View to which the command that fails to be replaced belongs. |
| Reason | Reason for the configuration replacement failure. |
display configuration replace file
Function
The display configuration replace file command displays the differences between the replacement configuration and the target configuration.
Usage Guidelines
Usage Scenario
After configurations are replaced, run the display configuration replace file command to check the differences between the replacement configuration and the target configuration.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] display configuration replace file # + interface Tunnel1 # + interface Tunnel2 # + interface a # - interface b
| Item | Description |
|---|---|
| + | New configuration. For each modified configuration, both "-" indicating the deleted configuration and "+" indicating the created configuration are displayed. |
| - | Deleted configuration. For each modified configuration, both "-" indicating the deleted configuration and "+" indicating the created configuration are displayed. |
display configuration rollback result
Function
The display configuration rollback result command displays the configurations that fail to be rolled back and the messages displayed when configuration commands are run.
Usage Guidelines
Usage Scenario
During the configuration rollback operation, some configurations may fail to be retrieved, and some configurations trigger the generation of prompt messages. You can run the display configuration rollback result command to view relevant information.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration rollback result !warning information interface 10GE1/0/5 + ipv6 enable Warning: The configuration is successful. Enable global BFD to validate the configuration. !There are still several differences as follow: # interface 10GE1/0/2 - ip address 3.3.3.3 255.255.255.0 + ip address 4.4.4.4 255.255.255.0 #
<HUAWEI> display configuration rollback result
<HUAWEI> display configuration rollback result
!warning information
+ ftp server enable
Warning: FTP is not a secure protocol, it is recommended to use SFTP.
!commit error information
Error: Some labels in the label range were used. Delete unwanted services to release the labels or check for other available label ranges.
!warning information
+ ftp server enable
Warning: FTP is not a secure protocol, it is recommended to use SFTP.
!commit error information
Error: Some labels in the label range were used. Delete unwanted services to release the labels or check for other available label ranges.
!There are still several differences as follow:
+ AAbbcc
#
| Item | Description |
|---|---|
| !warning information | Prompt messages during the configuration rollback operation. |
| + | Added configuration. For each modified configuration, both "-" indicating the deleted configuration and "+" indicating the created configuration are displayed. |
| !There are still several differences as follow: | Information about configurations that fail to be rolled back. |
| - | Deleted configuration. For each modified configuration, both "-" indicating the deleted configuration and "+" indicating the created configuration are displayed. |
display configuration sessions
Parameters
| Parameter | Description | Value |
|---|---|---|
| verbose |
Indicates detailed information about session status. |
- |
Usage Guidelines
Usage Scenario
To query information about users that have logged in to the device, you can run the display configuration sessions command to view session status.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display configuration sessions verbose
--------------------------------------------------------------------------------
Session : 60
User-Intf :
User : _SYSTEM_
Date : 2014-08-21 13:39:06
Lock-Type : -
Cfg-Mode : -
Client : NETCONF
Elapsed-Time : 1 days, 1:27:58
Session : 168 *
User-Intf : CON 1023
User :
Date : 2014-08-22 08:34:48
Lock-Type : -
Cfg-Mode : -
Client : CLI
Elapsed-Time : 0 days, 6:32:16
--------------------------------------------------------------------------------
<HUAWEI> display configuration sessions
--------------------------------------------------------------------------
Session User-Intf User Date Lock
--------------------------------------------------------------------------
108 SNMP_User 2013-02-11 17:24:09 -
158 CON 0 anonymous 2011-01-17 10:39:47 -
177 VTY 0 user 2011-01-17 12:00:11 -
179 VTY 1 user 2011-01-17 12:04:06 -
180 * VTY 2 user 2011-01-17 12:32:02 -
14911 * VTY 0 anonymous 2013-04-19 14:46:09 -
--------------------------------------------------------------------------
| Item | Description |
|---|---|
| Session | Indicates the ID of the session that connects to the system. |
| User-Intf | Indicates the interface information that the user used to logging on. |
| User | User name.
|
| Date | Indicates the time of the logging user. |
| Lock-Type | Indicates the lock type. |
| Cfg-Mode | Indicates the configuration mode. |
| Client | Indicates the client information. |
| Elapsed-Time | Indicates the elapsed time of the logging user. |
| Lock | Indicates the lock status. |
display configuration trial status
Function
The display configuration trial status command displays the trial running status of a system configuration.
Usage Guidelines
Usage Scenario
To view the trial running status of a system configuration, run the display configuration trial status command.
Trial running is initiated by NETCONF. If the trial running packets carry the persistency mark, the trial running status information of a system configuration contains the persistency mark.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] display configuration trial status Trial status: INACTIVE Trial time left (sec): 0
<HUAWEI> system-view [~HUAWEI] display configuration trial status Trial status: ACTIVE Trial time left (sec): 51
<HUAWEI> system-view [~HUAWEI] display configuration trial status Trial status: ACTIVE Persist id: IQ,d4668 Trial time left (sec): 30
| Item | Description |
|---|---|
| Trial status | Trial running status of a system configuration. The value can be:
|
| Trial time left (sec) | Remaining time of a trial run. |
| Persist id | Persistency mark. |
display current-configuration (All views)
Function
The display current-configuration command displays the set parameters that take effect on the device.
Format
display current-configuration [ configuration [ configuration-type [ configuration-instance ] | config-type-no-inst ] | all | inactive ] [ include-default ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| configuration |
Displays the configuration of some specified level-2 features. |
The value must be set according to the device configuration. |
| configuration-type |
Specifies the configuration type. |
The value must be set according to the device configuration. |
| configuration-instance |
Specifies the configuration instance. |
The instance is a string of 1 to 200 characters. |
| config-type-no-inst |
Specifies the configuration module. |
The value must be set according to the device configuration. |
| all |
Specifies all the configuration information. |
- |
| inactive |
Specifies all configurations of the board in the offline state. |
- |
| include-default |
Displays both the configurations that users have performed and default configurations. |
- |
Usage Guidelines
Usage Scenario
- After a set of configurations is complete, you can run the display current-configuration command to check the parameters that take effect. The parameters that do not take effect are not displayed. In addition, the in-use configuration parameters that adopt the default settings are not displayed.
- When the display current-configuration command is executed:
- If include-default is not specified, only configurations that users have performed are displayed.
- If include-default is specified, both default configurations and configurations that users have performed are displayed.
Configuration Impact
You can filter the output using regular expressions in the case of a large amount of configuration information. For usage of regular expressions, see "CLI Overview" in Configuration Guide > Basic Configurations.
Precautions
The following configurations are not displayed in the command output.
- Configurations that are the same as default ones
- Configurations that have not been committed In different view, this command displays the configurations associated with the view.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display current-configuration # sysname HUAWEI # interface 10GE1/0/1 # interface 10GE1/0/2 # user-interface con 0 set authentication password cipher $1d$k4:o79a_DJ$dkxW!,\@7Cjr*k+Q}gb'{g{x)#wS1GjQST'EZ]/F$ history-command max-size 30 #
<HUAWEI> display current-configuration | include user
local-user aaa password irreversible-cipher $1d$wrcoG+up@($z((,He+)x<\Wbv1K"paL#$~(NcTY~J|8kj)=7k:H$
<HUAWEI> display current-configuration | begin user
user-interface con 0
set authentication password cipher $1d$k4:o79a_DJ$dkxW!,\@7Cjr*k+Q}gb'{g{x)#wS1GjQST'EZ]/F$
history-command max-size 30
#
return
<HUAWEI> display current-configuration include-default | include user
local-user aaa password irreversible-cipher $1d$wrcoG+up@($z((,He+)x<\Wbv1K"paL#$~(NcTY~J|8kj)=7k:H$
user-password min-len 6
undo user-password complexity-check
user-password expire 0 prompt 0
undo user-password change
user-block failed-times 5 period 5
user-block reactive 5
<HUAWEI> display current-configuration include-default !Software Version V300R024C00 !Last configuration was updated at 2020-06-01 07:13:54+00:00 # ~language character-set UTF-8 # sysname HUAWEI # ~info-center channel 0 name console ~info-center channel 1 name monitor ~info-center channel 2 name loghost ~info-center channel 3 name trapbuffer
| Item | Description |
|---|---|
| # | The # command can be used to return to the system view from the current view stack. |
display current-configuration inheritance
Function
The display current-configuration inheritance command displays the configurations that contain the current user configuration and that are from a template.
Parameters
| Parameter | Description | Value |
|---|---|---|
| no-comment |
Displays configurations that do not contain comments of commands in the configuration template. |
- |
Usage Guidelines
Usage Scenario
After a group of template configurations are applied, you can run the display current-configuration inheritance command to check user configurations and configurations in the template. The parameters that do not take effect are not displayed. In addition, the in-use configuration parameters that adopt the default settings are not displayed.
Configuration Impact
You can filter the output through the regular expression in the case of a large amount of configuration information. For details about regular expression rules, see Configuration Guide > Basic Configuration > CLI Overview.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display current-configuration inheritance no-comment !Software Version V300R024C00 !Last configuration was updated at 2018-02-24 09:19:01+00:00 # command group g1 interface Loopback1 clear ip df end-group # interface LoopBack1 apply-command-group g1 return
<HUAWEI> display current-configuration inheritance !Software Version V300R024C00 !Last configuration was updated at 2018-02-24 09:19:01+00:00 # command group g1 interface Loopback1 clear ip df end-group # interface LoopBack1 apply-command-group g1 ! ! inherited from group g1 clear ip df # return
display saved-configuration configuration
Function
The display saved-configuration configuration command displays the parameters of the function to automatically save configurations.
Usage Guidelines
Usage Scenario
Run the display saved-configuration configuration command to check the parameters of the function to automatically save configurations, including the automatic save interval and CPU usage.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display saved-configuration configuration
Auto save configuration status : Enable
Auto save configuration interval : 60 minutes
Save delay after configuration changed : 10 minutes
The threshold of the CPU usage permitted when save : 50%(default)
| Item | Description |
|---|---|
| Auto save configuration status | Status of the automatic configuration saving function.
|
| Auto save configuration interval | Interval for auto-save. |
| Save delay after configuration changed | Auto-save delay time after a configuration change. |
| The threshold of the CPU usage permitted when save | Threshold of CPU usage permitted during auto-save. |
display saved-configuration time
Function
The display saved-configuration time command displays the time when configuration information is saved last time.
Usage Guidelines
Usage Scenario
To view the time when the system saves the configuration last time, run the display saved-configuration time command.
- In the command output, "Saved configuration manually:" indicates the time when the configuration is manually saved.
- In the command output, "Saved configuration automatically:" indicates the time when the configuration is automatically saved.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display saved-configuration time
Saved configuration automatically:
15:49:07 DefaultZoneName 2015/06/08
Time Zone: UTC+00:00
| Item | Description |
|---|---|
| Saved configuration automatically | The time information about the configuration of the autosave function. |
| Time Zone | Time zone. |
display this inheritance
Function
The display this inheritance command displays the configurations that contain the current user configuration and that are from a template.
Parameters
| Parameter | Description | Value |
|---|---|---|
| no-comment |
Displays configurations that do not contain comments of commands in the configuration template. |
- |
Usage Guidelines
Usage Scenario
After a set of configurations are complete in a certain view, you can run the display this inheritance command to check whether the configurations are correct.
Configuration Impact
You can filter the output through the regular expression in the case of a large amount of configuration information. For details about regular expression rules, see Configuration Guide > Basic Configuration > CLI Overview.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> system-view [~HUAWEI] interface loopback2 [~HUAWEI-LoopBack2] display this inheritance no-comment # interface LoopBack2 apply-command-group g1 clear ip df #
<HUAWEI> system-view [~HUAWEI] interface loopback2 [~HUAWEI-LoopBack2] display this inheritance # interface LoopBack2 apply-command-group g1 ! ! inherited from group g1 clear ip df #
end-group
Function
The end-group command ends configuration, commits existing configurations in a configuration template, and exits the configuration template view.
By default, the end-group command is not run.
load configuration replace
Function
The load configuration replace command loads the configuration file on a local or remote server to replace the running configuration on the current device.
Format
load configuration file filename replace [ relative ]
load configuration server ip-address [ vpn-instance vpn-instance-name ] transport-type { ftp | sftp } username user-name password password file filename replace [ relative ]
load configuration server ipv6 ipv6-address [ vpn-instance vpn-instance-name ] transport-type { ftp | sftp } username user-name password password file filename replace [ relative ]
load configuration server http url url-address [ vpn-instance vpn-instance-name ] [ file filename ] replace [ relative ]
load configuration server ip-address [ vpn-instance vpn-instance-name ] transport-type sftp file filename replace [ relative ] username user-name password
Parameters
| Parameter | Description | Value |
|---|---|---|
| relative |
Specifies that only configurations in the current view are replaced. |
- |
| server ip-address |
Specifies the IPv4 address of the remote server. |
The value is in dotted decimal notation. |
| vpn-instance vpn-instance-name |
Specifies a VPN instance name. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. In addition, the VPN instance name must not be _public_. When double quotation marks are used around the string, spaces are allowed in the string. |
| transport-type |
Specifies a file transfer mode. |
- |
| ftp |
Transfers files through FTP. |
- |
| sftp |
Transfers files through SFTP. |
- |
| username user-name |
Specifies the user name of a remote server. |
The value is a string of 1 to 64 case-sensitive characters, spaces and question marks not supported. |
| password password |
Specifies the password of a remote server. |
The value is a string of case-sensitive characters, including letters and digits. The string can contain spaces if it is enclosed in double quotation marks ("). A simple password is a string of 1 to 255 characters, while a ciphertext password is a string of 20 to 432 characters. |
| file filename |
Specifies the name of the configuration file to be loaded. |
The value is a string of case-sensitive characters. The value can contain uppercase letters, lowercase letters, digits, and special characters, but cannot contain spaces. The value is a string of 1 to 128 characters (including the suffix). The following special characters are not allowed: ~ ? * / \ : " | < > [ ] ; & $ ` !. The first and last characters cannot be periods (.). The file name extension must be .cfg, .zip, .dat, .bat, .txt, or the text file does not contain the file name extension. In FTP or SFTP mode, the file name can contain the server directory name. The file name cannot contain the following special characters: ~ ? * / \ : " | < > [ ] ; & $ ` !. |
| ipv6 ipv6-address |
Specifies the IPv6 address of a remote server. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
| http |
Specifies access to the remote server by HTTP. |
HTTP and HTTPS can be used. |
| url url-address |
Specifies the URL path of the configuration file on the remote server. |
It is a string data type. The value range is from 1 to 255 characters. |
Usage Guidelines
Usage Scenario
If multiple devices need to share the same source configuration file, to ensure that the configuration data on all the devices is consistent, run one of the following commands as required:
To load a local configuration file and use the configurations in the configuration file to replace the configurations in the running configuration file, run the load configuration file <fileName> replace [ relative ] command.- To load the configuration file on a specified remote IPv4 server and use the configurations in the configuration file to replace the configurations in the running configuration file on the local device, run the load configuration server <ipv4Addr> [ vpn-instance <vpnName> ] transport-type { ftp | sftp } username <usernameVal> password <passwordVal> file <fileName> replace [ relative ] command.
- To load the configuration file on a specified remote IPv6 server and use the configurations in the configuration file to replace the configurations in the running configuration file on the local device, run the load configuration server ipv6 <ipv6Addr> [ vpn-instance <vpnName> ] transport-type { ftp | sftp } username <usernameVal> password <passwordVal> file <fileName> replace [ relative ] command.
- To load a configuration file on the remote server with a specified URL to replace the running configuration on the current device, run the load configuration server http url <urlVal> [ vpn-instance <vpnName> ] [ file <saveFileName> ] replace [ relative ] command. The load configuration replace command can replace all configurations in the running configuration file on the local device or only the configurations in a specified view, depending on the content in the source configuration file to be loaded. To replace only the configurations in a specified view, specify relative in the command.
Follow-up Procedure
After the configuration file is loaded and replaced, the file enters the candidate configuration database. Run the commit command for relevant configurations to take effect.
Precautions
- The configuration file to be loaded must exist and meet the following conditions:
- The configuration file can contain only configuration commands, view switching commands, and #. When other types of commands (such as display query commands, reset/save/ping maintenance commands, quit, commit, return, upgrade-compatible commands, and one-phase commands) are executed, the device reports an error and continues to load subsequent commands.
- The interactive commands in the configuration file support only Y/N interaction.
- The indentation of commands in the configuration file must be correct. The commands in the system view and the level-1 view under the system view must be left-aligned, the commands in the level-1 view must be indented by one space, and the commands in each subsequent view must be indented by one more space.
- If the number sign (#) is left-aligned, the system view is displayed. If the number sign (#) is indented, it is used to isolate command blocks; in this case, the number sign (#) must be aligned with the first command in the following command block. If the number sign (#) is incorrectly used, configurations may be lost, or commands may be run in an unexpected view.
- The configuration file name extension must be .zip, .cfg, .txt, .dat, or .bat, or the file name does not have an extension. In FTP or SFTP mode, the file name can contain a server directory name. It is recommended that the directory name contain a slash (/). A file name does not contain the special characters: ~ ? * / : " | < > [ ].
- Both .cfg and .txt files are text files whose content can be directly viewed. If a .cfg or .txt file is specified as the configuration file to be loaded, the system restores the commands in the file one by one when the configuration file is loaded.
- A .zip file is obtained by compressing a .cfg file, occupying less space. If a .zip file is specified as the configuration file to be loaded, the system decompresses the file into a .cfg file, and then restores the commands in the .cfg file one by one when the configuration file is loaded. The .cfg file must have the same name as the .zip file. Otherwise, the configuration file fails to be loaded.
- A .dat file is a compressed file, which can be in binary or text mode. Only a .dat file exported from a Huawei device is supported, and the file cannot be modified manually. Otherwise, the file fails to be loaded.
- A .bat file is used for batch processing. It is a text file that can be modified manually.
- After the configuration replacement command is executed, pay attention to the replacement result displayed in the prompt message. You can run the commit command only after confirming that the replacement result is correct and meets the expectation. This prevents service functions from being affected after the configurations are committed when only partial configurations are successfully replaced.
- When FTP/STFP is used to load the configuration file on a specified remote server, the remote file is first obtained to the root directory of the device. Ensure that there is sufficient space for storing the file and no file with the same name exists.
- You are not advised to manually construct a configuration file. If the format of the constructed configuration file is incorrect, configuration restoration may fail or an error may occur during configuration restoration.
- This function can be performed only in two-phase validation mode.
- If the command to be replaced depends on some configurations and cannot be delivered separately or deleted using the undo command, the configuration replacement fails.
Example
<HUAWEI> system-view [~HUAWEI] ssl policy policy1 [*HUAWEI-ssl-policy-policy1] certificate load pem-cert client.crt key-pair rsa key-file client.key auth-code cipher YsHsjx_202206 [*HUAWEI-ssl-policy-policy1] signature algorithm-list ecdsa-secp256r1-sha256 ecdsa-secp384r1-sha384 ecdsa-secp521r1-sha512 ed25519 ed448 rsa-pss-pss-sha256 rsa-pss-pss-sha384 rsa-pss-pss-sha512 rsa-pss-rsae-sha256 rsa-pss-rsae-sha384 rsa-pss-rsae-sha512 rsa-pkcs1-sha256 rsa-pkcs1-sha384 rsa-pkcs1-sha512 ecdsa-sha1 ecdsa-sha224 rsa-sha1 rsa-sha224 dsa-sha1 dsa-sha224 dsa-sha256 dsa-sha384 dsa-sha512 [*HUAWEI-ssl-policy-policy1] quit [*HUAWEI] http [*HUAWEI-http] client ssl-policy abc [*HUAWEI-http] quit [*HUAWEI] commit [~HUAWEI] aaa [*HUAWEI-aaa] load configuration server http url https://10.1.1.1/https/config.cfg replace relative
<HUAWEI> system-view [~HUAWEI] load configuration server 10.1.1.1 transport-type sftp username huawei123 password YsHsjx_202206 file config.cfg replace
<HUAWEI> system-view [~HUAWEI] load configuration file config.cfg replace
refresh configuration candidate
Function
The refresh configuration candidate command re-executes candidate configuration to resolve configuration conflicts.
Usage Guidelines
Usage Scenario
If the system displays a message indicating that the current running configuration is changed when you run the display configuration candidate changes command to view the difference between the candidate configuration and current running configuration, run the refresh configuration candidate command to resolve the configuration conflict so that you can continue to view the configuration difference.
If a configuration conflict occurs before you commit the configuration, you can resolve the configuration conflict and then run the commit command to commit the configuration. Alternatively, run the commit command to commit the configuration directly, without resolving the configuration conflict.Precautions
This command applies only to the two-phase validation mode.
reset default-configuration
Usage Guidelines
Usage Scenario
To start a device with empty configuration by discarding the preset configuration file configured using the startup default-configuration command, run the reset default-configuration command to delete the preset configuration file.
Configuration Impact
If the preset configuration file is deleted and no configuration file is specified for next startup, the device does not use the preset configuration file to restore configurations upon next startup. As a result, the plug-and-play function may be affected.
Exercise caution and follow the instructions of the technical support personnel when you run this command.Example
<HUAWEI> reset default-configuration
Warning: The action will delete the default configuration file on the device.
The default configuration file will be cleared to reconfigure.No default configuration file is set for the device. When the device is started without the next startup configuration, the plug-and-play function may be affected.Continue? [Y/N]: y
Info: Succeeded in clearing the configuration on the device.
reset saved-configuration
Function
The reset saved-configuration command clears information about the configuration files on the storage device.
Usage Guidelines
Usage Scenario
After the device software is upgraded, the configuration file in the storage medium may not match the new software version. In this case, you can run the reset saved-configuration command to clear the old configuration file.
If the device in use applies to another scenario and the original configuration file of the device does not meet requirements in the scenario, you can run the reset saved-configuration command to clear the existing configuration file and set a new configuration file.Precautions
- Exercise caution when running this command, and you are advised to follow the instructions of the technical support personnel when you run this command.
- After secondary authentication for risky commands is enabled using the configuration re-authentication enable command, you must enter the login password for secondary authentication before running the reset saved-configuration command.
- When upgrading the system software package of a device, you need to specify the system software package for next startup first. In this case, the device automatically specifies the configuration file for next startup. You can run this command to clear the configuration.
Example
<HUAWEI> reset saved-configuration Warning: The action will delete the saved configuration on the device. The configuration will be erased to reconfigure.Continue? [Y/N]:n <HUAWEI> reset saved-configuration Warning: The action will delete the saved configuration on the device. The configuration will be erased to reconfigure.Continue? [Y/N]:y Warning: Now clearing the configuration on the device. Info: Succeeded in clearing the configuration on the device.
rollback configuration
Function
The rollback configuration command rolls the system configuration back to a preceding configuration.
Format
rollback configuration { to commit-id commit-id | last number-of-commits | to label label | to file file-name }
Parameters
| Parameter | Description | Value |
|---|---|---|
| to |
The system will be rolled back to the configurations when the configuration rollback point is generated. |
- |
| commit-id commit-id |
Specifies the ID of the configuration rollback point to which the system configuration is expected to roll back. |
The value is an integer that is generated automatically and ranging from 1000000001 to 1999999999, the value of periodical configuration rollback point is ranging from 2000000001 to 2999999999. |
| last number-of-commits |
Specifies the number of the last configuration rollback point to which the system rolls back. |
The value is an integer ranging from 1 to 80. |
| label label |
Specifies a user label for a configuration rollback point. A specified user label indicates the historical configuration state to which the system configuration is expected to roll back. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII character except for the space. However, the string can contain spaces if it is enclosed with double quotation marks (" "). The string cannot start with a digit or be a hyphen (-). |
| file file-name |
Rolls back the current configuration to the configuration in the specified configuration file. After the rollback, the configuration on the device is the same as that in the specified configuration file. |
The value is a string of 5 to 64 case-sensitive characters in the format of *.zip, *.cfg, or *.dat, spaces not supported. |
Usage Guidelines
Usage Scenario
When an error occurs or the configuration procedure has an unexpected impact on services, run the rollback configuration command to roll the system configuration back to a specified configuration.
Assume that a user has committed four configurations and four consecutive rollback points (A, B, C, and D) are generated. If an error is found in configurations committed at rollback point B and the system must be rolled back, configuration rollback allows the system to roll back to the configurations at rollback point A. Additionally, configuration rollback point E is generated and specially marked with a Rollback flag, indicating that this point is generated because of configuration rollback. If a configuration rollback error is detected, system configurations can be rolled back to what they were before the configuration rollback operation was performed and the new configuration rollback point is specially marked.Example
<HUAWEI> rollback configuration to label test
Warning: This operation will revert configuration changes to the previous status. During the rollback configuration process, some configurations involving differences may be temporarily invalid. Continue? [Y/N]:y
Checking changes...
Loading rollback changes
Committing
Check rollback result
Configuration rollback succeeded.
Please use 'display configuration commit changes last 1' to view the changes.
<HUAWEI> rollback configuration to file test.cfg
Warning: This operation will revert configuration changes to the file test.cfg. During the rollback configuration process, some configurations involving differences may be temporarily invalid. The time required for this operation depends on the configuration delivery time and configuration difference amount. If the configuration difference amount is large, this operation will take a long time. Continue? [Y/N]:y
Checking changes...
Loading rollback changes
Committing
Check rollback result
Configuration rollback succeeded.
Please use 'display configuration commit changes last 1' to view the changes.
save
Function
The save command saves all configurations to a storage device.
The save shareable-configuration command saves the configuration to a specified file and generates a root key based on the password entered by the user.
Parameters
| Parameter | Description | Value |
|---|---|---|
| configuration-file |
Specifies the name of a configuration file. |
The value is a string of 5 to 64 characters in the format of .zip, .cfg, or .dat. |
| password |
Password for saving a configuration file. |
- |
Usage Guidelines
Usage Scenario
- When a group of configurations are complete and the desired functions are achieved, all the configurations should be saved to the storage device.
- If you run the save [ <configuration-file> ] command without specifying the configuration-file parameter, all configurations are saved to the configuration file for the next startup by default. If no next-startup configuration file exists, the system prompts you to determine whether to save configurations to the vrpcfg.zip file. You can save configurations to the file or specify another file for saving the configurations. Then the specified file is configured as the next-startup configuration file. You can run the display startup command to view the name of the configuration file for next startup.
- The save [ <configuration-file> ] command backs up all configurations to the specified file on the storage device. This command does not affect the current startup configuration file. If the storage path and name of the configuration file specified using configuration-file are the same as those of the next-startup configuration file, the save configuration-file command functions the same as the save command.
- If you run the save [ <configuration-file> ] command without specifying the optional parameter configuration-file when saving the configuration file for the first time, the system asks you whether to save the file as vrpcfg.zip. The vrpcfg.zip file is the default configuration file, and it is empty initially.
- If a configuration-level user runs the save command, the configuration file can be saved only to the root directory.
- The save shareable-configuration command saves configurations to a specified file, generates a root key based on the entered password, and saves the root key to the file.
- The configuration-file parameter must be specified when you run the save shareable-configuration command. If the system has the next startup file, the specified file name cannot be the same as the next startup file name.
- If the password parameter is not specified, the preset password (default value) generated by the device is used. The preset password is generated based on the system master key of the device and cannot be viewed.
Configuration Impact
When you run the save command several times, the latest configuration overrides the previous configuration. If the file of the same name already exists, the contents of the original file are changed.
Running this command causes a temporary high CPU usage, but services are not affected.Precautions
- A configuration file can contain only configuration commands, view switching commands, and # symbols (used to switch to the system view). If you load other types of commands, such as display commands used for query, reset/save/ping commands used for maintenance, quit, return, and upgrade-compatible commands, the device reports an error and continues the loading of follow-up commands.
- Repeated commands cannot coexist in the same view.
- Command lines must be indented correctly. Specifically, a command line in the current view must be indented by one character compared with a command line in the previous view.
- If the pound sign (#) is left-aligned, the system view is displayed. If the pound sign (#) is indented, it is used only to isolate command blocks; in this case, the pound sign (#) must be aligned with the first command in the following command block. If the pound sign (#) is incorrectly used, configurations may be lost, or commands may be run in an unexpected view.
- The configuration for entering a command view must be present. Otherwise, no commands can be executed in the command view.
- The command execution sequence and dependency must be correct.
- Interactive commands in the configuration file only support automatic interaction in Y/N mode, the default is Y.
- The extension of the configuration file name must be .zip, .cfg or .dat. The system configuration file must be saved in the root directory of the storage device.
- A .cfg file is a text file. You can directly view the content of a .cfg file. After a .cfg file is specified as the configuration file, the system restores the commands in the file one by one when startup.
- A .zip file is the compression of a .cfg file, occupying less space. After a .zip file is specified as the configuration file, the system decompresses the file into a .cfg file, and then restores the commands in the file one by one when startup.
- A .dat file is a binary file. If the startup software version and the .dat file version are the same, the system restores all configurations in the .dat file in batches when the device starts. This speeds up the system startup.
- After the weak password dictionary maintenance function is enabled, the passwords (which can be queried using the display security weak-password-dictionary command) defined in the weak password dictionary are unavailable for the command save shareable-configuration.
Example
<HUAWEI> save shareable-configuration test.cfg
Warning: Are you sure to save the configuration to flash:/test.cfg? [Y/N]:y
Info: Save the configuration successfully.
<HUAWEI> save Warning: The current configuration will be written to the device. Continue? [Y/N]:y Now saving the current configuration to the slot 1 ......... Info: Save the configuration successfully.
set configuration appdata auto-check enable
Function
The set configuration appdata auto-check enable command enables the function of automatically checking whether data in the service process database is the same as that in the central database.
The undo set configuration appdata auto-check enable command disables the function of automatically checking whether data in the service process database is the same as that in the central database.
By default, the automatic check function is disabled.
Usage Guidelines
Usage Scenario
Device data is stored in the central database and service process databases. Each service process database needs to synchronize data from the central database. Any data inconsistency between the service databases and the central database may lead to unexpected operation results on hosts. As a result, service functions may be abnormal. To avoid this, you need to enable the automatic database information check function so that the system periodically checks the data consistency between the service databases and central database. If data inconsistency is detected, the device immediately reports an alarm to prompt you to analyze the impact of the inconsistency on services. In this case, you can restart the board or device to rectify the fault.
You can run this command to enable or disable the automatic data check function.set configuration commit
Function
The set configuration commit command sets a user label for a configuration rollback point.
The clear configuration commit command deletes a user label for a configuration rollback point.
By default, no user label is set for configuration commit.
Format
set configuration commit commit-id label label-string
clear configuration commit commit-id label
Parameters
| Parameter | Description | Value |
|---|---|---|
| commit-id |
Specifies the ID of a configuration rollback point. |
The id is a string of 1 to 20 characters and generated by the system automatically. |
| label label-string |
Specifies a user label for a configuration rollback point. The parameter value must be unique in the system and in one-to-one mappings with commit-id. |
The value is a string of 1 to 256 case-sensitive characters. It can be any visible ASCII character except for the space. However, the string can contain spaces if it is enclosed with double quotation marks (" "). The string cannot start with a digit or be a hyphen (-). The user label of the configuration rollback point must be unique in the system and in one-to-one mapping with the rollback point ID. |
Usage Guidelines
Usage Scenario
- After a configuration rollback point is generated, the system automatically allocates an ID for this configuration rollback point. The rollback point ID is an integer that ranges from 1000000001 to 1999999999, which is difficult to understand and remember. When the number of configuration rollback points that are automatically generated by the system reaches the upper threshold, earliest configuration rollback points are replaced by latest configuration rollback points. For some important configurations, however, the related configuration rollback points need to be retained. In this case, you can run the set configuration commit command to specify a user label for a configuration rollback point, which is easy to understand and remember and ensures that configuration rollback points related to important configurations are not replaced.
- You can specify a user label when you run the commit command to generate a rollback point. After a rollback point is generated, you can run the set configuration commit label command to set a user label for the rollback point. For continuous configuration rollback points with labels, you cannot directly modify the labels. You must run the clear configuration commit label command to delete the labels of the configuration rollback points first and then run the set configuration commit label command to specify user labels for the configuration rollback points.
- You can run the clear configuration commit label command to delete the configured labels. After a configuration rollback point is deleted, its label is deleted accordingly.
Follow-up Procedure
Run the display configuration commit list command to view information about the user label for a configuration rollback point.
Run the display configuration commit list command to display the configuration commit label information.Precautions
If the set configuration commit command is run several times, the latest configuration overwrites the previous configuration.
set configuration operation cpu-limit
Function
The set configuration operation cpu-limit command reduces the rate to some extent in response to the CPU overhigh caused by NMS data collection.
The undo set configuration operation cpu-limit command deletes the threshold configured for CPU rate decreasing.
By default, no threshold is configured for CPU rate decreasing.
Format
set configuration operation cpu-limit { percent-value access-type snmp | ncf-percent-value access-type netconf }
undo set configuration operation cpu-limit [ { access-type snmp | access-type netconf } ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| percent-value |
Specifies a threshold for CPU rate decreasing in SNMP access mode. |
The value is an integer ranging from 30 to 100. |
| access-type |
Specifies a protocol access type. |
- |
| snmp |
Specifies the access type protocol is snmp. |
- |
| ncf-percent-value |
Specifies a threshold for CPU rate decreasing in NETCONF access mode. |
The value is an integer ranging from 30 to 100. |
| netconf |
Specifies the access type protocol is netconf. |
- |
Usage Guidelines
Usage Scenario
Data collection by an NMS consumes many CPU resources. To ensure that other service runs properly, the device must reserve some resources for other services. To resolve this issue, run the set configuration operation cpu-limit command to configure a threshold for CPU rate decreasing. If the CPU usage reaches the configured threshold, the device reduces CPU resources allocated to the NMS when the NMS collects data. In this case, CPU pressure can be relieved to some extent.
Precautions
The default values of <percent-value> and <ncf-percent-value> are customized on the product side. You can run the display this include-default command to view the current default values.
set save-configuration checkpoint daily
Function
The set save-configuration checkpoint daily command enables or sets the time for periodically generating configuration rollback points.
The undo set save-configuration checkpoint daily command disables the function of periodically generating configuration rollback points.
By default, the system does not periodically generate configuration rollback points.
Format
set save-configuration checkpoint daily time time
undo set save-configuration checkpoint daily time [ time ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| time time |
Specifies the time when configuration rollback points are automatically generated. |
The value is in the hh:mm format. hh specifies the hour, which is an integer ranging from 0 to 23. mm specifies the minute, which is an integer ranging from 0 to 59. |
startup default-configuration
Function
The startup default-configuration command configures a preset configuration file for the system. If no configuration file is specified for next startup, the device uses this preset configuration file for startup.
Parameters
| Parameter | Description | Value |
|---|---|---|
| configuration-file |
Specifies the name of the preset configuration file. This file must exist. |
The value is a string of 8 to 127 characters in the format of *.defcfg. |
Usage Guidelines
Usage Scenario
If the system does not have the configuration file for next startup and starts with empty configuration, engineers need to perform onsite configuration, which is inconvenient for device O&M. To implement plug-and-play after an unconfigured device starts, you can run the startup default-configuration command to preset a configuration file for the device. The preset configuration file carries plug-and-play configurations. After the device starts with empty configuration next time, it uses the preset configuration file to restore configurations.
The preset configuration file is in plaintext format and uses .defcfg as the file name extension. Before running the startup default-configuration command, save the file to the root directory of the device. You can run the more *.defcfg command to view the file content. After the startup default-configuration command is run, the content of the preset configuration file in the root directory is imported to the fixed directory of the device, and the preset configuration file in the root directory can be deleted.Configuration Impact
If no configuration file is specified for next startup, the device uses the preset configuration file for next startup.
Precautions
The size of the preset configuration file cannot exceed 50 KB.
Exercise caution and follow the instructions of the technical support personnel when you run this command.startup
Function
The startup saved-configuration command specifies the configuration file to be loaded at the next startup of the system.
The startup shareable-configuration command imports a configuration file. The password entered by the user matches the key in the configuration file.
Format
startup saved-configuration configuration-file
startup shareable-configuration configuration-file [ password ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| configuration-file |
Specifies the name of a configuration file. The file must have been created. |
The name is a string of 5 to 64 characters in the format of *.zip, *.cfg or *.dat. |
| password |
Specifies the password for decrypting a configuration file. |
- |
Usage Guidelines
Usage Scenario
If the configuration file becomes inapplicable due to software upgrade, run the startup saved-configuration command to specify a new configuration file to be loaded at the next startup of the system. You can run the startup shareable-configuration command to configure the configuration file that contains the key information saved on another device as the next startup file.
The extension of the configuration file name must be .zip, .cfg or .dat. The system configuration file must be saved in the root directory of the storage device.- A .cfg file is a text file, whose contents can be viewed directly. If a .cfg file is specified as the configuration file, the system restores the commands in the file one by one during device startup.
- A .zip file is compressed from a .cfg file and occupies less space. If a .zip file is specified as the configuration file, the system first decompresses the file into a .cfg file, and then restores the commands in the .cfg file one by one during device startup.
- A .dat file is a compressed file, which can be in binary or text mode. If the startup software version and the .dat file version are the same, the system restores all configurations at a time without the need to restore the commands one by one, accelerating device startup. The specified configuration file for next startup must be checked against the first-login configuration file. If the check fails, the following message is displayed: Error: The configuration file will cause the next startup login failure.Please check it. This message indicates that the configuration file will cause a login failure for the next startup. You need to add the login configuration of the console port or port configured with the management IP address to the configuration file.
Configuration Impact
The configuration file to be loaded at the next startup of the system is changed.
Precautions
- The specified configuration file must exist.
- A .dat file cannot be modified manually. Otherwise, the configuration file will fail to be loaded when the device starts, and the device will start with empty configurations.
- If the automatic configuration saving function is enabled, after you run this command to specify the configuration file for next startup, configuration saving is triggered when the automatic saving interval expires. As a result, the configuration file for next startup may be overwritten by current configurations. If you do not want to overwrite the configuration file for next startup, run the undo configuration file auto-save command to disable the automatic configuration saving function before running the current command.
- If you run the save command after running the current command to specify the configuration file for next startup, the configuration file for next startup will be overwritten by the current configurations.
- If the specified configuration file does not have the HMAC code, the file can still be specified successfully but integrity check will not be performed. You need to ensure the validity of the file.
- After switching to the FIPS mode, the specified configuration file for next startup cannot be the configuration file created in non-FIPS mode.
Example
<HUAWEI> system-view [~HUAWEI] undo configuration file auto-save [*HUAWEI] commit [~HUAWEI] quit <HUAWEI> startup saved-configuration huawei.cfg
<HUAWEI> startup shareable-configuration 333.cfg
Info: Operating, please wait for a moment..................................done.
Info: Succeeded in setting the configuration for booting system.
<HUAWEI> startup shareable-configuration test.cfg password
Enter Password:
Info: Operating, please wait for a moment....................done.
Info: Succeeded in setting the configuration for booting system.
<HUAWEI> system-view [~HUAWEI] configuration file auto-save [*HUAWEI] commit [~HUAWEI] quit <HUAWEI> startup saved-configuration huawei.cfg
- abort
- abort trial
- apply-command-group
- clear configuration candidate
- clear configuration commit label
- clear configuration commit oldest
- collect diagnostic information(user view)
- command group
- commit (All views except the user view)
- commit label
- compare configuration
- configuration check local-user disable
- configuration checkpoint auto-save disable
- configuration current backup-to-file
- configuration current backup-to-server monthly
- configuration exclusive
- configuration exclusive by-user-name
- configuration exclusive timeout
- configuration file auto-save
- configuration file auto-save backup-to-server
- configuration re-authentication enable
- configuration save-policy interrupt-allowed
- display command-group applied
- display configuration apply-command-group fail-result
- display configuration candidate
- display configuration candidate (All views except the user view)
- display configuration changes
- display configuration commit
- display configuration commit list
- display configuration exclusive by-user-name
- display configuration exclusive user
- display configuration recover-result
- display configuration replace failed
- display configuration replace file
- display configuration rollback result
- display configuration sessions
- display configuration trial status
- display current-configuration (All views)
- display current-configuration inheritance
- display saved-configuration configuration
- display saved-configuration time
- display this inheritance
- end-group
- load configuration replace
- refresh configuration candidate
- reset default-configuration
- reset saved-configuration
- rollback configuration
- save
- set configuration appdata auto-check enable
- set configuration commit
- set configuration operation cpu-limit
- set save-configuration checkpoint daily
- startup default-configuration
- startup