Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Notational Conventions Used in Junos OS Configuration Hierarchies

When you are working in Junos OS command-line interface (CLI) configuration mode, the banner on the line preceding the prompt indicates the current hierarchy level. In the following example, the level is [edit protocols ospf]:

[edit protocols ospf]user@host#

(The Junos OS documentation uses user@host# as the standard configuration mode prompt. In an actual CLI session, the prompt shows your user ID and the name of the Juniper Networks device you are working on.)

Use the set ? command to display the statements that you can include in the configuration at the current level. The help apropos command is also context-sensitive, displaying matching statements only at the current level and below.

Note: In this document, statements are listed alphabetically within each hierarchy and subhierarchy. If a subhierarchy is sufficiently long that it might be difficult to determine where it ends and its next peer statement begins, the subhierarchy appears at the end of its parent hierarchy instead of in alphabetical order. In this case, a placeholder appears in its actual alphabetical position.

For example, at the [edit interfaces interface-name unit logical-unit-number] hierarchy level, the family family-name subhierarchy has more than 20 child statements, including several subhierarchies with child statements of their own. The full family family-name hierarchy appears at the end of its parent hierarchy ([edit interfaces interface-name unit logical-unit-number]), and the following placeholder appears at its actual alphabetical position:

family family-name {... the family subhierarchy appears after the main [edit interfaces interface-name unit logical-unit-number] hierarchy ...}

Another exception to alphabetical order is that the disable statement always appears first in any hierarchy that includes it.

 

Related Documentation

 

Published: 2012-11-26

Previous Page Next Page