Login
- Table of Contents
-
- 01-Fundamentals Configuration Guide
- 00-Preface
- 01-CLI configuration
- 02-RBAC configuration
- 03-Login management configuration
- 04-FTP and TFTP configuration
- 05-File system management configuration
- 06-Configuration file management configuration
- 07-Multichassis configuration sync configuration
- 08-Software upgrade configuration
- 09-ISSU configuration
- 10-GIR configuration
- 11-Automatic configuration
- 12-Device management configuration
- 13-Target configuration management configuration
- 14-Tcl configuration
- 15-Python configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 13-Target configuration management configuration | 67.17 KB |
Committing the target configuration command lines
Display and maintenance commands for target configuration
Managing target configuration
About target configuration
Target configuration enables you to configure and verify intended settings before merging them into the running configuration.
You can configure target configuration command lines in the following views:
· Private-mode system view and its lower-level views.
· Exclusive-mode system view and its lower-level views.
Commands available for real-time configuration are all available for target configuration.
Support for command lines in private-mode system view and in exclusive-mode system view depends on the device model. In private-mode system view and in exclusive-mode system, you do not need to commit hardware-related command lines and action command lines, because they take effect immediately.
Private-mode views and exclusive-mode views have an extra tilde sign (~) in their prompts as compared to their counterpart real-time-mode views. For more information about views, see "Using the CLI."
Committing the target configuration command lines
About this task
A commit operation commits all target configuration command lines. After a successful commit operation, the system creates a configuration rollback point.
Restrictions and guidelines
As a best practice, do not execute the commit command frequently. The system creates a configuration rollback point after each successful commit operation. Executing the command frequently increases device load and might cause commit failures.
Procedure
1. (Optional.) Specify the maximum number of rollback points:
a. Enter real-time-mode system view.
system-view
b. Set the maximum number of rollback points.
configuration commit max-number max-number
By default, the maximum number of rollback points is 100.
To create a new rollback point when the number of rollback points reaches the maximum, the system deletes the oldest rollback point.
c. Return to user view.
quit
2. (Optional.) Enable automatic saving for the target configuration command lines and configure the related parameters:
a. Enter real-time-mode system view.
system-view
b. Enable automatic saving for the target configuration command lines and configure the related parameters.
configuration commit auto-save path directory filename-prefix filename-prefix [ user user-name [ password { cipher | simple } string ] ] *
By default, automatic saving is disabled for the target configuration command lines.
c. Return to user view.
abort
3. Enter private-mode system view or exclusive-mode system view.
system-view { exclusive | private }
4. Configure features as required.
For more information about configuring features, see the configuration guides.
5. (Optional.) Display target configuration command lines.
display target-configuration
Incorrect target configuration command lines will affect the operation of the network. Use this command to verify that all target configuration command lines are correct.
6. (Optional.) Refresh uncommitted target configuration.
refresh target-configuration
7. Commit the target configuration command lines.
commit [ best-effort ] [ force ] [ label labelname ] [ save-running filename ] [ confirmed [ seconds | minutes minutes ] ] [ show-error ] [ clear-error ] [ description text ]
8. (Optional.) Roll back the running configuration.
configuration replace { file filename | last number | commit-id commit-id | label labelname }
|
|
CAUTION: This operation will cause settings not at the rollback point to be lost, which might cause service interruption. When you perform configuration rollback, make sure you fully understand its impact on your network. |
To reclaim target configuration command lines that have been committed, use this command to roll back the running configuration as required. For more information about this command, see configuration file management commands in Fundamentals Command Reference.
Display and maintenance commands for target configuration
Execute the following commands in private-mode system view, exclusive-mode system view, or their lower-level views:
· display target-configuration
· reset target-configuration
Execute the following commands in any view:
· display configuration commit diff
· display configuration commit list
· display configuration sessions
Execute the reset configuration commit command in user view.
|
Task |
Command |
|
Display the configuration differences between a rollback point and the running configuration or between two rollback points. |
display configuration commit diff [ at commit-id | last number | since commit-id ] |
|
Display rollback point information. |
display configuration commit list [ number | label ] [ verbose ] |
|
Display device configuration sessions. |
display configuration sessions |
|
Display the target configuration command lines. |
display target-configuration [ diff | failure [ brief ] | merge | success ] |
|
Clear old rollback points. |
reset configuration commit number |
|
Clear the target configuration command lines. |
reset target-configuration [ command [ text ] ] |
