02-09-2012 05:03 PM - edited 03-03-2019 06:29 AM
Hello All,
First time on the forum, and I'm no Cisco expert (college co-op, actually) so my apologies if this is a humorously simple or misplaced post.
I have two WS-X6148-45AF linecards here that have been out of use for quite some time.
Upon inserting them in one of our 6509-E's I noticed that both had "Minor Error"s on their module diagnostics.
I would have just assumed that the cards were dead and requested replacements, but both cards have the *exact* same diagnostic errors, which only seem to effect every-other port. That's too much of a coincidence for me, so I figured I'd ask on the forums and see if I'm just missing something obvious before I assume the worst. Are these cards both somehow damaged in the exact same way? Or is there some config/compatibility issue that I haven't heard of?
relevant diagnostic output from one of the cards (Both outputs the same, no use posting twice) is below:
Router#show diagnostic result module 4
Current bootup diagnostic level: minimal
Module 4: 48-port 10/100 mb RJ45 SerialNo : SAL11391VUY
Overall Diagnostic Result for Module 4 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) 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
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
I have tried:
-Dusting the cards off
-Making sure the backplane connectors are not obviously damaged
-Using the cards in different slots
-Using the cards in different chassis
-Using the cards with different supervisors (though all were 720-3B's, and all the chassis were 6509-E's)
The diagnostic failures always come up the same, and are always identical. Again, two identical hardware failures seems a little too coincidental for me.
Any input would be greatly appreciated!
Thanks,
Dave G.
02-09-2012 05:09 PM
Run a disruptive diagnostics.
In enable mode, the command should be "diagnostic" and so-on. My apologies, I don't have a 6500E handy at home right now.
02-09-2012 05:33 PM
Thanks for the quick reply - output of show diagnostic result after "diagnostic start module 4 test all" was run:
Router#show diagnostic result module 4
Current bootup diagnostic level: minimal
Module 4: 48-port 10/100 mb RJ45 SerialNo : XXXXXXXXXX
Overall Diagnostic Result for Module 4 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) 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
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
2) TestNetflowInlineRewrite:
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 F F F F F F F F F F F F
3) TestEobcStressPing --------------> .
4) TestFirmwareDiagStatus ----------> .
5) TestAsicSync --------------------> .
6) 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
----------------------------------------------------------------------------
U U 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
7) TestErrorCounterMonitor ---------> U
8) TestPortTxMonitoring:
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
----------------------------------------------------------------------------
U U 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
9) TestVDB -------------------------> .
Let me know if you need anything more - though I will be leaving the office for the evening in a few.
Thanks again for your time!
02-09-2012 09:43 PM
Like I said, run a DISRUPTIVE diagnostics. The command should start with "diagnostics" and you have to specify the module and the level of diagnostics.
What is your IOS and have you tried to re-seat the line card?
Have you tried moving the line card to a different slot?
02-10-2012 11:52 AM
I have already tried the following:
-Dusting the cards off
-Making sure the backplane connectors are not obviously damaged
-Using the cards in different slots
-Using the cards in different chassis
-Using the cards with different supervisors (though all were 720-3B's, and all the chassis were 6509-E's)
Current IOS version looks like "s72033_rp-ADVENTERPRISEK9_WAN-M"
As for the disruptive tests, correct me if I'm wrong:
Disruptive tests are indicated on the test ID list with attribute indicator "D"
Router#diagnostic start module 4 test ?
{..omitted..}
all Select all test ID
complete Select the Complete bootup test suite [Attribute = C]
minimal Select the Minimal bootup test suite [Attribute = M]
non-disruptive Select the Non-Disruptive test suite [Attribute = N]
per-port Select the Per-Port test suite [Attribute = P]
So running "diagnostic start module 4 test all" should run disruptive diagnostics, which is what I ran prior to posting my last "show diagnostic result module 4" output.
As far as I know, there is no way to specify a disgnostic with option "disruptive".
I am currently running a "diagnostic start system test all", to see if that turns up anything else - this is the closest thing to a truly disruptive diagnostic that I can think of.
Thanks again, sorry if I got any of my lingo wrong.
02-10-2012 02:00 PM
"all" option is disruptive. Wierd because you have some results as "U" which is un-tested.
Looks like it's time for you to RMA both cards. The diagnostics result looks pretty bad.
Can you post the "sh version"?
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