Obtaining Documentation; Documentation Feedback; Requesting Technical Support; About The Documentation - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - PHYSICAL LAYER CONFIGURATION GUIDE 2010-09-24 Configuration Manual

Table 2: Text and Syntax Conventions (continued)
Convention
| (pipe symbol)
[ ] (brackets)
[ ]* (brackets and asterisk)
{ } (braces)

Obtaining Documentation

Documentation Feedback

Requesting Technical Support

Copyright © 2010, Juniper Networks, Inc.
Description
Represents a choice to select one keyword
or variable to the left or to the right of this
symbol. (The keyword or variable can be
either optional or required.)
Represent optional keywords or variables.
Represent optional keywords or variables
that can be entered more than once.
Represent required keywords or variables.
To obtain the most current version of all Juniper Networks technical documentation, see
the Technical Documentation page on the Juniper Networks Web site at
http://www.juniper.net/ .
To download complete sets of technical documentation to create your own
documentation CD-ROMs or DVD-ROMs, see the Portable Libraries page at
http://www.juniper.net/techpubs/resources/index.html
Copies of the Management Information Bases (MIBs) for a particular software release
are available for download in the software image bundle from the Juniper Networks Web
site at
http://www.juniper.net/
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation to better meet your needs. Send your comments to
techpubs-comments@juniper.net
https://www.juniper.net/cgi-bin/docbugreport/
the following information with your comments:
Document or topic name
URL or page number
Software release version
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
Examples
diagnostic | line
[ internal | external ]
[ level1 | level2 | l1 ]*
{ permit | deny } { in | out }
{ clusterId | ipAddress }
.
, or fill out the documentation feedback form at
. If you are using e-mail, be sure to include

About the Documentation

xxi