Table of Contents
Introduction Troubleshooting Basics Link Models Finding Cabling Faults Troubleshooting Flowchart Escalation Procedure Using Advanced Troubleshooting Diagnostics Examples Conclusion 2 3 4 5 8 10 12 13 16
Introduction
Todays cabling installation professionals must know how to troubleshoot and diagnose high-performance cabling systems. Structured cabling systems have changed dramatically since the TIA-568A and IS11801 cabling standards were published in 1995. The revised and updated standards no longer recommend the Cat 5 cabling system and instead support Cat 5e or Cat 6 installations. Why the need for advanced diagnostics?
These high-performance cabling systems must be tested and certified in the field with new test parameters, new link definitions, more data points, higher bandwidth, tighter margins, new connector types, as well as patch cord requirements. The importance of component compliance and excellent workmanship during installation has risen accordingly. Due to the increased complexity of these cabling systems, determining the cause of failure and quickly restoring suitable performance has become a challenging task. This handbook has been written to guide you through troubleshooting of advanced structured cabling systems, so you can increase your productivity and deliver better value to your organization.
NETWORKSUPERVISION
Troubleshooting Basics
Copper cabling failures are most commonly caused by one of the following: 1. Installation errors (especially wiremap and pair twisting; always keep the original twist in wire pairs as much as practical) 2. Bad connectors 3. Inappropriate tester set up 4. Bad cable 5. Bad patch cords* 6. Cabling effects not accounted for in the link model (e.g. reflected FEXT)
*Patch cords would be higher on the list, except that they are only tested in the channel configuration, and the vast majority of tests are of the permanent link.
Link models
For meaningful results, it is essential to choose the appropriate autotest and link model. The Basic Link is now obsolete, and the majority of all field tests should use the Permanent Link model. The impact of this change is to move the reference point for the measurements from the tester interface to the far end of the test cord (as shown). In a practical sense, this means field testers must be much more sophisticated, because they must subtract all of the test cord effects for each measurement. From an installers perspective, the change from Basic to Permanent Link also means a loss of approximately 2 dB of NEXT margin at 250 MHz, which can lead to more failures and marginal results on Category 6/Class E links. When performing Permanent Link tests, take special care to ensure you are using adapters that are appropriate for the cabling under test (especially for Category 6/Class E links).
Patch Panel Consolidation Point Telecommunications Outlet
Channel measurements are typically done when restoring service, or to verify cabling for application support. It is uncommon to perform channel tests during normal installation, since the patch cords are rarely available at that time. Correct channel measurements must cancel the effects of the mated connection in the testers the channel adapters.
Patch Panel Consolidation Point Telecommunications Outlet
FAULT INFO
EXIT
LOW BATTERY
TALKING
TESTING
PASS
FAIL
TALK
ON
OFF
2 3
TALK
NETWORKSUPERVISION
Wiremap
Test Result Open Possible Cause of Result Wires broken by stress at connections Cables routed to wrong connection Damaged connector Cuts or break in cable Wires connected to wrong pins at connector or punch block Application-specific cable (e.g. Ethernet using 12/36 only) Improper connector termination Damaged connector Conductive material stuck between pins at a connection Damage to cable Application-specific cable (e.g. factory automation)
Short
Wires connected to wrong pins at connector or punch block Wires connected to wrong pins at connector or punch block Mix of 568A and 568B wiring standards (12 and 36 crossed) Crossover cables used (12 and 36 crossed) Wires connected to wrong pins at connector or punch block
Split pair
Length
Test Result Length exceeds limits Length reported is shorter than known length One or more pairs significantly shorter Possible Cause of Result Cable is too long check for coiled service loops and remove in this case NVP is set incorrectly Intermediate break in the cable
Note: Standard practices dictate that length be defined by the length of the shortest pair. NVP varies per pair, meaning each pair could be reported with a different length. These two conditions can result in a cable with three of four pairs over the length limit, yet the link result is a Pass (e.g. a channel with 101, 99, 103, 102 meters for the four pairs). A Pass in this case is the correct interpretation.
Delay/Skew
Test Result Exceeds limits Possible Cause of Result Cable is too long Propagation delay Cable uses different insulation materials on different pairs Delay skew
Unexpected Pass
Unexpected Pass
Resistance
Test Result Fail *Fail, or *Pass Likely Cause of Result Excessive cable length Poor connection due to oxidized contacts Poor connection due to marginally attached conductors Thinner gauge cable Incorrect patch cord type
Check NVP/Cable setting Check length If failure on only one pair: re-punch that pair at both ends Use time domain return loss analysis or time domain reflectomerty (TDR) to look for events Using OMNIScanner: Perform S-Band diagnostics Is connection within the bands? If not, connection out of limits If connection OK: - bad cord or cable (see time domain plot) Using OMNIScanner: Perform S-Band diagnostics Is connection in the bands? If not, connection out of limits If connection OK: bad cord or cable (see time domain plot)
NETWORKSUPERVISION
Using DSP 4X00: Perform HDTDX Locate fault and correlate NEXT event(s) with cabling to find source of failure
Using DSP 4X00: Perform HDTDR Locate fault and correlate RL event(s) with cabling to find source(s) of failure Check for presence of service loops If service loop present, remove tie wraps and spread out coils
Escalation procedure
1. Be able to answer Yes to the following questions:
Do the cable and connectors used in the installation match the performance rating of the autotest selected? If a Category 6/Class E installation, are all components matched appropriately? Has the appropriate autotest been selected? Has the correct link type been selected? Are you using the appropriate adapter for this test? Are you using the most current version of tester software? Is the NVP set correctly for the cable under test? Is the tester at ambient temperature and in calibration? Have you carefully reviewed the installation quality of the terminations, re-punched where necessary, and ensured the cable is not snagged or kinked? Wiremap passes?
2. Does the link fail with no marginal results (those marked with a *)?
If so, it is likely a bad component or cable, and any tuning or tweaking is not likely to get you to a Pass. Verify your results and methodology with your senior troubleshooting specialist. Use time domain analysis techniques to attempt to isolate the connection, cable, or patch cord as the source of failure. Save all test results with full swept frequency data and record the testers serial number and software version. Contact the appropriate supplier, share your test results with them, and work to resolve the problem.
10
The following suggestions may assist in improving the performance of a marginal link: Re-punch connections Replace connectors Replace patch cords (if a channel test) Remove or loosen any tightly binding cable ties Remove or loosen any service loops of cable in the wiring closet
11
While both are DSP-based digital testers, and both show both frequency and time domain representations of the cabling, they approach troubleshooting from slightly different perspectives. In order to get the most out of each tool, it is important to understand these differences so that you can interpret the information displayed correctly. While slightly different, each approach is equally viable.
DSP-4300 Schematic diagnostics display Shows crosstalk vs length Shows NEXT vs length Shows NEXT phase information Shows impedance vs length Shows return loss vs length Includes pass/fail S-Bands Time domain plots can be saved Magnitude and phase information can be exported X X X X X X X X X OMNIScanner2
12
Examples
The following examples illustrate NEXT failures. Similar results can be seen using Return Loss time domain diagnostic techniques. The first example is of the DSP-4300 display, followed by a comparison of the same NEXT cable fault using both the DSP-4300 and the OMNIScanner2. The last example illustrates a faulty connection. These examples should help to clarify the differences in appearance of faults and diagnostics techniques of each product.
Example 1a: Category 6 link with good connection but bad cable
DSP-4300 schematic display suggests cable may be bad over distance shown.
13
Example 1b:
Both DSP-4300 and OMNIScanner2 time domain displays show NEXT at connection is low, but cable has high NEXT throughout its length.
DSP-4300
OmniScanner2
On this magnified view, note that both testers see a high NEXT event nine meters into the cable.
Note that the magnitude of NEXT events remains roughly constant on the DSP display because it is showing crosstalk vs. length, while on the OMNI2 display the magnitude is gradually attentuating because it is showing NEXT vs. length.
14
The OMNIScanner2 testing the same link with the same personality module provides similar information. You can see that the connector response barely exceeds the allowable limit for Category 6 connectors (as indicated by the S-Bands), and there is the same secondary event 3.7 meters down the cable.
Cursor Maximum magnitude of event (1.06 times the Cat 5e connector limit) Secondary event at 3.7 meters Positive NEXT indicates inductive coupling Negative NEXT indicates capacitive coupling S-Bands indicate connector limits. S-Band limits are angled in because NEXT attenuates with distance
15
Conclusion
Despite good products and careful installation procedures, some failures are inevitable when testing Category 5e and 6 cabling. By knowing the nature of typical faults, and how they are represented in your testers display while troubleshooting, you can significantly reduce network downtime and restore service quickly. Taking the time to familiarize yourself with the capabilities of your test tool will be a modest investment that pays for itself many times over.
For the latest information on cable testing standards, news, and issues, visit www.cabletesting.com
16
For more information about Fluke Networks copper and fiber cabling solutions go to www.flukenetworks.com.
17
N E T W O R K S U P E R V I S I O N Fluke Networks, Inc. P.O. Box 777, Everett, WA USA 98206-0777 (800) 283-5853 Fax (425) 446-5043 Western Europe 00800 632 632 00, +44 1923 281 300 Fax 00800 225 536 38, +44 1923 281 301 Email: info-eu@flukenetworks.com Canada (800) 363-5853 Fax (905) 890-6866 EEMEA +31 (0)40 267 5119 Fax +31 (0)40 267 5180 Other countries call (425) 446-4519 Fax (425) 446-5043 E-mail: fluke-assist@flukenetworks.com Web access: http://www.flukenetworks.com