...
commit - commit the current set of changes
Syntax: commit [ comment <comment-text> ]
Use this command to apply and save uncommitted changes to the configuration.
When you add configuration to, modify the existing configuration, or delete configuration from the system, the changes you make must be committed before they take effect. To commit changes, use the commit command.
If you try to exit or quit configuration mode while uncommitted configuration changes still exist, the system gives you a warning. You cannot exit configuration mode until you either commit the changes by entering the commit command or discard the changes by using the discard command.
Until a configuration change is committed, the system marks the change when displaying the information.
| Note |
|---|
If your login username is not a member of the "secrets" login user group and you either save a configuration through the REST API or use the save command, the encrypted passwords in the configuration file are replaced with the ******** placeholder. If you load this configuration, the replaced password fields trigger validation errors because the placeholder does not match the format for an encrypted password. Do not commit this configuration. If you ignore the error message |
Use commit comment <comment-text> to add a comment that describes the reason for the commit and seen in the output from show system commit.
commit-confirm - commit the current set of changes; rollback if not confirmed
Syntax: commit-confirm <minutes> [ comment <comment-tex> ]
Use this command to set the system to require confirmation of a configuration commit.
This operation is useful when making configuration changes over a remote connection that could cause you to be unable to reconnect to the system, for example, accidentally changing the IP address of the management port.
A reboot during the commit-confirm timeout window results in the restoration of the previous configuration.
After making a configuration change, enter the commit-confirm command, specifying the confirmation interval. Commit the change. If the commit is completed, without incident, confirm the commit by entering the command confirm. If you do not confirm, the changes are rolled back.
If the new commit-confirmed configuration causes a crash before the confirmation window expires, the system reboots and rolls back to avoid an endless cycle of rebooting.
If you attempt to use the GRUB configuration recovery option when rebooting during the commit-confirm timeout window is active, a message to wait for the rollback to be completed is displayed.
If you enter commit, commit-confirm, or rollback commands during the commit-confirm timeout, the current commit that is pending confirmation is implicitly confirmed. For example, rollback 1 takes you back to the immediately preceding commit (before the original commit-confirm), and rollback 0 recommits the current configuration.
compare - compare configuration revisions
Syntax: compare [ rev-num1 [ rev-num2 ] ]
When used with no option, the working and active (running) configuration are compared. When only one revision number is specified, the system compares the working configuration to the specified revision. When two revisions are specified, the system compares the two specified revisions.
You can see the list of configuration file revisions by using show system commit in operational mode (use run show system commit in configuration mode).
confirm - confirm configuration changes
Syntax: confirm
Use this command to confirm a successful change in configuration after requiring commit confirmation.
For configuration changes that carry some risk of causing loss of access to a system, you can direct the system to require commit confirmation by using the command commit-confirm <minutes>. This command sets the system to wait for confirmation that a configuration has succeeded.
Entering the confirm command within the specified commit-confirm interval causes the configuration change to be accepted. If confirmation is not provided by entering this command, the system reboots to the previous configuration.
delete - delete a configuration element
Syntax: delete <config-node>
Use this command to delete a part of configuration. To do this, you delete the appropriate subnode of a configuration node.
If you show configuration before it is committed, you see the deleted statement flagged with a minus sign (-); the statement disappears after the configuration change is committed.
Some configuration nodes and statements are mandatory; these nodes or statements cannot be deleted. Some configuration statements are mandatory but have default values; if you delete one of these statements, the default value is restored.
discard - discard uncommitted changes
Syntax: discard
Use this command to discard all uncommitted changes to the configuration.
edit - edit a sub-element
Syntax; edit <path>
Use this command to navigate to a specific configuration subnode for editing. The [edit] prompt changes dynamically to mark your place in the configuration tree.
Once at that location, any actions you take such as showing, creating, or deleting configuration are relative to your location in the tree.
exit - exit from configuration level
Syntax: exit [ discard ]
Use this
...
command from a subnode in the configuration tree to navigate to the top of the configuration tree.
Use this command from the top of the configuration tree to exit from configuration mode to operational mode.
If you try to exit from configuration mode while there are still uncommitted configuration changes, the system gives you a warning. You cannot exit from configuration mode until you either commit the changes by entering the commit command or discard the changes by using the discard option. This option applies only to this usage.
load - load configuration from a file and replace candidate configuration
...