Switch: How to test a cable status?

Anand G · ‎08-07-2013

Works on 29xx, 37xx, 45xx & 65xx series model switches

Checking the Cable Status Using the TDR

You can check the status of copper cables using the time domain reflectometer (TDR). The TDR detects a cable fault by sending a signal through the cable and reading the signal that is reflected back to it. All or part of the signal can be reflected back by any number of cable defects or by the end of the cable itself.

Use the TDR to determine if the cabling is at fault if you cannot establish a link. This test is especially important when replacing an existing router, upgrading to Gigabit Ethernet, or installing new cables.

The port must be up before running the TDR test. If the port is down, you cannot enter the test cable-diagnostics tdr command successfully, and the following message is displayed:

router#test cable-diagnos tdr int gig0/1

% Interface Gi0/1 is administratively down

% Use 'no shutdown' to enable interface before TDR test start.

Note: TDR can test cables up to a maximum length of 115 meters.

How to run the test?

router # test cable-diagnos tdr int gig0/1

TDR test started on interface Gi0/1

A TDR test can take a few seconds to run on an interface

To Check the Result:

'show cable-diagnostics tdr int gig0/1' will provide the TDR results.

A Sample Run Result:

switch#sh ip int bri | i up

GigabitEthernet0/1 unassigned YES unset up up

switch#

switch#test cable-diagnostics tdr interface gigabitEthernet 0/1

TDR test started on interface Gi0/1

A TDR test can take a few seconds to run on an interface

Use 'show cable-diagnostics tdr' to read the TDR results.

switch#

*Mar 1 01:59:05.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down

*Mar 1 01:59:06.238: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down

*Mar 1 01:59:12.772: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up

*Mar 1 01:59:13.779: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up

switch#

Output:

switch#show cable-diagnostics tdr interface gigabitEthernet 0/1

TDR test last run on: March 01 01:59:04

Interface Speed Local pair Pair length Remote pair Pair status

--------- ----- ---------- ------------------ ----------- --------------------

Gi0/1 1000M Pair A 8 +/- 10 meters Pair B Normal

Pair B 8 +/- 10 meters Pair A Normal

Pair C 8 +/- 10 meters Pair D Normal

Pair D 8 +/- 10 meters Pair C Normal

switch#

Regards,

Anand G

Jose Solano · ‎11-02-2013

Hi,

Nice to know this test is available I think it can be really helpful..!

Anand G · ‎11-02-2013

Thanks Jose for your comments !

Though it is a basic test, it would be helpful in identifying and narrow down the L1 issue.

Leo Laohoo · ‎03-17-2014

Even though TDR is supported on the 3560G/E/X, 4500 and/or 6500 chassis, I wouldn't recommend it. Two main reasons:

1. TDR on the line card of the 4500 and/or 6500 (regardless of model and supervisor card) takes approximately 61 seconds (versus five to seven seconds on Catalyst 2960/G/X/R and Calatyst 3750G/E/X); and

2. TDR results on the 4500 and/or 6500 are, for a lack of a better word, "LACKING". TDR functions on these two platform is NOT design to do anything. The results won't give you what fault, how far is the fault, and which pins are faulty. The TDR result will only tell you if there's a fault or not. PER to our Cisco SE/AM have proven to be useless. Privately, I was told that the DEV of both BU "doesn't care" and "don't have the time" to improve TDR functionality.

My document on TDR: http://supportforums.cisco.com/document/74231/how-use-time-domain-reflectometer-tdr

Leo Laohoo · ‎10-19-2024

TDR result with Cisco IOS-XE is not to be trusted nor accurate: CSCvw97924 & CSCwd97177

Here are some screenshots of faulty TDR result:

9300, IOS-XE version 17.9.4a(Above) Pair A & B distance is "0".(Above) Pair "A" distance is (significantly) more than Pairs B, C and D.