Chapters0/30 ▾
0 of 30 lessons finished
- 1.Models, Media & Topologies0/5
- 2.IP Addressing, Subnetting & Routing0/5
- 3.Ports, Protocols & Services0/5
- 4.Network Operations0/5
- 5.Network Security0/5
- 6.Network Troubleshooting0/5
Chapter 6 · Lesson 3 of 5
Reading interface counters and port states
1 min read
| What you see | What it means |
|---|---|
| Late collisions and FCS errors on one side, runts and CRC errors on the other; ping fine, big transfers crawl | Duplex mismatch; set both ends to match, ideally both on autonegotiation |
| Rising output drops, zero CRC, runts and giants, utilization near 100% at peak | Egress congestion; add capacity or QoS |
| Rising CRC or FCS errors alone | Corruption on the medium, such as a damaged cable or EMI |
| Port err-disabled | The switch shut it for a violation such as port security, BPDU guard or flapping; remove the cause first |
| Port administratively down | A person shut it down |
| Port suspended | Link-aggregation settings do not match the rest of the bundle |
Runts are frames under the 64-byte minimum and giants are frames over the maximum size, so neither appears when the only problem is a full queue. Drops are counted when a frame arrives for a buffer that is already full.
Check yourself
1. A server connects to a switch over a 40 m certified copper run. Ping between the two succeeds with normal round-trip times, but large file transfers crawl. The switch interface counters show a steadily rising late collision count and FCS errors, while the server NIC counters show runts and CRC errors. What is the most likely cause?
2. A technician reads an interface summary on a building uplink: 'input errors 0, CRC 0, runts 0, giants 0, output drops 184532', and utilization peaks at 98 percent every afternoon while the link stays up. What do these counters prove?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
CompTIA Network+ cheat sheet: every key fact on one page →