Table 158: show isis interface Output Fields (continued)
Level of OutputField DescriptionField Name
none briefLevel 1 designated intermediate system.Level 1 DR
none briefLevel 2 designated intermediate system.Level 2 DR
none briefInterface's metric for Level 1 and Level 2. If there is no information, the metric
is 0.
L1/L2 Metric
detail extensiveFlood-group is configured on a specific IS-IS interface
NOTE: Seen only when Flood-group is configured.
Flood-group
Area-ID
detail extensiveThis routing device has signaled to advertise this interface to its neighbors in
their label-switched paths (LSPs).
Adjacency
advertisement:
Advertise
detail extensiveThis neighbor has signaled not to advertise this interface in the routing device’s
outbound LSPs.
Adjacency
advertisement:
Suppress
detailNumber of adjacencies established on this interface.Adjacencies
detailPriority value for this interface.Priority
detailMetric value for this interface.Metric
detail extensiveInterface's hello interval.Hello(s) / Hello
Interval
detail extensiveInterface's hold time.Hold(s) / Hold Time
detailRouter responsible for sending network link-state advertisements, which describe
all the routing devices attached to the network.
Designated Router
extensiveType of hello padding:
• Adaptive—On point-to-point connections, the hello packets are padded from
the initial detection of a new neighbor until the neighbor verifies the adjacency
as Up in the adjacency state TLV. If the neighbor does not support the
adjacency state TLV, then padding continues. On LAN connections, padding
starts from the initial detection of a new neighbor until there is at least one
active adjacency on the interface.
• Loose—(Default) The hello packet is padded from the initial detection of a
new neighbor until the adjacency transitions to the Up state.
• Strict—Padding is performed on all interface types and for all adjacency
states, and is continuous.
Hello padding
extensiveCurrent LDP synchronization state: in sync, in holddown, or not supported.LDP sync state
extensiveReason for being in the LDP sync state.reason
2695Copyright © 2017, Juniper Networks, Inc.
Chapter 42: Operational Commands