show interfaces fabric

Physical interface

Name of the physical interface.

Enabled

State of the interface.

Type

Physical interface type; for example, Ethernet.

Interface index

Index number of the physical interface, which reflects its initialization sequence.

SNMP ifIndex

SNMP index number for the physical interface.

Link-level type

Encapsulation being used on the physical interface.

MTU

Maximum transmission unit size on the physical interface.

Clocking

Reference clock source.

Speed

Speed at which the interface is running.

Duplex

Duplex mode of the interface, either Full-Duplex or Half-Duplex.

MAC-REWRITE Error

Specifies if the encapsulation of the packet has been changed.

BPDU Error

Specifies if a BPDU has been received on a blocked interface.

Loopback

Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback: Local or Remote.

Source filtering

Source filtering status: Enabled or Disabled.

Flow control

Flow control status: Enabled or Disabled. This field is only displayed if asymmetric flow control is not configured.

Device flags

Information about the physical device.

Interface flags

Information about the interface.

CoS queues

Number of CoS queues configured.

Hold-Times

Current interface hold-time up and hold-time down, in milliseconds.

Current address

Configured MAC address.

Hardware address

Hardware MAC address.

Last flapped

Date, time, and how long ago the interface went from down to up. The format is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second ago). For example, Last flapped: 2008–01–16 10:52:40 UTC (3d 22:58 ago).

Statistics last cleared

Date, time, and how long ago the statistics for the interface were cleared. The format is Statistics last cleared: year-month-day hour:minute:second:timezone (hour:minute:second ago). For example, 2010-05-17 07:51:28 PDT (00:04:33 ago).

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical interface.

• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.

• Input packets—Number of packets received on the interface.

• Output packets—Number of packets transmitted on the interface.

IPv6 transit statistics

If IPv6 statistics tracking is enabled, number of IPv6 bytes and packets received and transmitted on the logical interface:

• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.

• Input packets—Number of packets received on the interface.

• Output packets—Number of packets transmitted on the interface.

Input errors

Input errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious:

• Errors—Sum of the incoming frame terminated and FCS errors.

• Drops—Number of packets dropped by the input queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism.

• Framing errors—Number of packets received with an invalid frame checksum (FCS).

• Runts—Number of frames received that are smaller than the runt threshold.

• Policed discards—Number of frames that the incoming packet match code discarded because they were not recognized or not of interest. Usually, this field reports protocols that Junos OS does not handle.

• L3 incompletes—Number of incoming packets discarded because they failed Layer 3 sanity checks of the header. For example, a frame with less than 20 bytes of available IP header is discarded. L3 incomplete errors can be ignored if you configure the ignore-l3-incompletes statement.

• L2 channel errors—Number of times the software did not find a valid logical interface for an incoming frame.

• L2 mismatch timeouts—Number of malformed or short packets that caused the incoming packet handler to discard the frame as unreadable.

• FIFO errors—Number of FIFO errors in the receive direction that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning.

• Resource errors—Sum of transmit drops.

Output errors

Output errors on the interface. The following paragraphs explain the counters whose meaning might not be obvious:

• Carrier transitions—Number of times the interface has gone from down to up. This number does not normally increment quickly, increasing only when the cable is unplugged, the far-end system is powered down and then up, or another problem occurs. If the number of carrier transitions increments quickly (perhaps once every 10 seconds), the cable, the far-end system, or the PIC or PIM is malfunctioning.

• Errors—Sum of the outgoing frame terminated and FCS errors.

• Drops—Number of packets dropped by the output queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism.

• Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC supports only full-duplex operation, so for Gigabit Ethernet PICs, this number should always remain 0. If it is nonzero, there is a software bug.

• Aged packets—Number of packets that remained in shared packet SDRAM so long that the system automatically purged them. The value in this field should never increment. If it does, it is most likely a software bug or possibly malfunctioning hardware.

• FIFO errors—Number of FIFO errors in the send direction as reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning.

• HS link CRC errors—Number of errors on the high-speed links between the ASICs responsible for handling the fabric interfaces.

• MTU errors—Number of packets whose size exceeded the MTU of the interface.

• Resource errors—Sum of transmit drops.

Egress queues

Total number of egress queues supported on the specified interface.

Queue counters

CoS queue number and its associated user-configured forwarding class name.

• Queued packets—Number of queued packets.

• Transmitted packets—Number of transmitted packets.

• Dropped packets—Number of packets dropped by the ASIC's RED mechanism.

Input rate

Input rate in bits per second (bps) and packets per second (pps).

Output rate

Output rate in bps and pps.

Active alarms and Active defects

Ethernet-specific defects that can prevent the interface from passing packets. When a defect persists for a certain amount of time, it is promoted to an alarm. Based on the switch configuration, an alarm can ring the red or yellow alarm bell on the switch, or turn on the red or yellow alarm LED on the craft interface. These fields can contain the value None or Link.

• None—There are no active defects or alarms.

• Link—Interface has lost its link state, which usually means that the cable is unplugged, the far-end system has been turned off, or the PIC is malfunctioning.

MAC statistics

Receive and Transmit statistics reported by the PIC's MAC subsystem.

• Total octets and total packets—Total number of octets and packets. For Gigabit Ethernet IQ PICs, the received octets count varies by interface type.

• Unicast packets, Broadcast packets, and Multicast packets—Number of unicast, broadcast, and multicast packets.

• CRC/Align errors—Total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error).

• FIFO error—Number of FIFO errors that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning.

• MAC control frames—Number of MAC control frames.

• MAC pause frames—Number of MAC control frames with pause operational code.

• Oversized frames—Number of packets that exceed the configured MTU.

• Jabber frames—Number of frames that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. This definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition in which any packet exceeds 20 ms. The allowed range to detect jabber is from 20 ms to 150 ms.

• Fragment frames—Total number of packets that were less than 64 octets in length (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. Fragment frames normally increment because both runts (which are normal occurrences caused by collisions) and noise hits are counted.

• VLAN tagged frames—Number of frames that are VLAN tagged. The system uses the TPID of 0x8100 in the frame to determine whether a frame is tagged or not. This counter is not supported on EX Series switches and is always displayed as 0.

• Code violations—Number of times an event caused the PHY to indicate “Data reception error” or “invalid data symbol error.”

Packet Forwarding Engine Configuration

Information about the configuration of the Packet Forwarding Engine:

• Destination slot—FPC slot number.

• CoS transmit queue—Queue number and its associated user-configured forwarding class name.

• Bandwidth %—Percentage of bandwidth allocated to the queue.

• Buffer usec—Amount of buffer space allocated to the queue, in microseconds. This value is nonzero only if the buffer size is configured in terms of time.

• Priority—Queue priority: low or high.

• Limit—Displayed if rate limiting is configured for the queue. Possible values are none and exact. If exact is configured, the queue transmits only up to the configured bandwidth, even if excess bandwidth is available. If none is configured, the queue transmits beyond the configured bandwidth if bandwidth is available.

Item

Type of QFabric system component being viewed. Possible values include Node group, Interconnect device, Fabric control, Fabric manager, Diagnostic routing engine, and Ungrouped Node device.

Identifier

Hardware serial identifier of a QFabric system component. When you configure an alias name for a component, the ID is displayed.

Connection

Status of a QFabric system component: either Connected or Disconnected, depending on whether or not the Director software has detected keepalive messages for the listed component.

Configuration

Whether or not the configuration for a QFabric system component has been received and installed. The configuration can be Configured, Failed (unsuccessful), Pending (in the process of being written or retried), or Unknown.

Node group

Name of the Node groups associated with the QFabric system, and the Node devices assigned to each Node group. The group can be either Connected or Disconnected, depending on whether or not the Director software has detected keepalive messages for the devices in the group. This field also displays the serial ID for the Node group and the status for the Node group.

Fabric control

Name of the virtual Junos Routing Engines responsible for route selection within a QFabric system partition. The fabric control Routing Engine can be either Connected or Disconnected, depending on whether or not the Director software has detected keepalive messages for this virtual device. It also displays the identifier and configuration status for the fabric control Routing Engine.

Logical interface

Name of the logical interface.

Index

Index number of the logical interface, which reflects its initialization sequence.

SNMP ifIndex

SNMP interface index number for the logical interface.

Flags

Information about the logical interface.

If unicast Reverse Path Forwarding (uRPF) is explicitly configured on the specified interface, the uRPF flag appears. If uRPF was configured on a different interface (and therefore is enabled on all switch interfaces) but was not explicitly configured on the specified interface, the uRPF flag does not appear even though uRPF is enabled.

Encapsulation

Encapsulation method used on the logical interface.

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical interface.

• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.

• Input packets—Number of packets received on the interface.

• Output packets—Number of packets transmitted on the interface.

Local statistics

• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.

• Input packets—Number of packets received on the interface.

• Output packets—Number of packets transmitted on the interface.

Transit statistics

• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.

• Input packets—Number of packets received on the interface.

• Output packets—Number of packets transmitted on the interface.

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP address of the interface is also displayed.

Generation

Unique number for use by Juniper Networks technical support only.

Route table

Route table in which the logical interface address is located. For example, 0 refers to the routing table inet.0.