Filter
Top Products
Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
■
To configure a stub area, include
the stub statement at the [edit
protocols ospf area area-id]
hierarchy level.
■
The console port is labeled
CONSOLE.
Represents names of configuration
statements, commands, files, and
directories; IP addresses; configuration
hierarchy levels; or labels on routing
platform components.
Plain text like this
stub <default-metric metric>;
Enclose optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 | string2 | string3)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
| (pipe symbol)
rsvp { # Required for dynamic MPLS only
Indicates a comment specified on the
same line as the configuration statement
to which it applies.
# (pound sign)
community name members [
community-ids ]
Enclose a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identify a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
J-Web GUI Conventions
■
In the Logical Interfaces box, select
All Interfaces.
■
To cancel the configuration, click
Cancel.
Represents J-Web graphical user
interface (GUI) items you click or select.
Bold text like this
In the configuration editor hierarchy,
select Protocols>Ospf.
Separates levels in a hierarchy of J-Web
selections.
> (bold right angle bracket)
SRX Series Documentation and Release Notes
For a list of related SRX Series documentation, see
http://www.juniper.net/techpubs/hardware/srx-series-main.html.
If the information in the latest SRX Series Release Notes differs from the information
in the documentation, follow the SRX Series Release Notes.
SRX Series Documentation and Release Notes ■ xvii
About This Guide