Technical Documentation

Common Output Fields Description

This chapter explains the content of the output fields, which appear in the output of most show interfaces commands.

Destination Class Field

For the logical interface, the Destination class field provides the names of destination class usage (DCU) counters per family and per class for a particular interface. The counters display packets and bytes arriving from designated user-selected prefixes. For example:

                                           Packets                           Bytes
Destination class              	(packet-per-second)               (bits-per-second)
               
             gold                     	   1928095	                 161959980
                               (               889)                (   597762)
            bronze                               0                          0
                               (                 0)                (        0)
            silver                               0                          0
                               (                 0)                (        0)

Enabled Field

For the physical interface, the Enabled field provides information about the state of the interface, displaying one or more of the following values:

  • Administratively down, Physical link is Down—The interface is turned off, and the physical link is inoperable and cannot pass packets even when it is enabled.
  • Administratively down, Physical link is Up—The interface is turned off, but the physical link is operational and can pass packets when it is enabled.
  • Enabled, Physical link is Down—The interface is turned on, but the physical link is inoperable and cannot pass packets.
  • Enabled, Physical link is Up—The interface is turned on, and the physical link is operational and can pass packets.

Filters Field

For the logical interface, the Filters field provides the name of the firewall filters to be evaluated when packets are received or transmitted on the interface. The format is Filters: Input: filter-name and Filters: Output: filter-name. For example:

Filters: Input: sample-allFilters: Output: cp-ftp

Flags Fields

The following sections provide information about flags that are specific to interfaces:

Addresses, Flags Field

The Addresses, Flags field provides information about the addresses configured for the protocol family on the logical interface and displays one or more of the following values:

  • Dest-route-down—The routing process detected that the link was not operational and changed the interface routes to nonforwarding status
  • Is-Default—The default address of the router used as the source address by SNMP, ping, traceroute, and other network utilities.
  • Is-Preferred—The default local address for packets originating from the local router and sent to destinations on the subnet.
  • Is-Primary—The default local address for broadcast and multicast packets originated locally and sent out the interface.
  • Preferred—This address is a candidate to become the preferred address.
  • Primary—This address is a candidate to become the primary address.

Device Flags Field

The Device flags field provides information about the physical device and displays one or more of the following values:

  • Down—Device has been administratively disabled.
  • Hear-Own-Xmit—Device receives its own transmissions.
  • Link-Layer-Down—The link-layer protocol has failed to connect with the remote endpoint.
  • Loopback—Device is in physical loopback.
  • Loop-Detected—The link layer has received frames that it sent, thereby detecting a physical loopback.
  • No-Carrier—On media that support carrier recognition, no carrier is currently detected.
  • No-Multicast—Device does not support multicast traffic.
  • Present—Device is physically present and recognized.
  • Promiscuous—Device is in promiscuous mode and recognizes frames addressed to all physical addresses on the media.
  • Quench—Transmission on the device is quenched because the output buffer is overflowing
  • Recv-All-Multicasts—Device is in multicast promiscuous mode and therefore provides no multicast filtering.
  • Running—Device is active and enabled.

Family Flags Field

The Family flags field provides information about the protocol family on the logical interface and displays one or more of the following values:

  • DCU—Destination class usage is enabled.
  • Dest-route-down—The software detected that the link is down and has stopped forwarding the link's interface routes.
  • Down—Protocol is inactive.
  • Is-Primary—Interface is the primary one for the protocol.
  • Mac-Validate-Loose—Interface is enabled with loose MAC address validation.
  • Mac-Validate-Strict—Interface is enabled with strict MAC address validation.
  • Maximum labels—Maximum number of MPLS labels configured for the MPLS protocol family on the logical interface.
  • MTU-Protocol-Adjusted—The effective MTU is not the configured value in the software.
  • No-Redirects—Protocol redirects are disabled.
  • Primary—Interface can be considered for selection as the primary family address.
  • Protocol-Down—Protocol failed to negotiate correctly.
  • SCU-in—Interface is configured for source class usage input.
  • SCU-out—Interface is configured for source class usage output.
  • send-bcast-packet-to-re—Interface is configured to forward IPv4 broadcast packets to the Routing Engine.
  • targeted-broadcast—Interface is configured to forward IPv4 broadcast packets to the LAN interface and the Routing Engine.
  • Unnumbered—Protocol family is configured for unnumbered Ethernet. An unnumbered Ethernet interface borrows an IPv4 address from another interface, which is referred to as the donor interface.
  • Up–Protocol is configured and operational.
  • uRPF—Unicast Reverse Path Forwarding is enabled.

Interface Flags Field

The Interface flags field provides information about the physical interface and displays one or more of the following values:

  • Admin-Test—Interface is in test mode and some sanity checking, such as loop detection, is disabled.
  • Disabled—Interface is administratively disabled.
  • Down—A hardware failure has occurred.
  • Hardware-Down—Interface is nonfunctional or incorrectly connected.
  • Link-Layer-Down—Interface keepalives have indicated that the link is incomplete.
  • No-Multicast—Interface does not support multicast traffic.
  • No-receive No-transmit—Passive monitor mode is configured on the interface.
  • Point-To-Point—Interface is point-to-point.
  • Pop all MPLS labels from packets of depth—MPLS labels are removed as packets arrive on an interface that has the pop-all-labels statement configured. The depth value can be one of the following:
    • 1—Takes effect for incoming packets with one label only.
    • 2—Takes effect for incoming packets with two labels only.
    • [ 1 2 ]—Takes effect for incoming packets with either one or two labels.
  • Promiscuous—Interface is in promiscuous mode and recognizes frames addressed to all physical addresses.
  • Recv-All-Multicasts—Interface is in multicast promiscuous mode and provides no multicast filtering.
  • SNMP-Traps—SNMP trap notifications are enabled.
  • Up—Interface is enabled and operational.

The Link flags field provides information about the physical link and displays one or more of the following values:

  • ACFC—Address control field compression is configured. The Point-to-Point Protocol (PPP) session negotiates the ACFC option.
  • Give-Up—Link protocol does not continue connection attempts after repeated failures.
  • Loose-LCP—PPP does not use the Link Control Protocol (LCP) to indicate whether the link protocol is operational.
  • Loose-LMI—Frame Relay does not use the Local Management Interface (LMI) to indicate whether the link protocol is operational.
  • Loose-NCP—PPP does not use the Network Control Protocol (NCP) to indicate whether the device is operational.
  • No-Keepalives—Link protocol keepalives are disabled.
  • PFC—Protocol field compression is configured. The PPP session negotiates the PFC option.

Logical Interface Flags Field

The Logical interface flags field provides information about the logical interface and displays one or more of the following values:

  • ACFC Encapsulation—Address control field Compression (ACFC) encapsulation is enabled (negotiated successfully with a peer).
  • Device-down—Device has been administratively disabled.
  • Disabled—Interface is administratively disabled.
  • Down—A hardware failure has occurred.
  • Clear-DF-Bit—GRE tunnel or IPsec tunnel is configured to clear the Don't Fragment (DF) bit.
  • Hardware-Down—Interface protocol initialization failed to complete successfully.
  • PFC—Protocol field compression is enabled for the PPP session.
  • Point-To-Point—Interface is point-to-point.
  • SNMP-Traps—SNMP trap notifications are enabled.
  • Up—Interface is enabled and operational.

Label-Switched Interface Traffic Statistics Field

When you use the vrf-table-label statement to configure a VRF routing table, a label-switched interface (LSI) logical interface label is created and mapped to the VRF routing table.

Any routes present in a VRF routing table and configured with the vrf-table-label statement are advertised with the LSI logical interface label allocated for the VRF routing table. When packets for this VPN arrive on a core-facing interface, they are treated as if the enclosed IP packet arrived on the LSI interface and are then forwarded and filtered based on the correct table. For more information on the vrf-table-label statement, including a list of supported interfaces, see the JUNOS VPNs Configuration Guide.

If you configure the family mpls statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level and you also configure the vrf-table-label statement at the [edit routing-instances routing-instance-name] hierarchy level, the output for the show interface interface-name extensive command includes the following output fields about the LSI traffic statistics:

  • Input bytes—Number of bytes entering the LSI and the current throughput rate in bits per second (bps).
  • Input packets—Number of packets entering the LSI and the current throughput rate in packets per second (pps).

The following example shows the LSI traffic statistics that you might see as part of the output of the show interface interface-name extensive command:

Label-switched interface (LSI) traffic statistics:   Input bytes:                        0                 0 bps   Input packets:                    0                 0 pps

Policer Field

For the logical interface, the Policer field provides the policers that are to be evaluated when packets are received or transmitted on the interface. The format is Policer: Input: type-fpc/picport-in-policer, Output: type-fpc/pic/port-out-policer. For example:

Policer: Input: at-1/2/0-in-policer, Output: at-2/4/0-out-policer

Protocol Field

For the logical interface, the Protocol field indicates the protocol family or families that are configured on the interface, displaying one or more of the following values:

  • aenet—Aggregated Ethernet. Displayed on Fast Ethernet interfaces that are part of an aggregated Ethernet bundle.
  • ccc—Circuit cross-connect (CCC). Configured on the logical interface of CCC physical interfaces.
  • inet—IP version 4 (IPv4). Configured on the logical interface for IPv4 protocol traffic, including Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), Internet Control Message Protocol (ICMP), and Internet Protocol Control Protocol (IPCP).
  • inet6—IP version 6 (IPv6). Configured on the logical interface for IPv6 protocol traffic, including Routing Information Protocol for IPv6 (RIPng), Intermediate System-to-Intermediate System (IS-IS), and BGP.
  • iso—International Organization for Standardization (ISO). Configured on the logical interface for IS-IS traffic.
  • mlfr-uni-nni—Multilink Frame Relay (MLFR) FRF.16 user-to-network network-to-network (UNI NNI). Configured on the logical interface for link services bundling.
  • mlfr-end-to-end—Multilink Frame Relay end-to-end. Configured on the logical interface for multilink bundling.
  • mlppp—Multilink Point-to-Point Protocol (MLPPP). Configured on the logical interface for multilink bundling.
  • mpls—Multiprotocol Label Switching (MPLS). Configured on the logical interface for participation in an MPLS path.
  • tcc—Translational cross-connect (TCC). Configured on the logical interface of TCC physical interfaces.
  • tnp—Trivial Network Protocol (TNP). Used to communicate between the Routing Engine and the router’s packet forwarding components. The JUNOS Software automatically configures this protocol family on the router’s internal interfaces only.
  • vpls—Virtual private LAN service (VPLS). Configured on the logical interface on which you configure VPLS.

RPF Failures Field

For the logical interface, the RPF Failures field provides information about the amount of incoming traffic (in packets and bytes) that failed a unicast reverse path forwarding (RPF) check on a particular interface. The format is RPF Failures: Packets: xx,Bytes: yy. For example:

RPF Failures: Packets: 0, Bytes:0

Source Class Field

For the logical interface, the Source class field provides the names of source class usage (SCU) counters per family and per class for a particular interface. The counters display packets and bytes arriving from designated user-selected prefixes. For example:

                                                       Packets                                   BytesSource class                    (packet-per-second)                  (bits-per-second)                                                                                                                                               gold             1928095                        161959980                                           (                889)                 (           597762)                              bronze                        0                                        0                                           (                    0)                 (                     0)                                silver                         0                                        0                                           (                    0)                 (                     0)

Published: 2010-04-28