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 at the Juniper Networks Technical
Documentation 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
https://www.juniper.net/cgi-bin/docbugreport/
.
xix
Copyright © 2015, Juniper Networks, Inc.
About the Documentation
Summary of Contents for EX4300
Page 1: ...EX4300 Switch Hardware Guide Modified 2015 06 29 Copyright 2015 Juniper Networks Inc ...
Page 16: ...Copyright 2015 Juniper Networks Inc xvi EX4300 Switch Hardware Guide ...
Page 22: ...Copyright 2015 Juniper Networks Inc xxii EX4300 Switch Hardware Guide ...
Page 24: ...Copyright 2015 Juniper Networks Inc 2 EX4300 Switch Hardware Guide ...
Page 102: ...Copyright 2015 Juniper Networks Inc 80 EX4300 Switch Hardware Guide ...
Page 104: ...Copyright 2015 Juniper Networks Inc 82 EX4300 Switch Hardware Guide ...
Page 128: ...Copyright 2015 Juniper Networks Inc 106 EX4300 Switch Hardware Guide ...
Page 172: ...Copyright 2015 Juniper Networks Inc 150 EX4300 Switch Hardware Guide ...
Page 176: ...Copyright 2015 Juniper Networks Inc 154 EX4300 Switch Hardware Guide ...
Page 218: ...Copyright 2015 Juniper Networks Inc 196 EX4300 Switch Hardware Guide ...
Page 236: ...Copyright 2015 Juniper Networks Inc 214 EX4300 Switch Hardware Guide ...
Page 238: ...Copyright 2015 Juniper Networks Inc 216 EX4300 Switch Hardware Guide ...
Page 250: ...Copyright 2015 Juniper Networks Inc 228 EX4300 Switch Hardware Guide ...
Page 256: ...Copyright 2015 Juniper Networks Inc 234 EX4300 Switch Hardware Guide ...
Page 278: ...Copyright 2015 Juniper Networks Inc 256 EX4300 Switch Hardware Guide ...
Page 286: ...Copyright 2015 Juniper Networks Inc 264 EX4300 Switch Hardware Guide ...
Page 292: ...Copyright 2015 Juniper Networks Inc 270 EX4300 Switch Hardware Guide ...
Page 306: ...Copyright 2015 Juniper Networks Inc 284 EX4300 Switch Hardware Guide ...
Page 312: ...Copyright 2015 Juniper Networks Inc 290 EX4300 Switch Hardware Guide ...
Page 336: ...Copyright 2015 Juniper Networks Inc 314 EX4300 Switch Hardware Guide ...