Module 1.4 40 minIntermediate

When a link misbehaves — counters, duplex and speed

Even with the right IPs, a network can crawl or drop traffic because of L1 problems. This chapter teaches you to read 'show interfaces' counters, spot duplex/speed mismatches, and diagnose collisions versus runts versus CRC errors.

Sign up to read this chapter

What you'll learn

  • Identify duplex mismatch from interface counters.
  • Distinguish collisions, runts, giants, and CRC errors.
  • Decide when to set speed/duplex statically vs auto.

What 'show interfaces' tells you

New to networking? This is a troubleshooting chapter, and it is fine to read it quickly now and come back after Module 3, once you have built a few networks of your own. 'show interfaces' is the first command for a slow or flaky link. The top lines give the state ('is up, line protocol is up'), the MTU, and the duplex and speed the port is running at. The bottom block holds the counters: packets and bytes in and out, then the error counters this chapter decodes — input and output errors, CRC, frame, overrun, ignored, runts, giants, collisions and late collisions.

Counters accumulate from boot, or from the last time someone cleared them. So the useful habit is: 'clear counters', reproduce the problem, read again. A number on its own means little; a number that climbs while you watch is a live fault. The exhibit is real output from the NetForge lab, a healthy LAN port after a dozen pings.

R1 — a healthy LAN port
R1#show interfaces Gi0/0
GigabitEthernet0/0 is up, line protocol is up
  Hardware is Gigabit Ethernet, address is 02c0.ce2f.bd18 (bia 02c0.ce2f.bd18)
  Description: LAN to SW1
  Internet address is 192.168.5.1/24
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     12 packets input, 1176 bytes, 0 no buffer
     Received 0 broadcasts (0 multicasts), 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     12 packets output, 1176 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets

Duplex / speed mismatch — the most common L1 fault

If one side auto-negotiates and the other is hard-coded, the auto-side typically falls to half-duplex while the hard-coded side stays full. The link comes up, but you see late collisions on the half-duplex side and CRC errors and runts on the full-duplex side. The fix: either set both ends statically the same OR let both ends auto-negotiate. The sections below show why each of those things happens.

On a switched link, late collisions almost always mean a duplex mismatch. The other cause is a half-duplex segment that is too long: a cable run past 100 m, or a chain of hubs. Normal, early collisions only happen on half-duplex links.

10 more sections in this chapter, plus a 4-question quiz and a hands-on lab.

Account required

Create a free account to read Chapter 1.4 — When a link misbehaves — counters, duplex and speed

You can see the title, summary, and learning objectives. To read the chapter and build the labs, create a free account — Module 1 is fully readable on the free plan.

  • Read every chapter in Module 1 — How Networks Work
  • Save labs of up to 5 devices
  • Save up to 3 topologies
  • See the full course syllabus + chapter titles

Free account · no card required · compare plans any time

Build it step by step