Discussion

In this example, the error is in the RIP routing protocol, and this error is flagged by the
software process (the JUNOS term for a Unix daemon) that checks the configuration.
1.9 Exiting Configuration Mode
Problem
After you have completed making changes to the configuration, you want to activate
the configuration and return to operational mode.
Solution
From the top hierarchy level, activate the configuration and exit configuration mode:
[edit]
aviva@router1# commit
aviva@router1# quit
aviva@router1>
From a lower level in the hierarchy, commit and exit configuration mode:
[edit system]
aviva@router1# commit
aviva@router1# top
[edit]
aviva@router1# quit
aviva@router1>
The following command is a quicker variation:
[edit system]
aviva@router1# commit
aviva@router1# exit configuration-mode
aviva@router1>
From any hierarchy level, activate the configuration and exit configuration mode
with a single command:
[edit system]
aviva@router1# commit and-quit
aviva@router1>
Discussion
The commands in this recipe show several variations of quitting configuration mode
after you have committed a configuration. If you issue separate commit and quit (or
exit) commands, you must be at the top level of the hierarchy (at the [edit] level)
for the exit command to quit configuration mode. From a lower level, use the top
command to return quickly to the [edit] level. If you use the exit command at a
lower level, it returns you to the highest hierarchy from which you previously issued
an edit command.
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.
Exiting Configuration Mode | 25