[c-nsp] C6k diag failure in lab, need to worry?
Peter Rathlev
peter at rathlev.dk
Wed Apr 9 11:40:16 EDT 2008
'ello,
We just had a "funny" experience with a C6k/720 in our lab. We were
testing SXF13 AIS, and during a reload we saw the following:
00:01:36: %SCHED-SP-7-WATCH: Attempt to monitor uninitialized watched
bitfield (address 0).
-Process= "Shutdown", ipl= 0, pid= 256
-Traceback= 402C3A18 404ED840 4029C954 4029C940
00:01:40: %DIAG-SP-3-MAJOR: Module 5: Online Diagnostics detected a
Major Error.
Please use 'show diagnostic result <target>' to see test results.
00:01:40: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 5: TestAclDeny
failed
00:01:41: %OIR-SP-6-INSCARD: Card inserted in slot 5, interfaces are now
online
Reload scheduled for 07:05:31 PST Wed Apr 9 2008 (in 13 seconds)
Module 5 is the supervisor. Afterwards it reloaded and didn't do it
again, also across several reboots. It's a Sup720-3B with a single
WS-X6708-10GE and a WS-SVC-FWM-1. It never reaches starting GOLD for the
DFC.
I didn't have the time to do the "show diagnostics result" before
reboot, and afterwards it say it never got a failure on TestAclDeny:
fw1#sh diagnostic res mod 5 test 18 det
Current bootup diagnostic level: minimal
Test results: (. = Pass, F = Fail, U = Untested)
___________________________________________________________________________
18) TestAclDeny ---------------------> .
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 1
Last test execution time ----> Apr 09 2008 07:08:26
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 09 2008 07:08:26
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
fw1#
None of the other tests show any failures either: "show diagnostics
result module 5 detail | incl failure" gives only "0" and "n/a" stats. I
can do "diagnostic start module 5 test 18" all I want and no failures by
the way, just getting "%DIAG-SP-6-TEST_OK: Module 5: TestAclDeny{ID=18}
has completed successfully" and no problems.
Is this something we should try and dig into, reporting it to TAC? Or
should we just ignore this ~5 min delay in a lab reboot? We can't seem
to reproduce it. :'(
The box had just been "upgraded" to SXF13 AES shortly before (from SXF6
AIS) due to some miscommunications, and this was the first boot on SXF13
AIS, but I can't imagine this can have any impact.
Regards,
Peter
More information about the cisco-nsp
mailing list