Juniper Networks SRX 210 SRX Series Documentation and Release Notes, string1 string2 string3

About This Guide

Table 2: Text and Syntax Conventions (continued)

Convention	Description
Plain text like this	Represents names of configuration
	statements, commands, files, and
	directories; IP addresses; configuration
	hierarchy levels; or labels on routing
	platform components.

Examples

■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.

< > (angle brackets)	Enclose optional keywords or variables.
(pipe symbol)	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.
# (pound sign)	Indicates a comment specified on the
	same line as the configuration statement
	to which it applies.

stub <default-metric metric>;

broadcast multicast

(string1 string2 string3)

rsvp { # Required for dynamic MPLS only

[ ] (square brackets)	Enclose a variable for which you can
	substitute one or more values.
Indention and braces ( { } )	Identify a level in the configuration
	hierarchy.
; (semicolon)	Identifies a leaf statement at a
	configuration hierarchy level.

J-Web GUI Conventions

community name members [ community-ids]

[edit] routing-options {

static {

route default { nexthop address; retain;

}

}

}

Bold text like this	Represents J-Web graphical user	■	In the Logical Interfaces box, select
	interface (GUI) items you click or select.		All Interfaces.
		■	To cancel the configuration, click
			Cancel.
> (bold right angle bracket)	Separates levels in a hierarchy of J-Web	In the configuration editor hierarchy,
	selections.	select Protocols>Ospf.

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