Diagnostic Error

[ADIL ALTAEE]

How can I stop a show tech command from continuously running which take up to 10 min time?

and in what section in the result should I search if I'm searching for a hardware issue. 

the issue is: 

%PM-SP-4-ERR_DISABLE: diagnostics error detected on Gi2/32, putting Gi2/32 in err-disable state

 I was told to copy the result of this command to figure out the issue

.is there a way better than stoping it in the middle

[Mark Malone]

You don't stop a show tech , its what TAC would request its the full switch output info and what you load into the analyzer to see what the issue is
If you want smaller output dont use the show tech command

Usually you capture the show tech and save it or if you want to view all of it alter your terminal lines in the putty application , logging section in putty is where you set it up to save

https://damn.technology/capture-cisco-config-with-putty

If you don't want to run a show tech and you want to try review the issues , you can run your own diagnostics on it

https://community.cisco.com/t5/networking-documents/how-to-run-gold-diagnostic-tests-on-catalyst-6500-6000-series/ta-p/3132712

[pieterh]

you may be able to interrupt the output with

     <ctrl->^ X

information my be found while doing only 

     show logging

you may be able to retrieve the output quicker if you telnet/ssh into the device

and before show tech, do a 

     term len 0

[Matt Delony]

Hello ADIL ALTAEE

Show tech shouldn't take a long time to run, unless you run it on the console port which is very slow. I checked and it should work if you press Ctrl+shift+6 several times to stop a show tech.

Regarding the error message, it is reporting that interface G2/32 is being err-disabled due to diagnostic error. You can check for err-disabled interface status with the command "show interface status err-disable".

Based on the error message mnemonic, this looks to have come from a C6500 supervisor such as sup32 or sup720. you would want to check the diagnostic result for module 2 and check which diagnostic test is failing. you can check this with the command "show diagnostic result module 2 detail". Look for any diagnostic failures here with interface G2/32.

[ADIL ALTAEE]

thank you for replying 
I should add, this diagnostic error is not only on port32, but it is also on 34 ports. these 34 ports get in this state in the first booting of the switch. there are another 2 ports(their status is disabled) gets in this state(err-disable) when issuing "no shutdown" command. 

as for other 12 ports, they are working fine

I will try what you said and see what the result

[ADIL ALTAEE]

TestLoopback:

Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
----------------------------------------------------------------------------
F F F F F F F F F F F F F F F F F F F F F F F F

Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
----------------------------------------------------------------------------
. F . F . F . F . F . F . F . F . F . F . F . F

Error code ------------------> 43 (DIAG_CHECK_ETHER_PAK_ERROR)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Feb 03 2019 05:32:59
First test failure time -----> Feb 03 2019 05:32:59
Last test failure time ------> Feb 03 2019 05:32:59
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1

*all the ports that are pass(.) work fine(port 25, 27, 29,...., 47). others are err-disabled after reboot, except for port 1 and 2, they are err-disabled after issuing no shutdown on them.

TestUnusedPortLoopback:

Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
----------------------------------------------------------------------------
F F U U U U U U U U U U U U U U U U U U U U U U

Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
----------------------------------------------------------------------------
U U U U U U U U U U U U U U U U U U U U U U U U

Error code ------------------> 43 (DIAG_CHECK_ETHER_PAK_ERROR)
Total run count -------------> 3925
Last test testing type ------> Health Monitoring
Last test execution time ----> Feb 06 2019 09:48:55
First test failure time -----> Feb 03 2019 05:36:04
Last test failure time ------> Feb 06 2019 09:48:55
Last test pass time ---------> n/a
Total failure count ---------> 3925
Consecutive failure count ---> 3925

[ADIL ALTAEE]

What could I do next?
it is a supervisor 720 if this could help
thank you very much for your assistance