Conventions for Tag Summaries

The Usage section of the reference entries in this document uses the following text conventions:

• The tag described by the entry appears in bold font. Its parent and child tags appear in regular font. The string between the opening and closing parts of a tag element appears in italic font and describes the type of value represented by the tag.

The following sample for the <admin-groups> tag illustrates the fonts used in an entry:

<configuration>
    <protocols>
        <mpls>
            <admin-groups>
                <name>name</name> <!-- identifier -->
                <group-value>group-value</group-value>
            </admin-groups>
        </mpls>
    </protocols>
</configuration>

• An ellipsis (...) between a child tag's opening and closing tags indicates that the tag is itself a container tag. An entry for the child tag appears in alphabetical order in the chapter and lists all of its children.

The following example indicates that there are separate entries for the <defaults> and <route> children of the <aggregate> tag:

<aggregate>
    <defaults>...</defaults>
    <route>...</route>
</aggregate>

• XML comments appear between the strings <!-- and -->, as in the following example:

<name>value</name>       <!--identifier-->

• Some tags can be the child of more than one parent. If the immediate parents all occur at the same hierarchy level, the parent tag names appear in a single tag, separated by pipes ( | ). For example, the following indicates that the tag being described can be a child of both the <physical-interface> and <logical-interface> tags:

<physical-interface | logical-interface>

If the tag's parents occur at different levels of the hierarchy, there is a separate entry for each instance of the tag. To distinguish them, each entry's header specifies the statement path in parentheses following the tag name.

• Optional attributes appear in square brackets ( [ ] ). For example, the following indicates that the hostname and release attributes are optional but that the version attribute is required:

<junoscript version="version" [hostname="hostname"] [release="release"]>

• If an attribute has multiple mutually exclusive values, they appear in a list enclosed in parentheses ( ( ) ) and separated by pipes ( | ). For example, the following indicates that the action attribute can have one of the values merge, override, or replace:

action="( merge | override | replace )"