Discussion

Here’s an example sequence of edit and exit commands to illustrate this:
[edit]
aviva@router1# edit protocols
[edit protocols]
aviva@router1# edit ospf
[edit protocols ospf]
aviva@router1# edit area 0.0.0.1
[edit protocols ospf area 0.0.0.1]
aviva@router1# exit
[edit protocols ospf]
aviva@router1# exit
[edit protocols]
aviva@router1# exit
[edit]
aviva@router1# exit
Exiting configuration mode
aviva@router1>
A quicker way to commit and then exit configuration mode from a lower level in the
hierarchy is to use the commit command followed by the exit configuration-mode
command.
Perhaps the quickest way to commit and get back to operational mode is to use the
commit and-quit command. You can use this command at any hierarchy level. One
caveat is that this command succeeds only if there are no mistakes or syntax errors in
the configuration. If the commit fails, the CLI shows an error message, and you
remain in configuration mode.
See Also
Recipe 1.7
1.10 Keeping a Record of Configuration Changes
Problem
When you activate a configuration, you want to include a short message that
describes the changes you made.
Solution
Include a comment when you activate the configuration:
aviva@router1# commit comment "turned on telnet"
Discussion
It’s good practice to include a short description of the changes you made to each version
of a configuration file so you can keep a history of configuration changes. You
do this by using the comment option with the commit command.
26 | Chapter 1: Router Configuration and File Management
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.