test cable-diagnostics
To test the condition of 10-Gigabit Ethernet links or copper cables on 48-port 10/100/1000 BASE-T modules, use the test cable-diagnostics command in privileged EXEC mode.
test cable-diagnostics tdr interface type number
Syntax Description
tdr |
Activates the TDR test for copper cables on 48-port 10/100/1000 BASE-T modules. |
interface type |
Specifies the interface type; see the “Usage Guidelines” section for valid values. |
number |
Module and port number. |
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Release |
Modification |
---|---|
12.2(17a)SX |
Support for this command was introduced on the Cisco 7600 series routers. |
12.2(17b)SXA |
This command was changed to provide support for the 4-port 10GBASE-E serial 10-Gigabit Ethernet module (WS-X6704-10GE). |
12.2(17d)SXB |
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
Cable diagnostics can help you detect whether your cable has connectivity problems.
The TDR test guidelines are as follows:
-
TDR can test cables up to a maximum length of 115 meters.
-
The TDR test is supported on Cisco 7600 series routers running Release 12.2(17a)SX and later releases on specific mdoules. See the Release Notes for Cisco IOS Release 12.2SX on the Catalyst 6500 and Cisco 7600 Supervisor Engine 720, Supervisor Engine 32, and Supervisor Engine 2 for the list of the modules that support TDR.
-
The valid values for interface type are fastethernet and gigabitethernet .
-
Do not start the test at the same time on both ends of the cable. Starting the test at both ends of the cable at the same time can lead to false test results.
-
Do not change the port configuration during any cable diagnostics test. This action may result in incorrect test results.
-
The interface must be up before running the TDR test. If the port is down, the test cable-diagnostics tdr command is rejected and the following message is displayed:
Router# test cable-diagnostics tdr interface gigabitethernet2/12
% Interface Gi2/12 is administratively down
% Use 'no shutdown' to enable interface before TDR test start.
-
If the port speed is 1000 and the link is up, do not disable the auto-MDIX feature.
-
For fixed 10/100 ports, before running the TDR test, disable auto-MDIX on both sides of the cable. Failure to do so can lead to misleading results.
-
For all other conditions, you must disable the auto-MDIX feature on both ends of the cable (use the no mdix auto command). Failure to disable auto-MDIX will interfere with the TDR test and generate false results.
-
If a link partner has auto-MDIX enabled, this action will interfere with the TDR-cable diagnostics test and test results will be misleading. The workaround is to disable auto-MDIX on the link partner.
-
If you change the port speed from 1000 to 10/100, enter the no mdix auto command before running the TDR test. Note that entering the speed 1000 command enables auto-MDIX regardless of whether the no mdix auto command has been run.
Examples
This example shows how to run the TDR-cable diagnostics:
Router # test cable-diagnostics tdr interface gigabitethernet2/1
TDR test started on interface Gi2/1
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.