Week 4 · Lesson 8

Interface and Cable Troubleshooting

Most of the network is fine most of the time — and when it is not, the fault is disproportionately often at Layer 1. A single bad patch cable, a mismatched duplex setting, or a run that is just a few metres too long can produce symptoms that look like anything but a cabling problem. This lesson teaches you to read the interface counters that name the fault, and to know the tool for each layer of the problem.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Part 1

Reading interface state first

Before you chase counters, read the first line of show interfaces. It reports two independent things: the interface status (Layer 1, is there a signal?) and the line protocol status (Layer 2, does the framing and keepalive work?). The pairing tells you instantly which layer to attack.

SW1# show interfaces status
Port      Name    Status       Vlan       Duplex  Speed Type
Gi0/1             connected    10           full   1000 1000BaseTX
Gi0/2             notconnect   1            auto   auto 10/100/1000BaseTX
Gi0/3             err-disabled 1            auto   auto 10/100/1000BaseTX
InterfaceLine protocolMeaning and first move
upupHealthy. If users still complain, the fault is higher up the stack.
downdownLayer 1. No signal: cable unplugged, bad cable, dead NIC, wrong port.
updownLayer 2. Signal is present but framing/keepalive fails: encapsulation, VLAN, or protocol mismatch.
administratively downdownThe port was shut down in configuration; run no shutdown.
Exam tip. Memorise the pairing. “up/down” is a Layer 2 problem; “down/down” is a Layer 1 problem; “administratively down” means someone typed shutdown. An exam question that hands you line protocol is down alongside interface is up is testing whether you look one layer above the cable.
What do the states tell you? · select an interface status

Part 2

Collisions and late collisions

A collision happens when two devices on a shared, half-duplex segment transmit at the same time and their signals overlap. A small number of collisions is normal and expected on a healthy half-duplex segment — it is how CSMA/CD shares the medium. On a full-duplex link, however, collisions should be exactly zero, because each direction has its own path. Collisions on a full-duplex port are therefore a symptom, not normal behaviour.

A late collision is more serious. CSMA/CD can detect a collision only during the first 64 bytes (the slot time) of a frame; once a station has transmitted past that point it has effectively won the medium. A collision that arrives after the 64th byte is a late collision, and the frame is already lost. Late collisions almost always point to one of two things:

Definition — late collision. A frame collision detected after the first 64 bytes have been transmitted. Because the slot time has passed, CSMA/CD cannot recover cleanly. Late collisions are the fingerprint of a duplex mismatch or an over-long cable segment.
Part 3

Duplex mismatch: the classic fault

A duplex mismatch occurs when the two ends of a link disagree: one is configured (or negotiated) full duplex, the other half duplex. The behaviour is asymmetric, and that asymmetry is the clue.

The user-visible effect is severe slowness, not a dead link. The link comes up, ping may work, but throughput collapses under load because frames keep being destroyed. The fix is to make both ends agree: either set both to auto autonegotiation (preferred) or set both to the same explicit speed and duplex. Setting only one end manually is what creates the mismatch.

SW1 Gi0/1 configured FULL duplex reports: CRC, runts, FCS errors SW2 Gi0/1 configured HALF duplex reports: collisions, LATE collisions duplex mismatch: same link, two different rules The cure: autonegotiate both ends, or fix both ends to the same speed and duplex

A duplex mismatch is asymmetric. SW2, running half duplex, sees collisions and late collisions; SW1, running full duplex, sees CRC and runt errors because it receives corrupted frames while transmitting. The cure is to make both ends autonegotiate, or to fix both ends to the same speed and duplex.

Duplex mismatch · build the link and read the counters

Part 4

CRC/FCS errors, runts, and giants

Ethernet appends a Frame Check Sequence (FCS) — a CRC value — to every frame. The receiver recomputes it, and a mismatch means the frame was corrupted in transit. The switch drops the frame and increments a CRC (sometimes called FCS) error counter.

Note. The IEEE 802.3 maximum frame is 1518 bytes (1522 bytes with an 802.1Q tag), and the minimum is 64 bytes. Anything outside that window is by definition a runt or a giant and is counted as an input error.
Frame size window · move the slider
64 bytes min 1518 bytes max
1500 bytes Valid frame

Part 5

Input and output errors

Cisco interface counters group the physical errors into two buckets. Input errors are problems with frames the interface received; output errors are problems with frames it tried to transmit.

BucketCounters insideTypical cause
Input errorsrunts, giants, CRC, frame, overrun, ignored, no bufferDamaged cable, bad connector, EMI, duplex mismatch, NIC fault, overrun
Output errorscollisions, late collisions, deferred, output buffer failuresShared/half-duplex congestion, duplex mismatch, over-driven port
SW1# show interfaces gigabitethernet 0/1
GigabitEthernet0/1 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 001b.0c00.0001
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
     47 input errors, 41 CRC, 0 frame, 0 overrun, 0 ignored
     0 output errors, 0 collisions, 2 interface resets
     0 late collisions, 0 deferred
SW1# show interfaces counters errors
Port        Align-Err    FCS-Err   Xmit-Err    Rcv-Err  UnderSize  OutDiscards
Gi0/1              0         41          0         47          0            0
Gi0/2              0          0          0          0          0            0

show interfaces counters errors compresses every port into one line, which makes it the fastest way to sweep a whole switch for the one misbehaving port. show controllers goes deeper into the physical chip for serial and some optical interfaces, while show interfaces transceiver reports optical transmit/receive power and temperature for SFP modules — invaluable when a fibre link’s light level is marginal.

Memory hook. Input errors = what arrived broken (runts, giants, CRC, frame, overrun, ignored, no buffer). Output errors = what could not be sent cleanly (collisions, late collisions, deferred, output buffer failures). Runts and giants are always input errors; collisions and late collisions are always output errors.
Part 6

Speed mismatch, EMI, and attenuation

Speed mismatch. If one end is hard-set to 100 Mbps and the other to 1000 Mbps, autonegotiation cannot agree. The result is usually a link that fails to come up at all (down/down) or one that comes up at the lower speed with errors. The rule is the same as for duplex: let both ends autonegotiate, or set both ends identically.

Electromagnetic interference (EMI). Motors, fluorescent ballasts, power cables, and radio transmitters can induce noise onto a copper cable. Twisted pairs twist precisely to cancel interference, and shielded twisted pair (STP) adds a foil or braid shield, but a cable routed alongside high-voltage wiring will still suffer. EMI shows up as random CRC/FCS errors that grow with the amount of nearby electrical activity.

Attenuation. Every cable weakens a signal with distance. Copper Ethernet is specified to 100 metres precisely because beyond that the signal has attenuated too far to be reliably decoded. Symptoms of over-long runs are CRC errors and intermittent link drops that worsen over time as connectors age. Fibre attenuates far more slowly, which is why it is used for long runs, but it too has distance limits and can be damaged by tight bends.

Watch out. A single “random” CRC error is noise; a counter that keeps climbing is a fault. Always clear the counters (clear counters) and watch them over a few minutes before drawing a conclusion — a count that has sat unchanged for months may be ancient history.
Part 7

Cable problems, length limits and the tools to diagnose them

Beyond the signal itself, the physical cable is the usual suspect. The faults you must recognise:

The right tool matches the layer you are testing. Match each symptom to its instrument:

Tool / commandWhat it doesUse it for
show interfacesStatus, line protocol, speed/duplex, and all countersFirst look at any interface problem
show interfaces counters errorsOne line per port of error totalsSweeping the switch for the faulty port
show controllersPhysical-layer chip detail (cable, clocking, signalling)Serial/optical physical faults
show interfaces transceiverOptical power, temperature, and diagnosticsMarginal or failing fibre links
Cable tester / wiremapChecks each pair, continuity, and pinoutBad crimps, wrong pinouts, opens and shorts
Time-domain reflectometer (TDR)Sends a pulse and times the reflectionLocating a break or the distance to a fault in copper
OTDR (optical TDR)The fibre equivalent of a TDRLocating breaks, splices, and bends in fibre
Loopback plugLoops transmit back to receiveTesting a single port in isolation
Toner and probeTraces a cable through a bundle by injected toneIdentifying which cable is which in a patch panel
Tip. Work top-down when you can and bottom-up when you must. If a whole VLAN is unreachable, suspect configuration. If one device or one run is failing, go straight to Layer 1: check the link light, then show interfaces, then show interfaces counters errors, then swap the patch cable. Swapping a $2 cable solves more tickets than any console session.
Symptom to tool · pick the symptom

Key terms

Part 8 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco. Troubleshooting Ethernet and Interface Errors (collisions, late collisions, CRC, runts, giants). cisco.com.
  2. Cisco. CCNA (200-301) Exam Topics, Network Fundamentals — troubleshoot interfaces and cabling. cisco.com.
  3. IEEE. IEEE 802.3: Ethernet (frame size, FCS, and CSMA/CD). standards.ieee.org.
  4. Cisco. CCNA: Introduction to Networks — “Network Media” and “Network Troubleshooting”. netacad.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.