Study Cabling, Interface & Hardware Issues for Network+ (N10-009)
Recognize what bad cable type, poor termination, transceiver mismatch, low signal strength, or failing hardware looks like on the wire.
Physical troubleshooting questions are evidence questions. CompTIA wants to know whether you can recognize the clues that point to cable damage, poor termination, transceiver mismatch, or failing hardware before you start blaming routing or services. A link light alone is not enough evidence.
CRC error: A frame-check failure that can indicate corruption on the link or medium.
Optical transceiver: A removable module such as
SFPorSFP+that connects a switch or router interface to fiber media.
What CompTIA is really testing
The exam usually wants you to separate:
- physical-medium problems from logical-path problems
- interface-counter evidence from user symptom language
- port or optics mismatch from upstream routing failure
- intermittent hardware degradation from total device failure
Read the interface evidence first
1Gi1/0/12 is up, line protocol is up
2input errors 57, CRC 42, frame 9
3output errors 0
What to notice:
- the interface being “up” does not mean the link is healthy
- CRC and frame errors suggest the medium or physical signaling deserves investigation
- this is stronger evidence for a link-quality problem than for a DNS or routing problem
Common physical-layer causes
| Symptom or clue | Stronger first suspect |
|---|---|
| CRC errors, unstable link | damaged cable, bad termination, interference, optics issue |
| no link light | disconnected cable, wrong port, dead interface, power issue |
| mismatched speed or duplex behavior | negotiation issue, forced mismatch, bad legacy config |
| fiber link will not establish | wrong transceiver, polarity problem, wavelength or fiber-type mismatch |
| repeated intermittent drops | failing NIC, bad patch lead, loose connection, environmental issue |
Link lights are only one clue
CompTIA likes this trap:
“The port light is on, so the cable must be fine.”
That is weak reasoning. A port can show link while still producing:
- corruption
- negotiation mismatch
- intermittent drops
- low-quality optical signaling
Small escalation sequence
- Check interface status and counters.
- Confirm cable, connector, and transceiver type.
- Swap the simplest suspect component first.
- Re-test and compare counters or behavior.
That sequence is stronger than replacing upstream network services when the evidence is still local to the link.
Common traps
- assuming link lights prove the physical layer is healthy
- blaming routing when counters point to bad media
- forgetting that transceiver and fiber mismatches are common real-world causes
- changing several physical components at once and losing the true cause
What strong answers usually do
- use counters and interface status before escalating to higher layers
- connect CRC, drops, and negotiation clues to the medium first
- swap the smallest likely component before replacing larger devices
- keep physical evidence separate from user descriptions like “the network is slow”
Quiz
Continue with 5.3 Network Services, Routing & Switching Issues to keep the domain flow intact.