NetworkingNetwork+

Physical Layer Troubleshooting for CompTIA Network+ N10-009

Physical layer (Layer 1) issues cause the most fundamental network problems — no link, intermittent connectivity, and high error rates. CompTIA Network+ N10-009 tests physical layer troubleshooting in the Troubleshooting domain. Physical problems are often overlooked in favor of software fixes — the first step in systematic troubleshooting is always confirming physical layer health.

7 min

2 sections · 7 exam key points

1 practice questions

Common Physical Layer Symptoms and Causes

No link light: the interface LED is off or amber (fault) when it should be green. Causes: unplugged or damaged cable, faulty NIC, faulty switch port, wrong cable type (straight-through vs crossover — rarely an issue with modern Auto-MDI/MDIX). Test: try a different cable, try a different switch port, test the cable with a cable tester.

Intermittent connectivity: the link goes up and down repeatedly. Causes: loose cable connection, bent or partially broken cable, SFP transceiver issue (dirty or damaged fiber connector), EMI (electromagnetic interference from power cables, motors, fluorescent lights). Test: TDR/cable certifier to check cable quality, check cable routing (separation from power cables).

CRC errors / FCS errors: frames arrive with corrupted data. Causes: physical cable damage (bent, kinked, over-crimped), exceeding maximum cable distance, cable Category insufficient for speed (Cat5 for 10G), bad SFP transceiver, EMI interference, duplex mismatch (runts in half-duplex). Check: interface error counters on the switch port (show interface on Cisco).

Runts: frames shorter than 64 bytes — typically caused by collisions in half-duplex environments or duplex mismatch. Giants: frames larger than 1518 bytes (or the configured MTU) — caused by MTU misconfiguration or VLAN tagging issues on trunk ports.

Fiber Optic Physical Issues

Dirty fiber connectors: the most common cause of fiber connectivity problems. Even fingerprints or dust on a fiber end-face cause significant signal loss. Use inspection scopes and fiber cleaning tools (one-click cleaners) before connecting. Never look directly into a fiber connector — laser sources can damage eyes.

Bend radius violation: fiber optic cables have a minimum bend radius — bending too tightly causes internal reflections and signal loss. Visible to OTDR as a loss event at the bend location. Route fiber carefully without tight bends or kinks.

Wrong fiber type: single-mode transceiver with multimode fiber (or vice versa) causes severely degraded signal. Verify fiber type matches transceiver specifications. Connector mismatch: SC-to-LC adapter required when different connector types need to interconnect.

Key exam facts — Network+

No link light: check cable, NIC, switch port — replace/swap to isolate
CRC errors: physical damage, EMI, exceeding cable distance, duplex mismatch
Runts (< 64 bytes): collisions or duplex mismatch; Giants (> 1518): MTU issue
Intermittent link: loose connector, partially broken cable, EMI
Fiber: dirty connectors most common cause; use inspection scope and cleaner
Cable tester: basic continuity; TDR: locates fault by distance; OTDR: fiber faults
Duplex mismatch: half-duplex side generates runts and CRC errors

Common exam traps

If the cable looks undamaged externally, it's not the problem

Internal conductor breaks, improper crimping, and bent pairs are invisible externally but cause CRC errors and intermittent connectivity. A cable tester or TDR is required to confirm cable integrity

Practice questions — Physical Layer Issues

These questions are representative of what you will see on Network+ exams. The correct answer and explanation are shown immediately below each question.

Q1.A switch interface shows increasing CRC errors and runts, but the link light is green. What is the most likely cause?

A.VLAN misconfiguration

B.Duplex mismatch between the switch and connected device

C.Incorrect IP address configuration

D.DHCP scope exhaustion

Explanation: Runts (short frames) and CRC errors with a green link light are classic symptoms of a duplex mismatch. The full-duplex side transmits while the half-duplex side is also transmitting — the half-duplex side detects this as a collision, generating runts. CRC errors result from corrupted frames. Check duplex settings on both ends: the switch port and the connected device.

Frequently asked questions — Physical Layer Issues

How do I tell if a switch port has duplex mismatch?

On a Cisco switch, 'show interface GigabitEthernet0/1' shows speed and duplex, late collisions counter (only increments in half-duplex, not full), and input/output error counts. A mismatch shows: one side is auto-negotiated full-duplex, the other is hard-coded half-duplex. Increasing late collisions, runts, and CRC errors confirm the mismatch. Fix: configure both ends to the same speed and duplex (preferably both auto-negotiate).

Practice this topic

Network+practice questions

Test yourself on Physical Layer Issues

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

Free practice test Start 7-Day Free Trial

No credit card · Cancel anytime