topic RE: TDR or similar cable test diagnostics in ExtremeSwitching (EXOS/Switch Engine)

TDR or similar cable test diagnostics

Eduardo_Mendiza — Wed, 21 Sep 2016 03:36:00 GMT

Hello everyone,

I would like to know if the summit series has any TDR functionalities or similiar failure detection features on copper cables. I know the summit series has a run diagnostics command, but, from what I've read, it only tests ASIC and packet loopback.

Cheers.

Ed

RE: TDR or similar cable test diagnostics

Dave_Hammers — Wed, 21 Sep 2016 15:33:00 GMT

Starting with EXOS 21.1.2, the cablediag application is bundled in with EXOS.
Known issues:

Disruptive test: momentarily interrupts data on a link
Disrupts stacking if run on alternative stack link ports

# run script cablediag.py -h
usage: cablediag [-h] [-s SLOT [SLOT ...]] [-p PORT [PORT ...]] [-d]

optional arguments:
-h, --help show this help message and exit
-s SLOT [SLOT ...], --slot SLOT [SLOT ...]
Stacking slot number, e.g. 1,2 or 1-5
-p PORT [PORT ...], --port PORT [PORT ...]
Selected port number, e.g. 3,4,5 or 3-5
-d, --debug Enable debug

E.g.
# run script cablediag.py -p 2
cablediag: 1.0.0.1

Collecting port cable diagnostic information may take a moment...

port 2: cable (4 pairs, length +/- 10 meters)
pair A Ok, length 0 meters
pair B Ok, length 0 meters
pair C Ok, length 0 meters
pair D Ok, length 0 meters

E.g.
# run script cablediag.py
cablediag: 1.0.0.1

Collecting port cable diagnostic information may take a moment...

port 1: cable (4 pairs, length +/- 10 meters)
pair A Open, length 0 meters
pair B Open, length 0 meters
pair C Open, length 0 meters
pair D Open, length 0 meters
port 2: cable (4 pairs, length +/- 10 meters)
pair A Ok, length 0 meters
pair B Ok, length 0 meters
pair C Ok, length 0 meters
pair D Ok, length 0 meters
port 3: cable (4 pairs, length +/- 10 meters)
pair A Open, length 0 meters
pair B Open, length 0 meters
pair C Open, length 0 meters
pair D Open, length 0 meters
...

port 23: cable (4 pairs, length +/- 10 meters)
pair A Open, length 0 meters
pair B Open, length 0 meters
pair C Open, length 0 meters
pair D Open, length 0 meters
port 24: cable (4 pairs, length +/- 10 meters)
pair A Open, length 0 meters
pair B Open, length 0 meters
pair C Open, length 0 meters
pair D Open, length 0 meters
CABLEdiag: ERROR: port 25: Feature unavailable
CABLEdiag: ERROR: port 26: Feature unavailable
CABLEdiag: ERROR: port 27: Feature unavailable
CABLEdiag: ERROR: port 28: Feature unavailable
CABLEdiag: ERROR: port 29: Feature unavailable
CABLEdiag: ERROR: port 30: Feature unavailable
CABLEdiag: ERROR: port 31: Feature unavailable
CABLEdiag: ERROR: port 32: Feature unavailable
CABLEdiag: ERROR: port 33: Feature unavailable
CABLEdiag: ERROR: port 34: Feature unavailable

RE: TDR or similar cable test diagnostics

Stephane_Grosj1 — Wed, 21 Sep 2016 15:33:00 GMT

Ah, it made its way to 21.1.2! Good to hear.

RE: TDR or similar cable test diagnostics

Eduardo_Mendiza — Wed, 21 Sep 2016 22:20:00 GMT

Thanks for the answer Dave. That solves my doubt.

Ed

RE: TDR or similar cable test diagnostics

M_Nees — Wed, 31 May 2017 12:42:00 GMT

Test this feature with X440-G2 48 Ports - it does not work ;-(
GTAC Case 01327221

Other Switches X450-G2 or X440 24Port models working well.

I hope cablediag.py will be a standard CLI command in near future.

Regards

RE: TDR or similar cable test diagnostics

Drew_C — Wed, 31 May 2017 12:42:00 GMT

I've been trying to get it added to the standard CLI for a while. When 22.3 comes out, I might have a trick to share with you... 😉
Thanks for reporting the bug.

RE: TDR or similar cable test diagnostics

M_Nees — Fri, 23 Feb 2018 13:31:00 GMT

Hi Dave,
It seems that there are some changes in Cable Diagnostics 1.1.0.3.

Having a short look into "User Documentation" will only deleiver a HTML Error:
404: Not Found
https://rawgit.com/extremenetworks/EXOS_Apps/master/Cablediags/docs/

Regards

RE: TDR or similar cable test diagnostics

Dave_Hammers — Fri, 23 Feb 2018 19:21:00 GMT

Extreme is working on a central document web page for engineering created documentation.

api.extremenetworks.com

unfortunately, it is not enabled to be visible outside of Extreme just yet.

Until this is working, I've updated github with the doc for cablediag 1.1.0.3

RE: TDR or similar cable test diagnostics

JohanHendrikx — Mon, 23 Apr 2018 18:56:00 GMT

What is pair A, B, C and D (1,2 / 3,6/ 4,5 and 7,8)?

RE: TDR or similar cable test diagnostics

Alexandr_P — Wed, 09 Jan 2019 15:56:00 GMT

Hi, all!

So, what exactly is pairs A, B, C, D?

Thank you!

RE: TDR or similar cable test diagnostics

M_Nees — Wed, 09 Jan 2019 16:06:00 GMT

This is related to the below cablediagnostic output:

code:

port 2: cable (4 pairs, length +/- 10 meters)
 pair A Ok, length 0 meters
 pair B Ok, length 0 meters
 pair C Ok, length 0 meters
 pair D Ok, length 0 meters

@John: Good question ! (i hope it will be answered)
otherwise you have to test it by modifying a patch cable.

RE: TDR or similar cable test diagnostics

M_Nees — Wed, 09 Jan 2019 16:06:00 GMT

Any news after 10 months ?

RE: TDR or similar cable test diagnostics

Drew_C — Tue, 15 Jan 2019 04:17:00 GMT

It's working for me using my cell phone (not on internal wireless).
Specifically regarding cable diag, there's this page: http://api.extremenetworks.com/EXOS/Applications/Cablediag/

Note that in 22.5, a normal CLI command was added

code:

run diagnostics cable ports [ {port-list} | all ]

RE: TDR or similar cable test diagnostics

davidj_cogliane — Wed, 06 Feb 2019 05:19:00 GMT

Is there a similar script that could be run on a G1 switch running 16.2?

RE: TDR or similar cable test diagnostics

Drew_C — Thu, 07 Feb 2019 23:50:00 GMT

Hi David,
Try this: https://github.com/extremenetworks/EXOS_Apps/tree/master/Cablediags

RE: TDR or similar cable test diagnostics

davidj_cogliane — Thu, 07 Feb 2019 23:54:00 GMT

I had found that previously and get the below error
"Downloading to SwitchError: Failed to download image - Error: File could not be unwrapped."

These attempts have been on a X440-48p running 16.2.5.4

RE: TDR or similar cable test diagnostics

Justin_Noland1 — Fri, 22 Feb 2019 01:02:00 GMT

David, I ran into this same issue today. I found that by downloading the image via TFTP to my desktop and then uploading it to the switch using "download image x.x.x.x summitX-cablediag-1.1.0.3.xmod vr vr-default" I was able to install it successfully.

RE: TDR or similar cable test diagnostics

davidj_cogliane — Fri, 22 Feb 2019 02:21:00 GMT

Justin,

Thanks for the reply, that worked well for getting the image on the switch.

Unfortunately it still wont run.

440-G1 running 16.2.5.4-patch1-7 and I get the below error.

* Staging-Rack.9 # run script cablediag.py -p 16
cablediag: 1.1.0.3

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ C A U T I O N +
+ cablediag will momentarily interfere with traffic on active ports +
+-----------------------------------------------------------------------+
+ Ports: 16 +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Do you want to continue cable diagnostics? [y/N]: y
Collecting port cable diagnostic information may take a moment...
socket.timeout: timed out
* Staging-Rack.10 #

RE: TDR or similar cable test diagnostics

Justin_Noland1 — Fri, 22 Feb 2019 03:09:00 GMT

Son of a gun, you're right. Just did the same thing for me. Tried it on two different switches, an x440 and an x460, both running 16.2.4.5 patch1-8 and the failed the same way.

RE: TDR or similar cable test diagnostics

davidj_cogliane — Fri, 22 Feb 2019 03:33:00 GMT

Maybe the G1 switches just don't have the hardware to get this done.

Though I swear I saw a TAC guy do something similar in the past.