mass TDR testing on 2960x switches.

[Magnets]

We have had a new building cabled and i don't trust the test results given to us by the cabler.

We have over 2000 ports via many stacks of 2960x's

a spot check via the TDR command on ports that are connecting at 100 and should be 1000 are showing broken pairs.

This is then (mostly) being confirmed with a fluke tester.

Is there an easy way for me to run TDR on all gigabit ports?

I don't mind logging in to each stack, but doing each port manually is not sensible.

My plan was to log in about 3am when the users are at home and run the tests.

edit: update labels

[Leo Laohoo]

Oooooo ... TDR on a 2960X (specifically a 2960X) can really spell disaster if the switch/stack is running old codes. 

If I remembered correctly,15.0(2)EX and 15.2(2)E does not support TDR command at all. In the mid-part of 15.2(2)E, the TDR function was enabled but the output was very inaccurate.  

(The Cisco SE, who "champion" or "sponsored" my TDR request, said the BU did not mean for the 2960X to have TDR function.)

It would be good if the the stack was running something more recent, like 15.2(7)E5 or something. 

---

@Magnets wrote:

Is there an easy way for me to run TDR on all gigabit ports?

---

There was never the need to do this hence a "range" feature was never envisaged. 

---

@Magnets wrote:

My plan was to log in about 3am when the users are at home and run the tests.

---

I do it any time I want to.  The "hit" will not take long.  Besides, I would rather something was "active" or "live" when I do TDR.  

[Magnets]

"I do it any time I want to.  The "hit" will not take long.  "

Thanks for response Leo, I'm unsure why it has been marked as solved (i'm a beginner on these forums so perhaps i wasn't clear enough).

Each individual test will not take long, true, however i have thousands of ports that needs testing and no way that i know of of automating it.

My switches are running 15.2(6r)E

Why was there never a need to do a range of tdr? Sorry if i missed something obvious.

[Leo Laohoo · Accepted solution]

---

@Magnets wrote:

My switches are running 15.2(6r)E

---

15.2(6r)E is the ROMMON version.  

What is the IOS version?

---

@Magnets wrote:

Why was there never a need to do a range of tdr?

---

A lot of people use TDR daily but not a lot of people requests for a "range" of ports to do TDR.  And it is too late now because 2960X is already reaching sunset.

[Magnets]

oops, sorry. IOS is  15.2(7)E2

[Magnets]

thanks for the replies.

I will have to put something horrible together involving python and pscp

[Leo Laohoo]

---

@Magnets wrote:

thanks for the replies.

I will have to put something horrible together involving python and pscp

---

Don't.  

Use SNMP.  

We had an SNMP script that could do this and present the output onto a webpage.  
Shooting SNMP is less CPU-intensive.

[Magnets · Accepted solution]

Thanks.

will look into it.

[Georg Pauwen]

Hello,

on a side note, and I have not read the entire thread, are you running the 'tdr test cable interface' command ? An EEM script might be able to do this as well...

---

[Magnets]

i am. 

I don't know anything about EEM scripts, but will have a google. thanks. If i do ever find a way to automate it i'll post the script on this thread.