Users behind a router complain of slow file transfers. An engineer collects counters from both ends of the link between SW1 Gi1/0/3 and R1 Gi0/0/1:SW1# show interfaces gi1/0/3
Half-duplex, 100Mb/s, media type is 10/100/1000BaseTX
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 152 collisions, 0 interface resets
0 babbles, 87 late collision, 0 deferred
R1# show interfaces gi0/0/1
Full Duplex, 100Mbps, link type is auto, media type is RJ45
210 runts, 0 giants, 0 throttles
341 input errors, 341 CRC, 0 frame, 0 overrun, 0 ignoredWhat is the most likely cause?
Choose one.
A duplex mismatch produces different symptoms on each end of the same link.
The half-duplex end transmits when it senses the line idle and treats incoming frames during its transmission as collisions, many detected after the first 64 bytes (late collisions). The full-duplex end ignores carrier sense, so it transmits over the half-duplex end's frames, and the frames the half-duplex end aborts arrive truncated as runts or with bad FCS (CRC errors). Here the outputs show 'Half-duplex' versus 'Full Duplex' at the same 100 Mb/s, which rules out a speed mismatch; a damaged cable or over-length run would not explain the asymmetric counters.
- Compare the duplex and speed lines of both outputs.
- Note that speeds match but duplex differs.
- Match late collisions to the half-duplex end and CRC/runts to the full-duplex end.
- Conclude duplex mismatch and set both ends to the same duplex (preferably autonegotiate both).
Exam tip: Late collisions on one end plus CRC errors on the other end of the same link means duplex mismatch.
CCNA Interface and Cable Issues: Duplex, Errors, Copper and Fiber Troubleshooting — the lesson that teaches this.