Configuration Statements And Identifiers - Juniper JUNOS - NETWORK OPERATION GUIDE REV1 Network Operation Manual

Configuration Statements and Identifiers

You configure all router properties by including statements in the configuration. A
statement consists of a keyword, which is fixed text, and, optionally, an identifier.
An identifier is an identifying name that you define, such as the name of an
interface, or a username, which allows you and the CLI to discriminate among a
collection of statements.
The following list shows the statements available at the top level of the
configuration mode (that is, the trunk of the hierarchy tree). Table 135 on page 643
describes each statement.
Command Description
Return to a previously committed configuration. The software saves the last
rollback
10 committed configurations, including the rollback number, date, time, and
name of the user who issued the commit configuration command.
erases any configuration changes made to the current candidate
rollback 0
configuration. The currently operational JUNOS software configuration is
stored in the file juniper.conf, and the last three committed configurations are
stored in the files juniper.conf.1.gz, juniper.conf.2.gz, and juniper.conf.3.gz.
These four files are located in the directory /config/, which is on the router's
flash drive. The remaining six previous committed configurations, the files
juniper.conf.4.gz through juniper.conf.9.gz, are stored in the directory
/var/db/config/, which is on the router's hard disk.
Syntax:
rollback <number>
Run a CLI command without exiting from configuration mode.
run
Syntax:
run command
Save the configuration to an ASCII file, by default in the users home directory.
save
The contents of the current level of the statement hierarchy (and below) are
saved, along with the statement hierarchy containing it. This allows a section
of the configuration to be saved, while fully specifying the statement
hierarchy.
Syntax: save filename
set Create a statement hierarchy and set identifier values. This is similar to
except that your current level in the hierarchy does not change, and you can
set identifier values whereas edit only allows access to a statement-path.
Syntax: set (statement-path | identifier)
show Display the current configuration.
Syntax: show (statement-path | identifier)
status Display the users currently editing the configuration.
top Return to the top level of configuration command mode, which is indicated by
the [edit] banner, or execute a command from the top level of the
configuration.
Syntax: top <configuration-command>
up Move up one level in the statement hierarchy.
Syntax: up <number>
update Update a private database.
[edit]
user@host# set ?
Possible completions:
> access Network access configuration
Appendix A: Command-Line Interface Overview
CLI Configuration Mode
edit
!
641