Octet

What is the difference between input errors, overruns, input queue drops and output drops?

Show the answer

Say this first

Input errors are frames that arrived damaged or malformed: CRC, runts, giants, framing. Overruns and ignored mean the frame was fine, but the receiving hardware or its buffers could not take it in time. Input queue drops on a router mean packets punted to the CPU arrived faster than it could process them. Output drops mean the egress queue was full: more traffic was aimed at the port than it could send, which is congestion, very often in short bursts.

Go deeper

CounterWherePoints to
CRC, frame, runts, giantsreceive, the frame is badcabling, optics, duplex, MTU
overrunreceive, the hardware FIFO filled before the frame moved to memorythe receiving device cannot keep up with line-rate bursts
ignored, no bufferreceive, no free bufferbursts, buffer shortage
Input queue drops (third number in Input queue)packets for the router's CPUtoo much punted traffic: control plane, ARP, packets not switched in hardware
Total output dropstransmit, egress queue fullcongestion: speed mismatch such as 10G into 1G, many-to-one, microbursts
output errors, underrunstransmit hardwarerare; hardware

Fault or capacity?

Output drops with no input errors anywhere on the path are capacity, not cabling. The answers are QoS (decide what gets dropped), more bandwidth, spreading load across links, or more buffer where the platform allows it.

Where the drops really are

show interfaces gives a total. Per-queue drops live in show policy-map interface on routers with a QoS policy, and in platform-specific queue commands on switches.

Traps

  • Sending someone to replace a cable because of output drops. Output drops are a capacity or burst problem.
How did you do?