04-19-2013 04:29 PM - edited 03-07-2019 12:55 PM
hi, i have a standalone SUP720, no traffic is passing through it. only one port connected for remote telnet, its kind of backup device.
today i checked its log, and there are some wiered message.
is it a software bug or my SUP has gone bad?
any suggestion/help would be appreciated.
*Apr 19 18:19:02: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:5
*Apr 19 18:19:03: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=2% Traffic=0%
netint_thr_active[0], Tx_Rate[658], Rx_Rate[80], dev=4[IPv6, fail=5]
*Apr 19 18:20:29: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:10
*Apr 19 18:20:30: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[676], Rx_Rate[100], dev=4[IPv6, fail=10]
*Apr 19 18:21:56: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:15
*Apr 19 18:21:57: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=1% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[636], Rx_Rate[80], dev=4[IPv6, fail=15]
*Apr 19 18:23:23: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:20
*Apr 19 18:23:24: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[636], Rx_Rate[80], dev=4[IPv6, fail=20]
*Apr 19 18:24:50: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:25
*Apr 19 18:24:51: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=5% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[538], Rx_Rate[20], dev=4[IPv6, fail=25]
*Apr 19 18:26:16: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:30
*Apr 19 18:26:17: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=1% Traffic=0%
netint_thr_active[0], Tx_Rate[578], Rx_Rate[40], dev=4[IPv6, fail=30]
*Apr 19 18:27:43: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:35
*Apr 19 18:27:44: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=6% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[608], Rx_Rate[80], dev=4[IPv6, fail=35]
*Apr 19 18:29:10: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:40
*Apr 19 18:29:11: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=5% RP=2% Traffic=0%
netint_thr_active[0], Tx_Rate[670], Rx_Rate[100], dev=4[IPv6, fail=40]
*Apr 19 18:30:36: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:45
*Apr 19 18:30:37: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[608], Rx_Rate[80], dev=4[IPv6, fail=45]
*Apr 19 18:32:03: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:50
*Apr 19 18:32:04: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=2% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[698], Rx_Rate[100], dev=4[IPv6, fail=50]
*Apr 19 18:33:30: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:55
*Apr 19 18:33:31: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[658], Rx_Rate[80], dev=4[IPv6, fail=55]
*Apr 19 18:34:56: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:60
*Apr 19 18:34:57: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[653], Rx_Rate[100], dev=4[IPv6, fail=60]
*Apr 19 18:36:23: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:65
*Apr 19 18:36:24: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=4% RP=2% Traffic=0%
netint_thr_active[0], Tx_Rate[578], Rx_Rate[60], dev=4[IPv6, fail=65]
*Apr 19 18:36:58: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 6 TestSPRPInbandPing recovered after 66 consecutive failure(s)
*Apr 19 18:38:24: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:5
*Apr 19 18:38:25: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[653], Rx_Rate[100], dev=4[IPv6, fail=5]
*Apr 19 18:39:35: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 6 TestSPRPInbandPing recovered after 8 consecutive failure(s)
*Apr 19 18:42:08: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:5
*Apr 19 18:42:09: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=4% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[670], Rx_Rate[100], dev=4[IPv6, fail=5]
*Apr 19 18:43:34: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 6 TestSPRPInbandPing recovered after 9 consecutive failure(s)
05-15-2013 01:49 PM
Oh and if it is a Cisco module in 6/2 it probably isn't. If that makes sense? There are fakes being inserted into the supply chain. Cisco is doing a lot to prevent this, but there will undoubtably be fakes around.
05-15-2013 03:49 PM
Hi, i am not concerned about 6/1, 6/2 Non Cisco SFP.
i am concerned about these errors
*May 15 18:01:30: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics...
*May 15 18:01:40: %DIAG-SP-3-MINOR: Module 1: Online Diagnostics detected a Minor Error. Please use 'show diagnostic result
*May 15 18:01:40: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 1: TestL3VlanMet failed
*May 15 18:01:41: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online
*May 15 18:02:54: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:5
*May 15 18:02:55: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=1% Traffic=0%
netint_thr_active[0], Tx_Rate[658], Rx_Rate[80], dev=4[IPv6, fail=5]
*May 15 18:04:21: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 6 TestSPRPInbandPing consecutive failure count:10
*May 15 18:04:22: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[516], Rx_Rate[20], dev=4[IPv6, fail=10]
*May 15 18:05:13: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 6 TestSPRPInbandPing recovered after 12 consecutive failure(s)
05-15-2013 03:47 PM
Your chassis is having a backplane issue. You may need to RMA the entire chassis.
05-20-2013 12:37 PM
Could there be any other issue except Chases back plane?
Also if i dont have Cisco Contract for RMA. Can i do sort of Repair contract now , so if they can repair it etc? not sure if its an option
05-20-2013 12:56 PM
Your backplane is not at fault. All your errors relate to module 6 which you say is the Sup720. Did you try swapping out the SFP in 6/2 that I suggested in an earlier post? You have many errors for a non-Cisco SFP. Save the money and swap that or remove it. See if the errors persist. But I would stake a lot on you not having an issue with the backplane
05-21-2013 01:24 PM
Hi, i have removed SFP from SUP slot, SFP error are gone.
But my concern is not SFP unsupported modules. my concern is fllowing error of
Module 5 TestSPRPInbandPing consecutive failure count
*May 21 14:47:33: %OIR-SP-6-INSPS: Power supply inserted in slot 1
*May 21 14:47:33: %C6KPWR-SP-4-PSOK: power supply 1 turned on.
*May 21 14:47:33: %OIR-SP-6-INSPS: Power supply inserted in slot 2
*May 21 14:47:34: %C6KENV-SP-4-FANHIOUTPUT: Version 2 high-output fan-tray is in effect
*May 21 14:47:36: %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
*May 21 14:47:36: %DIAG-SP-6-RUN_MINIMUM: Module 5: Running Minimal Diagnostics...
*May 21 14:48:00: %DIAG-SP-6-DIAG_OK: Module 5: Passed Online Diagnostics
*May 21 14:48:00: %OIR-SP-6-INSCARD: Card inserted in slot 5, interfaces are now online
*May 21 14:48:03: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics...
*May 21 14:48:13: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics
*May 21 14:48:13: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online
*May 21 15:02:44: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:5
*May 21 15:02:45: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[556], Rx_Rate[40], dev=4[IPv6, fail=5]
*May 21 15:04:11: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:10
*May 21 15:04:12: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=1% Traffic=0%
netint_thr_active[0], Tx_Rate[516], Rx_Rate[20], dev=4[IPv6, fail=10]
*May 21 15:05:37: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:15
*May 21 15:05:38: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=5% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[608], Rx_Rate[80], dev=4[IPv6, fail=15]
*May 21 15:07:04: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:20
*May 21 15:07:05: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[648], Rx_Rate[100], dev=4[IPv6, fail=20]
*May 21 15:08:31: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:25
*May 21 15:08:32: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[976], Rx_Rate[239], dev=4[IPv6, fail=25]
*May 21 15:09:57: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:30
*May 21 15:09:58: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=2% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[698], Rx_Rate[100], dev=4[IPv6, fail=30]
*May 21 15:11:24: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:35
*May 21 15:11:25: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[636], Rx_Rate[80], dev=4[IPv6, fail=35]
*May 21 15:12:51: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:40
*May 21 15:12:52: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=6% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[516], Rx_Rate[40], dev=4[IPv6, fail=40]
*May 21 15:14:17: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:45
*May 21 15:14:18: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=1% Traffic=0%
netint_thr_active[0], Tx_Rate[556], Rx_Rate[40], dev=4[IPv6, fail=45]
*May 21 15:15:44: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:50
*May 21 15:15:45: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[648], Rx_Rate[100], dev=4[IPv6, fail=50]
*May 21 15:17:11: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:55
*May 21 15:17:12: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[630], Rx_Rate[80], dev=4[IPv6, fail=55]
*May 21 15:17:27: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 5 TestSPRPInbandPing recovered after 55 consecutive failure(s)
05-20-2013 03:14 PM
1 Minor Error
2 Pass3 Minor Error
4 Minor Error
5 Pass
6 Minor Error
This output lends to my opinion that you've got a backplane issue.
I have never seen an error like this before.
05-21-2013 01:27 PM
Hi, i removed all Cards, and now only one Ethernet and one Sup card. ( also removed non Cisco SFP from Sup slot )
now i dont see those minor errors. and it states PASS. But still receiving those TestSPRPInbandPing errors.
Also i changed SUP slot to 5 but didnt make a difference.
6506BK# sh module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-TX
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0008.7dce.fae8 to 0008.7dce.fb17 10.1 7.2(1) 8.5(0.46)RFW Ok
5 0011.21b5.6c34 to 0011.21b5.6c37 3.2 8.1(3) 12.2(18)SXF1 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
5 Policy Feature Card 3 WS-F6K-PFC3A 2.4 Ok
5 MSFC3 Daughterboard WS-SUP720 2.4 Ok
Mod Online Diag Status
---- -------------------
1 Pass
5 Pass
*May 21 15:02:44: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:5
*May 21 15:02:45: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[556], Rx_Rate[40], dev=4[IPv6, fail=5]
*May 21 15:04:11: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:10
*May 21 15:04:12: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=1% Traffic=0%
netint_thr_active[0], Tx_Rate[516], Rx_Rate[20], dev=4[IPv6, fail=10]
*May 21 15:05:37: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:15
*May 21 15:05:38: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=5% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[608], Rx_Rate[80], dev=4[IPv6, fail=15]
*May 21 15:07:04: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:20
*May 21 15:07:05: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[648], Rx_Rate[100], dev=4[IPv6, fail=20]
*May 21 15:08:31: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:25
*May 21 15:08:32: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[976], Rx_Rate[239], dev=4[IPv6, fail=25]
*May 21 15:09:57: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:30
*May 21 15:09:58: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=2% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[698], Rx_Rate[100], dev=4[IPv6, fail=30]
*May 21 15:11:24: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:35
*May 21 15:11:25: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[636], Rx_Rate[80], dev=4[IPv6, fail=35]
*May 21 15:12:51: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:40
*May 21 15:12:52: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=6% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[516], Rx_Rate[40], dev=4[IPv6, fail=40]
*May 21 15:14:17: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:45
*May 21 15:14:18: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=1% Traffic=0%
netint_thr_active[0], Tx_Rate[556], Rx_Rate[40], dev=4[IPv6, fail=45]
*May 21 15:15:44: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:50
*May 21 15:15:45: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=3% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[648], Rx_Rate[100], dev=4[IPv6, fail=50]
*May 21 15:17:11: %CONST_DIAG-SP-3-HM_TEST_FAIL: Module 5 TestSPRPInbandPing consecutive failure count:55
*May 21 15:17:12: %CONST_DIAG-SP-6-HM_TEST_INFO: CPU util(5sec): SP=7% RP=0% Traffic=0%
netint_thr_active[0], Tx_Rate[630], Rx_Rate[80], dev=4[IPv6, fail=55]
*May 21 15:17:27: %CONST_DIAG-SP-6-HM_TEST_RECOVERED: Module 5 TestSPRPInbandPing recovered after 55 consecutive failure(s)
I am arranging for an OLD Chasis from store room to test SUP in that, to see if SUP is faulty or Chasis. Mean while any suggestions would be helpful
05-21-2013 01:35 PM
Here is funny thing.
Detail Diagnostic of Module 5 saying no Error on that test
6506BK#sh diagnostic result module 5 detail
Current bootup diagnostic level: minimal
Module 5: Supervisor Engine 720 (Active)
Overall Diagnostic Result for Module 5 : PASS
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
2) TestSPRPInbandPing --------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 228
Last test execution time ----> May 21 2013 15:50:32
First test failure time -----> May 21 2013 15:01:32
Last test failure time ------> May 21 2013 15:17:08
Last test pass time ---------> May 21 2013 15:50:32
Total failure count ---------> 55
Consecutive failure count ---> 0
CPU util(5sec) SP -----------> 4%
CPU util(5sec) RP -----------> 1%
Traffic ---------------------> 0%
netint_thr_active -----------> 0
Inband Tx_Rate --------------> 834
Inband Rx_Rate --------------> 179
Per-device Failure Count ----> n/a
05-21-2013 03:10 PM
If this is the diagnostics result from the OLD chassis, then your other chassis could have a faulty backplane.
08-16-2013 12:41 PM
Finally after long long time, i was able to change Chasis for 6506 Switch. and i am gettign same error on other chasis.
so its SUP720 issue for sure.
Not sure where to go now :-s not sure if its reliable any more or not:(
sh diagnostic result module 6 detail
Current bootup diagnostic level: minimal
Module 6: Supervisor Engine 720 (Active) SerialNo : .
Overall Diagnostic Result for Module 6 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
___________________________________________________________________________
1) TestScratchRegister -------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 28137
Last test execution time ----> Aug 16 2013 14:51:57
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 16 2013 14:51:57
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
2) TestSPRPInbandPing --------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 54865
Last test execution time ----> Aug 16 2013 14:52:12
First test failure time -----> Aug 05 2013 13:25:36
Last test failure time ------> Aug 16 2013 14:52:12
Last test pass time ---------> n/a
Total failure count ---------> 54865
Consecutive failure count ---> 54865
CPU util(5sec) SP -----------> 3%
CPU util(5sec) RP -----------> 0%
Traffic ---------------------> 0%
netint_thr_active -----------> 0
Inband Tx_Rate --------------> 856
Inband Rx_Rate --------------> 179
Per-device Failure Count ----> 4[IPv6, fail=54865]
___________________________________________________________________________
3) TestTransceiverIntegrity:
Port 1 2
----------
U U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
4) TestActiveToStandbyLoopback:
Port 1 2
----------
U U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
5) TestLoopback:
Port 1 2
----------
. .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:24:56
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:24:56
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
6) TestNewIndexLearn ---------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:24:57
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:24:57
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
7) TestDontConditionalLearn --------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:24:58
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:24:58
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
8) TestBadBpduTrap -----------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:24:58
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:24:58
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
9) TestMatchCapture ----------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:24:59
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:24:59
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
10) TestProtocolMatchChannel --------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:01
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:01
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
11) TestFibDevices ------------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:03
First test failure time -----> Aug 05 2013 13:25:03
Last test failure time ------> Aug 05 2013 13:25:03
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1
___________________________________________________________________________
12) TestIPv4FibShortcut -------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:04
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:04
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
13) TestL3Capture2 ------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:04
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:04
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
14) TestIPv6FibShortcut -------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:04
First test failure time -----> Aug 05 2013 13:25:04
Last test failure time ------> Aug 05 2013 13:25:04
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1
___________________________________________________________________________
15) TestMPLSFibShortcut -------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:05
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
16) TestNATFibShortcut --------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:05
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
17) TestAclPermit -------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:05
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
18) TestAclDeny ---------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:05
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
19) TestQoSTcam ---------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:16
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:16
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
20) TestL3VlanMet -------------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:16
First test failure time -----> Aug 05 2013 13:25:16
Last test failure time ------> Aug 05 2013 13:25:16
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1
___________________________________________________________________________
21) TestIngressSpan -----------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:18
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:18
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
22) TestEgressSpan ------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:18
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:18
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
23) TestNetflowInlineRewrite:
Port 1 2
----------
U U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
24) TestFabricSnakeForward ----------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:18
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:18
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
25) TestFabricSnakeBackward ---------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:19
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:19
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
26) TestTrafficStress ---------------> U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
27) TestFibTcamSSRAM ----------------> U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
28) TestAsicMemory ------------------> U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
29) TestNetflowTcam -----------------> U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
30) ScheduleSwitchover --------------> U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
31) TestFirmwareDiagStatus ----------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:20
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Aug 05 2013 13:25:20
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
32) TestFabricFlowControlStatus -----> U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 0
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
Current run count -------------------------->: 0
First test execution time ------------------>:
Last test execution time ------------------->:
Total FPOE Rate0 Count --------------------->: 0
Total FPOE Reduced Rate Count -------------->: 0
___________________________________________________________________________
08-16-2013 10:55 PM
Ahmad,
Go ahead and create the RMA for the Sup module.
Reason:
Module 6: Supervisor Engine 720 (Active) SerialNo : .
Overall Diagnostic Result for Module 6 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
11) TestFibDevices ------------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:03
First test failure time -----> Aug 05 2013 13:25:03
Last test failure time ------> Aug 05 2013 13:25:03
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1________
14) TestIPv6FibShortcut -------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:04
First test failure time -----> Aug 05 2013 13:25:04
Last test failure time ------> Aug 05 2013 13:25:04
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1
20) TestL3VlanMet -------------------> F
Error code ------------------> 1 (DIAG_FAILURE)
Total run count -------------> 1
Last test execution time ----> Aug 05 2013 13:25:16
First test failure time -----> Aug 05 2013 13:25:16
Last test failure time ------> Aug 05 2013 13:25:16
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1
____________________________
Couple of test are been failing. AS we have already tried reseating and placing this card on different chassis the components on the Sup modules seems to be defect.
Please raise the RMA and get the new sup module.
HTH
regards
Inayath
*Plz rate all usefull posts.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide