Network Infrastructure and Connectivity · Topic 1 of 9
Interface and Cable Issues
Diagnose copper and fiber link faults: read interface status, CRC and collision counters, duplex and speed mismatches, signal levels, distance and pin out.
- 6 min
- up/up is healthy. down/down is Layer 1. administratively down means
shutdown. up/down is Layer 2. - CRC means damaged frames: cable, interference, port or duplex mismatch.
- Runts are too short and giants are too large. Late collisions mean duplex mismatch or an overlong cable.
What it is
When a link misbehaves, the fault is in the cable, the interface settings or the device at the other end.
Cisco devices keep status words and error counters that point to the cause, if you can read them. This objective is about diagnosing: you are shown output or symptoms and must name the fault.
The topic covers collisions, errors, duplex and speed, distance, fiber signal levels, pin out and cable types.
How it works
Start with interface status, read the counters, then check the settings and the physical layer at both ends.
Reading interface status
The first line of show interfaces gives the physical line status, then the line protocol (Layer 2).
| Status / protocol | Usual meaning |
|---|---|
| up / up | Working at Layers 1 and 2 |
| down / down | No signal: unplugged, bad cable, far end off, wrong fiber type |
| administratively down / down | Someone entered shutdown |
| up / down | Signal present but a Layer 2 problem, such as an encapsulation or keepalive mismatch |
On a switch, show interfaces status shows one line per port. The Status column reads connected, notconnect, disabled or err-disabled, and the Duplex and Speed columns show a-full and a-100 when the values were auto-negotiated.
Switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Gi0/1 connected 10 a-full a-1000 10/100/1000BaseTX
Gi0/2 notconnect 10 auto auto 10/100/1000BaseTX
Gi0/3 err-disabled 10 auto auto 10/100/1000BaseTX
Reading error counters
show interfaces GigabitEthernet0/1 prints the counters. This excerpt comes from the full-duplex side of a duplex mismatch:
2481 runts, 0 giants, 0 throttles
6892 input errors, 4411 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 3 interface resets
0 late collision, 0 deferred
- Input errors: the total of all receive errors.
- CRC: the frame arrived damaged, so the checksum failed. Causes are a bad cable, interference, a faulty port or a duplex mismatch.
- Runts: frames shorter than 64 bytes, often a result of collisions.
- Giants: frames above the maximum size, normally 1518 bytes (1522 with an 802.1Q tag).
- Collisions and late collisions: only possible on half duplex. A late collision happens after the first 64 bytes, which points to a duplex mismatch or a cable that is too long.
show interfaces counters errors gives a one line per port summary, with columns such as FCS-Err, Rcv-Err and UnderSize.
Run clear counters, then check again. A big number that never moves is old history. A number that rises while you watch is the active fault.
Speed and duplex mismatch
Auto-negotiation lets both ends agree on the best speed and duplex. Trouble starts when one end is hard-coded and the other is left on auto.
The auto end can usually sense the speed, but it cannot learn the duplex of a hard-coded partner, so it falls back to half duplex. If the hard-coded end is full duplex, you have a duplex mismatch.
The link stays up and a ping may work, but real traffic is slow. The half-duplex side counts collisions and late collisions. The full-duplex side counts CRC errors and runts.
A speed mismatch is simpler: the ends cannot agree and the link does not come up.
interface GigabitEthernet0/1
speed 100
duplex full
Never hard-code one side and leave the other on auto. Hard-code both to the same values, or leave both on auto.
Copper: distance, cable type and pin out
Twisted pair Ethernet reaches 100 meters per run, including patch cords. A longer run gives CRC errors, or a link that comes up at a lower speed.
Category matters too. Category 5e supports 1000BASE-T, and Category 6a supports 10GBASE-T over the full 100 meters.
The standard wiring is T568B on both ends of a straight-through cable. A crossover has T568B on one end and T568A on the other.
| Pin | T568B color | Used by 10/100 on a host or router NIC |
|---|---|---|
| 1 | white/orange | Transmit |
| 2 | orange | Transmit |
| 3 | white/green | Receive |
| 4 | blue | 1000BASE-T only |
| 5 | white/blue | 1000BASE-T only |
| 6 | green | Receive |
| 7 | white/brown | 1000BASE-T only |
| 8 | brown | 1000BASE-T only |
10 and 100 Mbps use only pins 1, 2, 3 and 6. Gigabit uses all four pairs, so a cable with a broken pair on pins 4, 5, 7 or 8 often links at 100 Mbps instead of 1000. Auto-MDIX, on by default on most switches, corrects a wrong straight-through or crossover choice. A switch port uses the opposite pairs from a host NIC, which is why straight-through works between them.
Many Catalyst switches can test copper with test cable-diagnostics tdr interface GigabitEthernet0/1, then show cable-diagnostics tdr interface GigabitEthernet0/1.
Fiber: type, distance and signal level
Fiber is a pair of strands, one for each direction. The transmit port at one end must connect to the receive port at the other.
| Fault | What you see |
|---|---|
| Transmit and receive swapped | down / down at both ends |
| Multimode module on single-mode cable (or reverse) | No link, or a very weak signal |
| Run longer than the module allows | Link down, or errors |
| Dirty or damaged connector, tight bend | Weak receive power, CRC errors |
| Single-mode run that is too short | Receive power too strong |
Typical reach: 1000BASE-SX over multimode up to 550 meters (50 micron fiber, less on 62.5 micron), and 1000BASE-LX over single-mode up to 10 kilometers. Both ends need matching modules.
Signal level is read from the transceiver:
show interfaces GigabitEthernet1/0/1 transceiver detail
The output lists transmit and receive power in dBm. Compare the receive value with the module's accepted range: too low means loss on the path (dirt, bend, distance), and too high means an overload that needs an attenuator.
Common mistakes
Reading old counters as a live fault. Clear the counters and watch whether they rise.
Blaming the cable first. A duplex mismatch produces the same errors, so check both ends before replacing anything.
Hard-coding only one side. That is the classic cause of a duplex mismatch.
Expecting a dead link from a duplex mismatch. The link stays up and the symptom is slow traffic.
What to remember for the exam
- up/up is healthy. down/down is Layer 1. administratively down means
shutdown. up/down is Layer 2. - CRC means damaged frames: cable, interference, port or duplex mismatch.
- Runts are too short and giants are too large. Late collisions mean duplex mismatch or an overlong cable.
- Collisions only occur on half duplex.
- A duplex mismatch shows collisions on the half side and CRC errors on the full side.
- Copper is 100 meters. Gigabit needs all four pairs.
- Fiber needs transmit connected to receive, matching module types, and receive power inside the module's range.
- Straight-through is T568B to T568B. Crossover is T568B to T568A.
Check yourself
Which counters appear on each side of a duplex mismatch?
The half-duplex side shows collisions and late collisions. The full-duplex side shows CRC errors and runts.
A copper link comes up at 100 Mbps although both ports support 1000 Mbps. What is a likely physical cause?
A damaged pair or a bad pin out, because gigabit needs all four pairs and 100 Mbps uses only pins 1, 2, 3 and 6.
A fiber link is down/down at both ends and the modules match. What do you check first?
Whether transmit and receive are swapped, then the connectors and the receive power in dBm.
Topic 1 of 9 in Network Infrastructure and Connectivity
Test yourself on Network Infrastructure and Connectivity
The full Cisco CCNA 200-301 v2.0 question bank has 1,242 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Cisco. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.