-----Original Message-----
From: Gert Doering [mailto:g...@greenie.muc.de]
Sent: Thursday, January 27, 2011 1:39 AM
To: Mack McBride
Cc: Church, Charles; nsp-cisco
Subject: Re: [c-nsp] Move from SXI4 to SXI5
Hi,
On Wed, Jan 26, 2011 at 10:57:39PM -0800, Mack McBride wrote:
> I have only encountered one bug (Cisco internal bug - not public)
> related to IPv6 routes covering ::/96 You will get a health test fail on
> reboot. The sup will register a minor error and the 67xx blades with DFC will
> fail to boot due to major error. Work around is to avoid statics for default
> or routes covering ::/96.
> ACLs can cover the ::/96 instead of null routes.
Ugh. This is scary. Do you have a bug ID? (Even if it's internal, it might
be useful to give to TAC to have them tell me when it's fixed...)
Just testing... rebooting a Sup720-10G with SXI5 and a static IPv6 default
route (lab router, and for the SXI5 testing, it didn't have IPv6 on it yet),
and I don't see anything unusual in the messages on the console. No DFC
modules, though, but I had expected to see something for the Sup...
*Jan 27 08:08:50: %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module
in slot 5 became active.
*Jan 27 09:08:53: %DIAG-SP-6-RUN_COMPLETE: Module 5: Running Complete
Diagnostics...
*Jan 27 09:09:06: %DIAG-SP-6-DIAG_OK: Module 5: Passed Online Diagnostics
What sort of log message do you see?
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
------ reply -----
You would need something that will be up when the supervisor boots.
In our specific cast it was 'ipv6 route ::/3 Null0' although 'ipv6 route ::/96
Null0' will work as well.
These blocks should not be routing traffic.
The error is:
SP: *Aug 3 03:39:11.759 MDT: %DIAG-6-RUN_COMPLETE: Module 5: Running
Complete Diagnostics...
SP: *Aug 3 03:39:22.128 MDT: %DIAG-3-MINOR: Module 5: Online Diagnostics
detected a Minor Error. Please use 'show diagnostic result <target>' to see
test results.
SP: *Aug 3 03:39:22.132 MDT: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 5:
TestFibDevices failed
We did more extensive testing in our lab and found that a default would cause
DFC equipped blades to fail if it came up before the DFCs ran the
TestFibDevices test but it was a Major Error instead of a minor error. CFC and
non-DFC blades do not show this behavior.
*Dec 1 21:33:31.824 MST: %DIAG-SP-3-MAJOR: Module 8: Online Diagnostics
detected a Major Error. Please use 'show diagnostic result <target>' to see
test results.
*Dec 1 21:33:31.828 MST: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 8:
TestFibDevices failed
*Dec 1 21:33:37.600 MST: %OIR-SP-3-LC_FAILURE: Module 8 has Major online
diagnostic failure, Card will be reset to re-run diagnostic. Please check
sup-bootflash diaginfo file for previous detailed diagnostic result.
Bug ID is CSCsu61601 - Module 5: TestFibDevices failed
(DIAG_CHECK_IPV6_PAK_ERROR)
Mack
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
