Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.4. Interface and Cable Issues

💡 First Principle: Interface problems fall into two categories: physical layer issues (cables, connectors, optics) and configuration mismatches (speed, duplex). Think of it like car trouble: the symptoms might look similar, but you wouldn't replace the engine for a flat tire. The show interfaces command reveals which category you're dealing with.

Imagine this troubleshooting scenario: A user reports their network is "slow." You check their switchport and see: CRC: 2847, late collisions: 245. Your instinct says "bad cable"—you swap it. No improvement. You swap the patch panel port. No improvement. Finally you notice the switchport is stuck at half-duplex while the user's NIC negotiated full-duplex. Hours wasted because you didn't read the counters correctly. Note which side shows the evidence: collision counters only ever increment on the HALF-duplex end, because full duplex disables collision detection entirely.

What happens when you misdiagnose: Physical problems require hardware replacement. Configuration problems require settings changes. Replacing hardware for a configuration problem wastes time and money. Changing settings for a physical problem does nothing. The counters tell you which direction to go.

Common Issues and Indicators:
IssueSymptomsshow interfaces Evidence
CollisionsShared media contentionHigh collision counter
Late collisionsDuplex mismatch, or a segment longer than the collision domain allowsLate collision counter > 0 on the half-duplex side
CRC errorsBad cable, interference, bad NICCRC errors, input errors
Duplex mismatchOne side full, other halfHigh collisions + CRC errors
Speed mismatchInterface down or errorsInterface may show down
Input/output queue dropsCongestion—more traffic than the interface or CPU can handleDrop counters climb while CRC/collision counters stay at 0

Duplex Mismatch Scenario: When one side is set to full duplex and the other to half duplex, the full-duplex side transmits whenever it likes because it never checks for collisions. The half-duplex side therefore logs collisions—many of them late collisions—and aborts frames mid-transmission, and the full-duplex side receives those cut-off frames as runts and CRC/FCS errors.

Switch# show interfaces gigabitEthernet 0/1
  Input errors: 153, CRC: 127, frame: 0
  Output errors: 0, collisions: 2847, late collision: 245

⚠️ Exam Trap: If you see late collisions on a switched network (not a hub), suspect duplex mismatch. Normal collisions shouldn't occur on a full-duplex switched port.

Reading interface status (show interfaces, show ip interface brief):

Status / ProtocolMeaningUsual fix
administratively down / downPort disabled with shutdownno shutdown
down / downLayer 1 problem: no or bad cable, far end off, speed mismatchCheck cabling and the far end
up / downLayer 1 works but Layer 2 fails: encapsulation or keepalive mismatch (common on serial links)Match encapsulation/keepalives on both ends
up / upWorking—
err-disabled (show interfaces status)Switch shut the port automatically after a violation (port security, BPDU Guard, etc.)Fix the cause, then shutdown/no shutdown or errdisable recovery

show interfaces <name> shows status and error counters; show running-config interface <name> shows only that interface's configuration.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned