Fluke Networks CertiFiber Pro Users Manual User Manual
Page 154

Versiv Cabling Certification Product Family
Technical Reference Handbook
132
Resistance test gives FAIL, FAIL*, or PASS* result
Link is too long (may need to remove coiled service loops)
Bad connection due to oxidized or loose contacts
Wire gauge is too thin
Wires in a pair have too much difference in the number of twists
(resistance is unbalanced)
Wrong type of patch cord used
Note
The HDTDR analyzer can help you locate the cause of
a resistance failure. See page 143.
Length gives a FAIL result
Link is too long (may need to remove coiled service loops)
NVP is set incorrectly
Length exceeds the limit, but the length test did not fail
If the length of the shortest pair does not exceed the limit by 10 %, then the
length test passes even if other pairs exceed the limit. This is the 10 % rule for
length, as given in the ANSI/TIA standard. See the Fluke Networks Knowledge
base for details.
Propagation delay or delay skew gives FAIL result
Link is too long (may need to remove coiled service loops)
Cable has different insulation materials on different pairs. This causes
differences in the twist ratios, which causes differences in propagation
delays among pairs.
“Bad patch cord” message (indicates excessive crosstalk over the first or last
2 m of the cabling)
Wire pairs are untwisted too much in the RJ45 plug
Poor quality patch cord used for channel
Cable on a permanent link interface adapter is badly distorted or
damaged
Wrong test standard selected
Table 7. Causes of Twisted Pair Test Failures (continued)