Table 2: Text and Syntax Conventions
(continued)
Examples
Description
Convention
•
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; configuration hierarchy levels;
or labels on routing platform
components.
Text like this
stub <default-metric
metric
>;
Encloses 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
]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
•
In the Logical Interfaces box, select
All Interfaces
.
•
To cancel the configuration, click
Cancel
.
Represents 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 menu
selections.
>
(bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•
Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at
http://www.juniper.net/techpubs/index.html
, simply click the stars to rate the content,
and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
http://www.juniper.net/techpubs/feedback/
xv
Copyright © 2017, Juniper Networks, Inc.
About the Documentation
