Configuring Ethemet Ports Using TDR Cable Diagnostics Using TDR Cable Diagnostics Time Domain Reflectometry (TDR) is a feature that is used to detect cable faults. This feature is best deployed in networks where service providers and system administrators want to quickly diagnose the state of a cable during outages, before proceeding with further diagnosis Extended TDR is a feature that is used to know the attached cable characteristics. Its implemented by ‘monitoring the transmitted signals amplitude received from the link partner. Both the tests are used to find out different parameter of a cable under different scenarios. When a TDR test is initiated, a signal is sent down a cable to determine the distance to a break or other discontinuity in the cable path, The length of time it takes for the signal to reach the break and return is, used to estimate the distance to the discontinuity. jating a TDR Cable Diagnostics Test Consider the following guidelines before initiating a TDR test + Only one test can run at any given time, and there is no way to stop test once it has started, + The TDR test runs an “out-of-service” test; other data and protocol traffic on the port is interrupted when the test is active + TDR is supported only on copper ports and not on fiber or stacking ports + TDR is not supported on Link aggregate ports + Each time a TDR test is run, statistics from a test previously run on the same port are cleared, A TDR testis initiated using the interfaces tdr-test-start CLI command For example, the following command starts the test on port 2/1 > interfaces 2/1 tar-test-start + The TDR Test (CLIs related to TDR-Test) can run on both OS 6250 and OS 6450 platforms. While the Extended-TDR Test (CLIs related to Extended-TDR Test) can run only on a switch with 1 GIG link capability (OS 6450), + Extended TDR is @ feature that is used to know the attached cable characteristics. tis implemented by ‘monitoring the transmitted signals amplitude received from the link partner. Both the tests are used to find out different parameter of a cable under different scenarios. These Cable Diagnostic feature are supported and are integrated into the CPSS SDK. + The Extended-TDR Test results (cable-length) between different pairs and between multiple readings within each pair can vary based on the link partner’s differential voltage and temperature conditions of the device under test, Ifthe same cable is measured several times, occasionally there can be a major deviation in the reading exceeding +/- 10 meters. A Extended-TDR test is initiated using the interfaces tdr-extended-test-start CLI command, For example, the following command starts the test on port 2/1: > interfaces 2/1 tdr-extended-test-start + Extended TDR can work only when the gigabit link is established between the two link partners. + Extended TDR operations cannot be performed on fiber, stacking and combo ports. OmniSwitch 6250/6450 Network Configuration Guide December 2014 page 1-23Using TDR Cable Diagnostics Configuring Ethernet Ports Displaying TDR Test Results The show interfaces tdr-statisties command is used to display TDR test statistics, For example: > show interfaces 1/3 tdr-statistics Legend: Pair 1 ~ gzeen and wa. Pair 2 - orange and whi Bair 3 - and wait Pair 4 - blue and waite The show interfaces tdr-extended-statistics command is used to display the results of the last Extended TDR test performed on a port. For example: > shox interfaces 1/5 tér-ex Accurate Cable length (in meters) Pair 1:15 Pair 2:15 Pair 4:15 Downshift :Ne Dot The following cable states are indicated in the show interfaces tdr-statisties command output + OK—Wire is working properly + Open:—Wire is broken + Short—Pairs of wire are in contact with each other + Impedance Mismatch - + Two cable of different quality/resistence are connected to each other through patch connector, + Ifthe pair is short in a cable, it may affect the resistance of another pair hence it will result Imped- ance mismatch on that particular pair + Unknown - Cable diagnostic test unable to find the state of a cable, + Pair Swap - Determines the channel associated with the MDI pair (cross or nat for each two MDI pairs). page 1-24 ‘OmniSwitch 6250/6450 Network Configuration Guide December 2014Configuring Ethemet Ports Using TDR Cable Diagnostics + Pair Polarity- Detects if the pairs are connected with reverse polarity (reverse on one side between ‘two conductors in one pair) + Pair Skew-The skew among the four pairs of cable (delay between pairs, in n-seconds) + Cable Length - The length of the cable, in meters + Downshift - Gives the downshift status of the port, when the gigabit link cannot be established. Clearing TDR Test Statistics The interfaces no tdr-statistics command is used to clear the statistics of the last test performed on the port. There is no global statistics clear command. For example, the following command clears the TDR statistics on port 2/1 > interfaces 2/1 no tér-statistics TDR statistics from a previous test are also cleared when a new test starts on the same port. Clearing TDR Extended Test Statistics The interfaces no tdr-extended-statistics command is used to clear the statistics of the last test performed on the port. There is no global statistics clear command, For example, the following command clears the Extended TDR statistics on port 2/1 faces 2/1 no tdr-extended-statistics TDR extended statistics from a previous test are also cleared when a new test starts on the same port, OmniSwitch 6250/6450 Network Configuration Guide December 2014 page 1-25