Cabling & Media Standards

Mental model

The physical layer determines how fast and how far. Get this wrong and the rest of the stack works perfectly while users complain about slow networks. Two big categories of media:

• Copper twisted pair: cheap, terminates with RJ45, runs up to 100 meters. The default for desk drops, APs, IP phones, cameras.
• Fiber optic: more expensive, multiple connector types, runs from 100m to many kilometers. The default for switch-to-switch uplinks, datacenter spine-leaf, building-to-building, ISP last mile.

Within each category, multiple grades exist for different bandwidth and distance targets.

Copper twisted pair: Cat ratings

All Ethernet over copper uses 8 wires in 4 twisted pairs. The category number determines bandwidth and distance.

Common confusions:

• Cat6 caps at 1 Gbps over 100m, but supports 10 Gbps if the run is ≤55m. Many people quote “Cat6 = 10 Gbps” without the distance caveat.
• Cat6A is the practical 10 Gbps copper standard for full 100m runs. If you’re building today and want headroom, use Cat6A everywhere.
• Cat7 is rarely seen in US enterprise. Most installers skip from Cat6A to fiber for longer or faster runs.
• Cat8 is short-haul only. Designed for ToR copper jumpers in datacenters; useless for general office cabling.

Shielding

• UTP (Unshielded Twisted Pair): the standard. Cheaper, easier to terminate.
• STP / FTP / S/FTP: Shielded variants. Reduce alien crosstalk, more expensive, harder to ground properly, required for some industrial environments.

For 99% of enterprise installs, UTP is fine. STP only matters in high-EMI environments (factories, hospitals near MRI).

Termination

RJ45 connectors on both ends. Two wiring standards exist:

• T568A: green pair on pins 1/2
• T568B: orange pair on pins 1/2 (more common in N. America)

Both work. The rule: be consistent across both ends of a cable. Mixing A and B on the same cable creates a crossover (used to be needed for switch-to-switch; auto-MDIX handles it now).

Fiber optic: types and modes

Fiber transmits light, not electricity. Two fundamental types:

Why the difference? Single-mode’s tiny core forces light into a single path → less dispersion → much longer distance. Multi-mode’s wider core allows multiple paths → cheaper transceivers but signal disperses faster.

Multi-mode grades (OM)

Multi-mode fiber comes in OM grades. Higher number = better bandwidth × distance product.

OM3 and OM4 are the modern defaults for datacenter MMF. OM1/OM2 are legacy and should be replaced.

Single-mode (OS1 / OS2)

OS1 and OS2 are similar; OS2 is slightly better for outdoor/long-haul. Single-mode supports speeds from 1G to 800G+ over distances from a few hundred meters (with cheap transceivers) to 80+ km (with long-haul DWDM).

Connectors

Multiple fiber connector types exist. Common ones:

Polish type matters for connector loss: UPC (blue, lower loss) vs APC (green, even lower loss, used in PON / carrier networks). Don’t mix them at a single connection.

Transceivers: what plugs into the switch port

A switch port doesn’t natively know what cable it’s talking to. You insert a transceiver (a small pluggable module) into the switch’s SFP/QSFP cage, which converts between the switch’s electrical interface and the optical or copper media on the cable.

Cable choices for transceiver speeds:

• DAC (Direct Attach Copper): short (≤7 m) passive copper cable with transceivers built into both ends. Cheap. Use for top-of-rack server connections.
• AOC (Active Optical Cable): same idea but with fiber. Longer (up to ~30 m) than DAC. Used for mid-rack to top-of-rack runs that don’t justify pluggable optics.
• Pluggable optics + structured fiber: most flexible. Use for inter-switch links and anything over ~10 m.

Vendor lock: the dirty secret

Many switch vendors “validate” only their own-branded transceivers. A generic 10G SFP+ from a third-party (FS, ProLabs) physically works and often costs 1/10 the price of a Cisco-branded one, but on stricter platforms (Catalyst 9000, Nexus), the port may refuse the optic without service unsupported-transceiver configured.

SW1(config)# service unsupported-transceiver
SW1(config)# no errdisable detect cause gbic-invalid

service unsupported-transceiver is a hidden command and is not supported by Cisco TAC. Use third-party optics with eyes open.

Distance + bandwidth chart: the reference card

Diagnosing copper and fiber problems (CCNA v2.0 1.1)

A slow or flapping link leaves evidence in the interface counters. Start with show interfaces:

SW1# show interfaces GigabitEthernet1/0/10
  ...
     0 runts, 0 giants, 0 throttles
     1843 input errors, 1843 CRC, 0 frame, 0 overrun, 0 ignored
  ...
     0 babbles, 0 late collision, 0 deferred

Counters only matter if they’re increasing: clear counters GigabitEthernet1/0/10, wait, look again.

Duplex and speed mismatch clues: one end shows Full-duplex and the other Half-duplex, late collisions pile up on the half-duplex side while CRC errors and runts grow on the full-duplex side, and CDP logs a duplex mismatch message. Set both ends to auto, or hard-code both to the same values.

Fiber

SW1# show interfaces transceiver
SW1# show interfaces Te1/1/1 transceiver detail
SW1# show idprom interface Te1/1/1

The detail view lists Tx and Rx optical power in dBm next to four thresholds: high alarm, high warning, low warning and low alarm. Rx power below the low warning line means too little light is arriving. The usual suspects:

• Dirty or damaged connectors. Clean and inspect both ends before swapping hardware.
• Wrong fiber type. A single-mode optic on multimode fiber, or the reverse. show idprom tells you exactly which optic is installed.
• Mismatched optics. SR on one end and LR on the other, or different wavelengths.
• Distance. The run is longer than the optic and fiber grade support (see the chart above).
• Polarity. Tx must land on the far end’s Rx. If both ends transmit fine but receive nothing, check the pair.

Copper

Pinout: straight-through for unlike devices (PC to switch), crossover for like devices (switch to switch) on older gear. Auto-MDIX (mdix auto) detects the cable type and adjusts, so modern ports accept either.

TDR cable test on a Catalyst 9000 copper port:

SW1# test cable-diagnostics tdr interface GigabitEthernet1/0/10
SW1# show cable-diagnostics tdr interface GigabitEthernet1/0/10

Each pair reports Normal, or a fault: open, short, or impedance mismatch. TDR works best with the far end disconnected, results can be invalid when the far port uses auto-MDIX, and Cisco recommends running it more than once.

Common mistakes

1. Quoting “Cat6 = 10 Gbps” without distance. It’s 10 Gbps only to 55m. For full 100m runs at 10G, use Cat6A.

2. Mismatched transceivers. Both ends must use the same standard. A 10G-SR (multi-mode short range) on one end and 10G-LR (single-mode long range) on the other won’t link.

3. Mixing MMF and SMF. Single-mode optics aimed into multi-mode fiber lose power; multi-mode optics into single-mode get refracted away from the core. Either way, no link.

4. OM3 over 40G QSFP+ at 400m. OM3 caps at 100m for 40/100G. Use OM4 or single-mode for longer.

5. Forgetting MPO polarity. 12-fiber MPO trunks have a polarity (A, B, or C): wrong polarity means the TX of one device hits the TX of the other. Buy patch cords that match your trunk type.

6. Ignoring heat in large PoE bundles. 802.3at and 802.3bt are specified over Cat5e and up, but heat builds in tight bundles. Prefer Cat6A for large bundles of PoE++ (802.3bt). Full Power over Ethernet breakdown covers the standards (802.3af / at / bt), classes, and switch power-budget math.

7. Buying expensive Cat8 for office cabling. Cat8 is short-haul datacenter copper. For a typical desk drop, Cat6A is the modern standard.

8. Connecting APC to UPC. Polish mismatch = high loss and back-reflection, and it can damage the end faces. Stick with one polish type per fiber path.

Lab to try tonight

This is hard to lab without real cables and switches. What you can do:

1. Look at your existing patch panels. Identify the cable Cat rating (printed on the jacket).
2. Open your switch and look at its uplink ports. SFP cage? SFP+? QSFP? Note the form factor.
3. If you have an SFP-capable switch, pull out a transceiver and read the label. It’ll say something like 1000BASE-LX (1G single-mode) or 10GBASE-SR (10G multi-mode short range).
4. From the CLI, show interface Gi1/1 transceiver (Cisco) shows the optical power, useful for “is this fiber okay” diagnostics.
5. In CML or EVE-NG, fiber/copper choice is abstracted away, but you can simulate distance/loss issues by changing link delay parameters.

Cheat strip