Tab; Arrow Keys; The No Version - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x System Basics Configuration Guide
32

Tab

Use this key to complete the current keyword. For example, if you entered a portion of a
lengthy command, such as
host1(config)#class
and press Tab, the full name of the command appears:
host1(config)#classifier-list

Arrow Keys

Some terminals have arrow (or cursor) keys on their keyboards. These arrow keys are
very useful; however, to use them you must have an ANSI/VT100 emulating terminal.
The Up Arrow and Down Arrow keys display command history. The Up Arrow key displays
the previous command; you can also use Ctrl+p. The Down Arrow key displays the next
command; you can also use Ctrl+n.
The Left Arrow and Right Arrow keys allow the user to move the cursor back and forth
in the command line.

The no Version

With very few exceptions, every system configuration command has a no version, which
you can use to negate a command (or a portion of it as specified by an optional keyword)
or to restore its default setting. When you use a command without the keyword no, you
can reenable a disabled feature or override a default setting.
You have the option of using the default keyword whenever the no keyword is also a
choice; simply enter the keyword default instead of no.
In most cases, when you execute the default version of a command, it produces the
exact results as the no version. There are some commands for which the default version
yields a different result from the no version.
Commands for which the default behavior differs from the no behavior are clearly
identified in the JunosE Command Reference Guide. Unless otherwise specified, therefore,
the default command is identical to the no command and is neither documented nor
discussed.
The syntax for each no command is described in the JunosE Command Reference Guide.
The few system configuration commands that do not have a no version are indicated in
the individual command description.
Because show commands are for the purpose of monitoring your configurations, they
do not have no versions. Most User Exec and Privileged Exec mode commands do not
have no versions.
The CLI can act on no versions of commands when you have entered sufficient information
to distinguish the command syntactically; the CLI ignores all subsequent input on that
line.
Copyright © 2010, Juniper Networks, Inc.