Juniper EX9200 Features Manual page 124

Network Management and Monitoring Feature Guide for EX9200 Switches
Table 8: show interfaces Fast Ethernet Output Fields (continued)
Field Name Field Description
Output errors on the interface. The following paragraphs explain the counters
Output errors
whose meaning might not be obvious:
Carrier transitions
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
Drops
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
Collisions
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
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
ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
HS link CRC errors
ASICs responsible for handling the router interfaces.
MTU errors
Resource errors
Total number of egress queues supported on the specified interface.
Egress queues
NOTE:
20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a discrepancy in the
output of the
counted in the Egress queues section of the output. This problem occurs on
non-enhanced DPCs because the egress queue statistics are polled from IMQ
(Inbound Message Queuing) block of the I-chip. The IMQ block does not
differentiate between ingress and egress WAN traffic; as a result, the combined
statistics are displayed in the egress queue counters on the Routing Engine. In
a simple VPLS scenorio, if there is no MAC entry in DMAC table (by sending
unidirectional traffic), traffic is flooded and the input traffic is accounted in IMQ.
For bidirectional traffic (MAC entry in DMAC table), if the outgoing interface is
on the same I-chip then both ingress and egress statistics are counted in a
combined way. If the outgoing interface is on a different I-chip or FPC, then only
egress statistics are accounted in IMQ. This behavior is expected with
non-enhanced DPCs
CoS queue number and its associated user-configured forwarding class name.
Queue counters
(Egress)
Queued packets
Transmitted packets
Dropped packets
108
—Number of times the interface has gone from
—Sum of the outgoing frame aborts and FCS errors.
—Number of packets dropped by the output queue of the I/O Manager
—Number of Ethernet collisions. The Gigabit Ethernet PIC supports
—Number of packets that remained in shared packet SDRAM
—Number of FIFO errors in the send direction as reported by the
—Number of errors on the high-speed links between the
—Number of packets whose size exceeded the MTU of the interface.
—Sum of transmit drops.
In DPCs that are not of the enhanced type, such as DPC 40x 1GE R, DPCE
command because incoming packets might be
show interfaces
—Number of queued packets.
—Number of transmitted packets.
—Number of packets dropped by the ASIC's RED mechanism.
Level of Output
extensive
to .
down up
detail extensive
detail extensive
Copyright © 2016, Juniper Networks, Inc.