You enter configuration mode by entering the configure operational mode command.
The following configuration mode commands are available:
user@host>configureentering configuration mode [edit] user@host#?Possible completions: <[Enter]> Execute this command activate Remove the inactive tag from a statement annotate Annotate the statement with a comment commit Commit current set of changes copy Copy a statement deactivate Add the inactive tag to a statement delete Delete a data element edit Edit a sub-element exit Exit from this level help Provide help information insert Insert a new ordered data element load Load configuration from an ASCII file quit Quit from this level rename Rename a statement rollback Roll back database to last committed version run Run an operational-mode command save Save configuration to an ASCII file set Set a parameter show Show a parameter status Display database user status top Exit to top level of configuration up Exit one level of configuration
For a complete list of the configuration commands, see Complete Configuration Mode Commands and Statements.
The access privilege level required to enter configuration mode is controlled by the configure permission bit. Users for whom this permission bit is not set do not see the configure command as a possible completion when they enter a ? in operational mode, and they cannot enter configuration mode. Users for whom this bit is set do see this command and can enter configuration mode. When in configuration mode, a user can view and modify only those statements for which they have access privileges set. For more information, see Configure Access Privilege Levels.
You can enter configuration mode with either the configure command or the configure exclusive command. The configure exclusive command gives you sole access to the configuration database, locking out all other users.
If you and other users enter configuration mode with the configure command, everyone can make configuration changes and commit all changes made to the configuration. This means that if you and another user have made configuration changes and the other user commits, the changes you made are committed as well. That is, no one has a lockout on the configuration file.
If, when you enter configuration mode, another user is also in configuration mode, a message indicates who the user is and what portion of the configuration the user is viewing or editing:
user@host> configure
Entering configuration mode
Current configuration users:
root terminal p3 (pid 1088) on since 1999-05-13 01:03:27 EDT
[edit interfaces so-3/0/0 unit 0 family inet]
The configuration has been changed but not committed
[edit]
user@host>
If, when you enter configuration mode, the configuration contains changes that have not been committed, a message appears:
user@host> configure
Entering configuration mode
The configuration has been changed but not committed
[edit]
user@host>
If, while in configuration mode, you try to make a change while the configuration is locked by another user, a message indicates that the configuration database is locked, who the user is, and what portion of the configuration the user is viewing or editing:
user@host# set system host-name ipswitch
error: configuration database locked by:
user2 terminal d0 (pid 1828) on since 19:47:58 EDT, idle 00:02:11
exclusive [edit protocols]
If you enter configuration mode with the configure exclusive command, you lock the candidate configuration for as long as you remain in configuration mode, allowing you to make changes without interference from other users. Other users can enter and exit configuration mode, but they cannot change the configuration. If another user has locked the configuration, and you need to forcibly log them out, enter the operational mode command request system logout user.
If, when you enter configuration mode, another user is also in configuration mode, and has the configuration locked, a message indicates who the user is and what portion of the configuration the user is viewing or editing:
user@host> configure
Entering configuration mode
Users currently editing the configuration:
root terminal p3 (pid 1088) on since 2000-10-30 19:47:58 EDT, idle 00:00:44
exclusive [edit interfaces so-3/0/0 unit 0 family inet]