This chapter covers a NEW objective in the CCNA v2 exam (200-301 v2.0, 2026 blueprint): 'Copper and Fiber Cable Types, Distance Limits, and Interface Diagnostics.' Cisco added this to reflect the real-world importance of physical-layer troubleshooting—after all, if the cable is bad, no routing protocol can save you. You'll need to know the exact distance limits for UTP, multimode fiber, and single-mode fiber, plus how to use interface diagnostics like TDR and optical power monitoring. This is foundational for the 'Network Infrastructure and Connectivity' domain (25% of the exam) and essential for any network engineer who has ever crawled under a desk to check a loose cable.
Jump to a section
Imagine you need to send a fleet of delivery trucks from one city to another. You have two choices: a multi-lane highway (like copper Ethernet) or a dedicated, straight-shot express lane (like fiber optic). The highway has multiple lanes (twisted pairs) but is limited to 100 meters because after that, the traffic gets too congested—signal attenuation and interference degrade the data. If you try to extend the highway beyond 100 meters, trucks start getting lost (bit errors). Now consider the express lane: it's a single, laser-guided lane (fiber core) that can run for kilometers with no stops. But the express lane requires special trucks (optical transceivers) and has two types: a wider lane for short hauls (multimode fiber, up to 550 meters) and a narrower lane for ultra-long hauls (single-mode fiber, up to 40 km). If you use the wrong type of truck (transceiver) for the lane, your trucks will crash (no link). And just as a road inspector can use a reflectometer to find cracks in the pavement, a network engineer uses a TDR (Time Domain Reflectometer) on copper or an OTDR (Optical Time Domain Reflectometer) on fiber to find breaks or bad splices. The diagnostic tools (show commands) are like checking the speedometer and fuel gauge—they tell you if the physical path is healthy.
Why Cable Types Matter for the CCNA Exam
Cisco's 200-301 v2.0 exam now explicitly tests your understanding of physical media characteristics. You must know the distance limits for common Ethernet cabling: 100 meters for twisted-pair copper (Cat5e, Cat6, Cat6a), 550 meters for 1000BASE-SX (multimode fiber), and 5-40 km for 1000BASE-LX (single-mode fiber). These are not arbitrary numbers—they are determined by signal attenuation, dispersion, and the physics of the medium. The exam will ask you to select the correct cable for a given distance and speed requirement, or to interpret interface diagnostics to identify a faulty cable.
Copper Cabling: UTP and STP
Unshielded Twisted Pair (UTP) is the most common Ethernet cable. It uses four twisted pairs of copper wire with RJ-45 connectors. The twisting cancels electromagnetic interference (EMI). Categories matter: Cat5e supports 1000BASE-T (1 Gbps) up to 100 meters, Cat6 supports 10GBASE-T up to 55 meters (100 meters for 1 Gbps), and Cat6a supports 10GBASE-T up to 100 meters. Shielded Twisted Pair (STP) adds a foil shield for extra EMI protection, common in industrial environments. The absolute maximum distance for any twisted-pair Ethernet (10/100/1000/10G) is 100 meters—this is a hard limit due to signal degradation. Beyond 100 meters, you must use a repeater (switch) or fiber.
Fiber Optic Cabling: Multimode vs. Single-Mode
Fiber uses light pulses to transmit data. Multimode fiber (MMF) has a larger core (50 or 62.5 microns) allowing multiple light paths (modes). This causes modal dispersion, limiting distance. Typical limits: 1000BASE-SX (850 nm laser) up to 220-550 meters depending on fiber type (OM1, OM2, OM3, OM4). OM4 can reach 550 meters for 10 Gbps. Single-mode fiber (SMF) has a tiny core (9 microns) allowing only one mode, virtually eliminating dispersion. 1000BASE-LX (1310 nm laser) can reach 5 km, and 1000BASE-ZX (1550 nm) up to 70 km. For 10 Gbps, 10GBASE-LR reaches 10 km, 10GBASE-ER up to 40 km. The exam focuses on 1000BASE standards: -SX (MMF, 550m), -LX (SMF, 5km), and -ZX (SMF, 70km).
Interface Diagnostics: Show Commands and TDR
Cisco IOS provides several commands to diagnose physical layer issues. The most important for the exam:
show interfaces [interface] – Displays line protocol status, errors, and counters. Look for 'up/up' for a working interface. Errors like CRC, runts, giants indicate cable or duplex issues.
show interfaces [interface] transceiver – Shows optical transceiver details: wavelength, temperature, voltage, and optical power (Tx and Rx). For fiber, if Rx power is below the threshold, the link may be unreliable.
show interfaces [interface] transceiver detail – More detailed, including diagnostic monitoring data.
test cable-diagnostics tdr interface [interface] – Runs a Time Domain Reflectometer (TDR) test on copper cables. It detects cable faults (open, short, impedance mismatch) and estimates distance to the fault. Requires the interface to be in a down state.
Example output for TDR:
Router# test cable-diagnostics tdr interface gigabitethernet0/1
TDR test started on interface Gi0/1
Router# show cable-diagnostics tdr interface gigabitethernet0/1
Interface GigabitEthernet0/1
Pair 1: OK
Pair 2: Open, distance 45 meters
Pair 3: OK
Pair 4: Short, distance 12 metersThis tells you that Pair 2 has an open circuit 45 meters from the switch, and Pair 4 has a short at 12 meters. The cable is faulty and must be replaced.
Interaction with Higher Layers
Physical layer issues cause symptoms like intermittent connectivity, slow performance, or complete link loss. A bad cable can cause excessive CRC errors, leading to retransmissions at Layer 2 (Ethernet) and Layer 4 (TCP). The exam may present a scenario where 'show interfaces' shows increasing CRC errors but the link is up—this points to a cable issue (e.g., length too long, poor termination, EMI). Always check the cable before blaming the switch or router.
Key Values to Memorize
| Cable Type | Standard | Max Distance | |------------|----------|--------------| | Cat5e UTP | 1000BASE-T | 100 m | | Cat6 UTP | 10GBASE-T | 55 m (10G), 100 m (1G) | | Cat6a UTP | 10GBASE-T | 100 m | | MMF (OM3) | 1000BASE-SX | 550 m | | MMF (OM4) | 10GBASE-SR | 400 m | | SMF | 1000BASE-LX | 5 km | | SMF | 1000BASE-ZX | 70 km |
For the exam, remember: copper = 100m max, MMF = 550m max for 1G, SMF = 5km+ for 1G. If a question asks for a 2 km link at 1 Gbps, the answer is single-mode fiber with 1000BASE-LX.
Identify Cable Type Needed
Determine the required speed (e.g., 1 Gbps) and distance (e.g., 300 meters). For distances up to 100 meters, copper (Cat5e or better) is appropriate. For distances between 100 and 550 meters, use multimode fiber with 1000BASE-SX. For distances beyond 550 meters (up to 5 km), use single-mode fiber with 1000BASE-LX. For very long distances (up to 70 km), use 1000BASE-ZX. Always check the transceiver compatibility: the SFP module must match the fiber type (MMF vs SMF) and the connector (LC, SC).
Verify Interface Status
Use `show interfaces` to check if the interface is up/up. If it's down/down, the cable is likely disconnected or faulty. If it's up/down (line protocol down), there may be a Layer 1 issue like no carrier from the far end. Example: `Router# show interfaces gigabitethernet0/1` Look for 'GigabitEthernet0/1 is up, line protocol is up'. Also check counters for CRC errors, runts, giants, and collisions. High CRC errors indicate cable problems.
Check Transceiver Diagnostics
For fiber interfaces, use `show interfaces transceiver` to see optical power levels. Example output: `Router# show interfaces gigabitethernet0/1 transceiver` Look for 'Temperature', 'Voltage', 'Current', 'Tx Power', 'Rx Power'. Compare Rx Power to the threshold (usually -3 to -24 dBm for 1000BASE-LX). If Rx Power is too low (e.g., -30 dBm), the link may flap or not come up. Also check for 'Alarm' or 'Warning' flags. This command is critical for diagnosing fiber issues.
Run TDR on Copper Cables
If a copper interface is down or has errors, run a TDR test. First, ensure the interface is administratively down: `Router(config)# interface gigabitethernet0/1` then `Router(config-if)# shutdown`. Then execute: `Router# test cable-diagnostics tdr interface gigabitethernet0/1`. Wait a few seconds, then view results: `Router# show cable-diagnostics tdr interface gigabitethernet0/1`. The output shows each pair's status (OK, Open, Short) and the distance to the fault. This pinpoints the exact location of a break or short.
Interpret TDR Results
If a pair shows 'Open', the cable is broken at that distance (e.g., 45 meters). If 'Short', two wires are touching. If 'Impedance Mismatch', the cable has a bad termination or is damaged. If all pairs show 'OK', but the interface still has errors, the issue might be EMI, excessive length, or a faulty transceiver. Replace the cable if faults are found. For example, an open at 45 meters means the cable is cut or a connector is loose at that point.
Verify After Replacement
After replacing a faulty cable, re-enable the interface: `Router(config-if)# no shutdown`. Then use `show interfaces` to confirm the interface is up/up and error counters are not increasing. For fiber, also check `show interfaces transceiver` to ensure Rx power is within range. If the problem persists, check the far-end device and cable. Document the fix. This step confirms the physical layer is healthy before moving to Layer 2 troubleshooting.
Scenario 1: Campus Building Wiring Closet
A university has a building with wiring closets on each floor. They need to connect switches between floors. The distance between floors is about 150 meters. Copper is limited to 100 meters, so they must use fiber. The IT team runs multimode fiber (OM3) with 1000BASE-SX SFPs, supporting up to 550 meters—well within range. They terminate with LC connectors. After installation, one link fails to come up. Using show interfaces transceiver, they find Rx power is -28 dBm, below the threshold. Inspection reveals a dirty connector. Cleaning with a fiber optic cleaning tool restores the link. This scenario shows the importance of optical power monitoring.
Scenario 2: Data Center Server Connectivity
In a data center, servers are connected to top-of-rack switches with Cat6a copper cables for 10 Gbps. The maximum distance from server to switch is 30 meters, well within 100 meters. However, one server experiences intermittent connectivity. show interfaces shows high CRC errors. A TDR test reveals an impedance mismatch at 25 meters. The cable run passes through a cable management arm that is pinching the cable. Replacing the cable solves the issue. This demonstrates how TDR can locate physical damage without crawling through the rack.
Scenario 3: Remote Office WAN Link
An enterprise connects a remote office 2 km away using single-mode fiber with 1000BASE-LX SFPs. The link goes down. show interfaces transceiver shows no light (Rx power = -40 dBm). The fiber path includes a patch panel in the main building. An OTDR (external tool) identifies a break at 1.8 km, likely due to construction damage. The service provider repairs the fiber. This shows that beyond basic diagnostics, specialized tools like OTDR are needed for long fiber runs.
Common Mistakes
Using copper for distances >100 meters. This causes excessive attenuation and errors.
Mixing single-mode and multimode fiber without mode-conditioning patch cables. 1000BASE-LX on MMF requires a mode-conditioning patch cord to prevent differential mode delay.
Ignoring transceiver diagnostics. Many engineers blame the switch when the issue is a dirty connector or low optical power.
New in CCNA v2
This topic is entirely new in the 200-301 v2.0 blueprint. In v1.1, cable types were mentioned only in passing; now they are a distinct objective under 'Network Infrastructure and Connectivity' (25% of exam). Cisco added this because network engineers spend significant time on physical layer issues. Candidates who studied v1.1 materials will be missing this objective entirely. You must know exact distance limits and diagnostic commands.
Exactly What the Exam Tests
Objective 1.1: 'Compare and contrast copper and fiber cable types, distance limits, and interface diagnostics.' Expect multiple-choice questions that:
Ask for the maximum distance of a given cable type (e.g., Cat5e at 1 Gbps = 100m).
Present a scenario requiring you to choose the correct cable (e.g., 300m at 1 Gbps → multimode fiber).
Show output from show interfaces transceiver and ask you to interpret optical power levels.
Show TDR results and ask to identify the fault.
Common Wrong Answers and Traps
Wrong distance for 10GBASE-T on Cat6: Many candidates choose 100m, but Cat6 only supports 10G up to 55m. Cat6a supports 100m. The exam will test this distinction.
Confusing 1000BASE-SX and -LX: -SX is for MMF (550m), -LX is for SMF (5km). Candidates often reverse them.
Assuming all fiber is unlimited: Fiber has distance limits too—don't pick 'any distance'.
Ignoring transceiver compatibility: A question may give a 2km SMF link but list a 1000BASE-SX SFP as an option. That's wrong because -SX is for MMF.
TDR on live interface: TDR requires the interface to be shut down. A question might say 'The engineer ran TDR while the interface was up' → invalid.
Decision Rule for Cable Selection Questions
Determine speed (e.g., 1 Gbps).
Determine distance.
If distance ≤ 100m → copper (Cat5e, Cat6, etc.).
If 100m < distance ≤ 550m → multimode fiber (1000BASE-SX).
If 550m < distance ≤ 5km → single-mode fiber (1000BASE-LX).
If distance > 5km → single-mode fiber with 1000BASE-ZX or longer reach.
Command Outputs to Recognize
show interfaces – 'CRC errors' indicate cable issues.
show interfaces transceiver – 'Rx Power' low means bad fiber or connector.
show cable-diagnostics tdr – 'Open' or 'Short' with distance.
Elimination Strategy
If a question asks for the best cable for a 200m, 1 Gbps link, eliminate copper (too far), eliminate SMF with -SX (wrong standard), eliminate MMF with -LX (wrong standard). The correct answer is MMF with 1000BASE-SX.
[CCNA v2 NEW] This objective is new in v2.0; candidates must know exact distance limits for copper (100m) and fiber (550m for MMF, 5km for SMF at 1G).
Copper (UTP) maximum distance for any Ethernet standard (10/100/1000/10G) is 100 meters. Beyond that, use fiber.
1000BASE-SX uses multimode fiber (850nm) with a maximum distance of 550 meters (OM3/OM4).
1000BASE-LX uses single-mode fiber (1310nm) with a maximum distance of 5 kilometers (up to 10km with some implementations).
1000BASE-ZX uses single-mode fiber (1550nm) with a maximum distance of 70 kilometers.
Use `show interfaces transceiver` to check optical power levels; Rx power below threshold indicates a fiber issue.
Use `test cable-diagnostics tdr` on a shut down copper interface to locate cable faults (open, short, impedance mismatch).
Cat6 supports 10GBASE-T only up to 55 meters; Cat6a supports 10GBASE-T up to 100 meters.
Always match transceiver type to fiber type: -SX for MMF, -LX for SMF. Mixing requires mode-conditioning patch cables.
These come up on the exam all the time. Here's how to tell them apart.
Multimode Fiber (MMF)
Larger core (50 or 62.5 microns)
Uses LED or VCSEL (850nm for -SX)
Shorter distance (up to 550m for 1G)
Lower cost transceivers
Higher modal dispersion
Single-Mode Fiber (SMF)
Tiny core (9 microns)
Uses laser (1310nm or 1550nm)
Longer distance (5km+ for 1G)
Higher cost transceivers
Lower dispersion, higher bandwidth
Mistake
Fiber optic cables can run any distance without signal loss.
Correct
Fiber has distance limits based on the type: multimode fiber (1000BASE-SX) max 550m, single-mode (1000BASE-LX) max 5km, and (1000BASE-ZX) max 70km. Beyond these, signal attenuation and dispersion cause errors.
People think light in fiber is lossless, but it still attenuates over distance and suffers from dispersion.
Mistake
All Cat6 cables support 10 Gbps up to 100 meters.
Correct
Cat6 supports 10GBASE-T only up to 55 meters. Cat6a supports 10GBASE-T up to 100 meters. This is due to higher frequency requirements and alien crosstalk.
Candidates often remember 'Cat6 is for 10G' but forget the distance limitation.
Mistake
TDR can be run on a live interface without shutting it down.
Correct
TDR requires the interface to be administratively down (`shutdown`) because it sends pulses that could interfere with live traffic.
Some think TDR is non-intrusive like a cable tester, but Cisco's implementation requires the interface to be down.
Mistake
A link LED on the switch means the cable is good.
Correct
The link LED only indicates electrical continuity, not cable quality. A cable can have high error rates due to attenuation or EMI while still showing a link light.
Many troubleshooters trust the LED and look elsewhere, missing the real issue.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
100 meters. This is the standard for all twisted-pair Ethernet (10/100/1000/10G) regardless of category. Beyond 100 meters, signal attenuation causes too many errors. If you need longer, use fiber or a switch as a repeater.
Use the command `show interfaces transceiver` in privileged EXEC mode. Look for 'Tx Power' and 'Rx Power' in dBm. Compare Rx Power to the transceiver's threshold (often around -24 dBm for -LX). If it's below, the link may be unreliable. Also check for alarms like 'Rx power low'.
No. TDR (Time Domain Reflectometer) is for copper cables only. For fiber, you need an OTDR (Optical Time Domain Reflectometer), which is an external tool. Cisco switches do not have built-in OTDR; you must use a separate device.
1000BASE-SX uses multimode fiber (850nm wavelength) and supports distances up to 550 meters. 1000BASE-LX uses single-mode fiber (1310nm) and supports distances up to 5 kilometers. -SX uses cheaper optics; -LX is for longer distances. They are not interchangeable without mode-conditioning patch cables.
A link light only indicates electrical continuity at Layer 1. You could have excessive CRC errors due to a bad cable, a duplex mismatch, or interference. Check `show interfaces` for errors. Also ensure the cable is not too long (max 100m for copper). The link light does not guarantee error-free data.
It shows detailed diagnostic information for the transceiver, including temperature, voltage, current, and optical power (Tx/Rx). It also shows alarm thresholds and status flags. This command is useful for troubleshooting fiber links where the basic transceiver command shows only summary data.
Technically yes, but only with a mode-conditioning patch cable. Without it, the single-mode laser can cause differential mode delay and excessive errors. The exam expects you to know that -LX SFPs on MMF require a mode-conditioning patch cord. In practice, it's better to match the transceiver to the fiber type.
You've just covered Copper and Fiber Cable Types, Distance Limits, and Interface Diagnostics — now see how well it sticks with free CCNA 200-301 practice questions. Full explanations included, no account needed.
Done with this chapter?