Article 1: Testing and Fault Finding Cat5e and Cat6 Network Cabling

Introduction

Category 5e (Cat5e) and Category 6 (Cat6) structured cabling systems form the backbone of most modern Ethernet networks. Whether installed in offices, schools, warehouses, retail environments, or data centres, reliable network performance depends heavily on the quality of the cable installation and ongoing maintenance.

Fault finding and testing network cabling is a critical skill for network engineers, telecoms engineers, and IT technicians. Proper testing identifies faults before they cause downtime and ensures installations comply with recognised standards.

Understanding Cat5e and Cat6 Cabling

Cat5e

Cat5e supports:

• 10 Mbps Ethernet
• 100 Mbps Fast Ethernet
• 1000 Mbps Gigabit Ethernet
• Operating frequency up to 100 MHz

Cat6

Cat6 provides:

• Improved crosstalk performance
• Higher bandwidth
• Operating frequency up to 250 MHz
• Gigabit Ethernet to 100 metres
• 10 Gigabit Ethernet up to shorter distances (typically 55 metres depending on conditions)

Both use four twisted pairs terminated using RJ45 connectors and follow either T568A or T568B wiring standards.

Common Network Cable Faults

1. Open Circuit

An open circuit occurs when a conductor is broken or not properly terminated.

Symptoms

• No network connection
• Intermittent connectivity
• Link light absent

Causes

• Damaged cable
• Faulty punch-down connection
• Poor crimping
• Broken conductor

2. Short Circuit

Occurs when two conductors are touching.

Symptoms

• Network device fails to establish link
• Complete network failure on affected cable

Causes

• Damaged insulation
• Poor RJ45 termination
• Crushed cable

3. Miswire

Conductors terminated in the wrong order.

Symptoms

• Reduced performance
• Link failure
• Inconsistent network speed

Example

Pair 1 connected to Pair 3 instead of Pair 1.

4. Split Pairs

One of the most common installation faults.

What is a Split Pair?

The correct pin locations appear connected, but the twisted pairs have been mixed.

Symptoms

• Cable tester may show continuity
• Gigabit links fail
• High error rates
• Poor throughput

Why It Matters

Twisting controls electromagnetic interference and crosstalk. Mixing pairs destroys this protection.

5. Excessive Cable Length

Ethernet standards specify:

• Permanent link: 90 metres
• Channel length: 100 metres maximum

Symptoms

• Slow speeds
• Packet loss
• Intermittent connectivity

6. High Attenuation

Signal weakens over distance.

Causes

• Excessive cable run
• Damaged conductors
• Poor quality cable

Symptoms

• Reduced link speed
• Frequent disconnections

7. Near-End Crosstalk (NEXT)

Signal leakage between wire pairs.

Causes

• Poor terminations
• Untwisted conductors
• Inferior cable quality

Symptoms

• Reduced network performance
• Certification failure

8. Return Loss

Signal reflections caused by impedance mismatches.

Causes

• Poor RJ45 terminations
• Sharp cable bends
• Damaged cable

Symptoms

• Random transmission errors
• Reduced performance

Essential Testing Equipment

Wire Map Tester

Basic tester used for continuity and wiring verification.

Tests:

• Opens
• Shorts
• Reversals
• Miswires
• Split pairs

Ideal during installation.

Cable Certification Tester

Professional equipment such as:

• Fluke DSX Series
• Ideal LanTEK
• Viavi Certifier

Tests:

• Wire map
• Length
• NEXT
• FEXT
• Return loss
• Attenuation
• Propagation delay

These provide standards-compliant certification.

Tone Generator and Probe

Used for cable tracing.

Useful when:

• Identifying cable routes
• Locating unknown outlets
• Finding abandoned cables

Network Tester

Provides live network diagnostics.

Can verify:

• Link speed
• PoE status
• Switch port information
• VLAN data

Step-by-Step Fault Finding Procedure

Step 1 – Visual Inspection

Always start with a physical inspection.

Check for:

• Crushed cable
• Tight bend radius
• Water damage
• Poor terminations
• Damaged outlets

Many faults are discovered before any tester is connected.

Step 2 – Verify Link Indicators

Check:

• Switch port LEDs
• Device NIC LEDs
• Patch panel indicators

No link generally indicates:

• Open circuit
• Faulty termination
• Device issue

Step 3 – Test Cable Continuity

Use a wire map tester.

Look for:

• Opens
• Shorts
• Reversed pairs
• Split pairs

Record results before re-terminating.

Step 4 – Measure Cable Length

Long cables often cause hidden problems.

Professional testers use Time Domain Reflectometry (TDR) to determine:

• Cable length
• Distance to fault

Example:

Pair 1-2 Open at 37.4m

This greatly reduces troubleshooting time.

Step 5 – Certify Performance

If the cable passes continuity testing but performance remains poor:

Perform certification testing.

Check:

• NEXT
• Return loss
• Insertion loss
• Delay skew

Certification often reveals hidden quality issues.

Step 6 – Verify Active Network Operation

Confirm:

• Link speed negotiated correctly
• PoE delivery
• Error counts on switch port
• Packet loss

A cable can pass basic tests while still causing network issues.

Common Fault Scenarios

Link Limited to 100 Mbps Instead of 1 Gbps

Possible causes:

• One pair open
• Split pair
• Incorrect termination

Gigabit Ethernet requires all four pairs.

Intermittent Connectivity

Possible causes:

• Loose punch-down connection
• Damaged patch lead
• Excessive bending
• Moisture ingress

PoE Device Not Powering Up

Check:

• Cable continuity
• Pair integrity
• PoE voltage
• Pin configuration

High CRC Errors on Switch Port

Likely causes:

• Crosstalk
• Return loss
• Poor terminations
• Cable damage

Best Practices for Cat5e and Cat6 Installations

• Maintain pair twists to within 13 mm of termination.
• Avoid cable kinks.
• Follow bend radius recommendations.
• Separate data cables from power cables.
• Use quality patch panels and keystones.
• Label all cables clearly.
• Test every cable after installation.
• Certify commercial installations.

Conclusion

Successful Cat5e and Cat6 fault finding combines visual inspection, continuity testing, certification testing, and live network diagnostics. Most faults originate from poor termination practices, physical damage, or incorrect installation techniques. Using a structured troubleshooting process significantly reduces downtime and ensures reliable network performance.

Article 2: Testing and Fault Finding Fibre Optic Cabling

Introduction

Fibre optic cabling has become the preferred medium for high-speed communications due to its enormous bandwidth, long-distance capabilities, and immunity to electromagnetic interference.

However, fibre networks require specialised testing techniques and equipment. Unlike copper cabling, many fibre faults are invisible and can only be identified using optical test equipment.

Understanding Fibre Optic Cabling

Single-Mode Fibre (SMF)

Typically:

• 9/125 µm core
• Very long distances
• High-speed backbone links
• ISP and telecom networks

Common wavelengths:

• 1310 nm
• 1550 nm

Multi-Mode Fibre (MMF)

Typically:

• 50/125 µm
• 62.5/125 µm

Used for:

• LANs
• Data centres
• Building interconnects

Common wavelengths:

• 850 nm
• 1300 nm

Common Fibre Faults

1. Fibre Break

A complete break in the fibre.

Symptoms

• Total loss of signal
• Link down

Causes

• Excavation damage
• Excessive pulling tension
• Crushing

2. Excessive Bending

Every fibre has a minimum bend radius.

Symptoms

• High attenuation
• Intermittent connection
• Reduced optical power

Types

Macro-bend

Large visible bend.

Micro-bend

Small distortions within fibre structure.

3. Dirty Connectors

The most common fibre problem.

Sources

• Dust
• Oil
• Fingerprints
• Contamination during installation

Symptoms

• High insertion loss
• Reflection issues
• Intermittent failures

4. Poor Splices

Faulty fusion or mechanical splicing.

Symptoms

• Increased loss
• Reduced performance
• Link instability

5. High Connector Loss

Every connector introduces attenuation.

Excessive loss may indicate:

• Damaged ferrule
• Poor polish
• Contaminated connector

6. Reflectance Problems

Back reflections travel toward the transmitter.

Causes

• Poor connectors
• Dirty interfaces
• Faulty splices

Symptoms

• Reduced transmission quality
• Equipment alarms

Fibre Testing Equipment

Visual Fault Locator (VFL)

A red laser used for fault identification.

Useful for:

• Breaks
• Sharp bends
• Connector faults

Limitations

Not suitable for long-distance testing.

Optical Power Meter (OPM)

Measures received optical power.

Provides:

• Received signal level
• End-to-end loss measurements

Light Source

Used with a power meter.

Enables:

• Insertion loss testing
• Link validation

OTDR (Optical Time Domain Reflectometer)

The most important fibre troubleshooting tool.

Functions include:

• Distance measurement
• Fault location
• Splice analysis
• Connector testing

OTDR Testing Explained

OTDR operates similarly to radar.

It:

1. Sends light pulses down the fibre.
2. Measures reflected signals.
3. Creates a graphical trace.

The trace reveals:

• Connector locations
• Splices
• Bends
• Fibre breaks
• End of fibre

Typical OTDR Fault Detection

Broken Fibre

Visible as:

-------------------
|
|
X

Signal abruptly ends at the break.

Bad Splice

Visible as a large step loss in the trace.

Example:

Normal Fibre
|
|
Large Loss
|
|
Normal Fibre

Dirty Connector

Appears as an excessive reflective event.

Fibre Fault Finding Procedure

Step 1 – Visual Inspection

Check:

• Connector condition
• Patch leads
• Fibre trays
• Cable routing

Inspect for:

• Damage
• Tight bends
• Crushing

Step 2 – Clean Connectors

Always clean before testing.

Use:

• Fibre cleaning pens
• Lint-free wipes
• Optical-grade cleaning fluid

Industry practice:

Inspect → Clean → Inspect Again

Step 3 – Test Optical Power

Measure received optical power.

Compare results with:

• Manufacturer specifications
• Design link budget

Step 4 – Perform Insertion Loss Testing

Measure total path loss.

Compare against expected values.

Example:

Expected: 2.5 dB
Measured: 4.8 dB

Indicates a fault is likely present.

Step 5 – Run OTDR Analysis

Determine:

• Distance to fault
• Splice quality
• Connector quality
• Reflection events

Document all findings.

Common Fibre Fault Scenarios

Complete Link Failure

Possible causes:

• Broken fibre
• Equipment fault
• Disconnected patch lead

Use:

• VFL
• OTDR

High Optical Loss

Possible causes:

• Dirty connectors
• Damaged patch leads
• Bad splice
• Excessive bends

Intermittent Operation

Possible causes:

• Movement-sensitive bend
• Poor connector seating
• Damaged enclosure

Reduced Network Throughput

Possible causes:

• Marginal optical levels
• Reflection issues
• Damaged transceivers

Fibre Testing Standards

Testing should comply with recognised standards such as:

• ISO/IEC 11801
• ANSI/TIA-568
• IEC 14763
• BS EN 50173

Documentation should include:

• OTDR traces
• Loss measurements
• Fibre identifiers
• Test wavelengths
• Pass/fail results

Best Practices for Fibre Installations

• Never exceed pulling tensions.
• Observe minimum bend radius.
• Always clean connectors before mating.
• Use fusion splicing where possible.
• Label fibres clearly.
• Store OTDR traces for future reference.
• Test both directions where required.
• Maintain accurate documentation.

Conclusion

Fibre optic fault finding requires a systematic approach and specialised test equipment. Most problems originate from contamination, excessive bending, poor splicing, or physical damage. By using tools such as optical power meters, VFLs, and OTDRs, engineers can quickly identify faults, minimise downtime, and ensure fibre infrastructure delivers maximum performance and reliability.