Well, as feedback for the issue raised, the bug you flagged is not causing anything other than a traceback message...
Arie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Arie Vayner (avayner) Sent: Tuesday, November 17, 2009 10:11 To: Jared Mauch; [email protected] Subject: Re: [c-nsp] how not to write a release note Jared, I took a quick look and this has to do with QOS. I have sent an internal query for more info. Will advise. Arie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jared Mauch Sent: Tuesday, November 17, 2009 01:11 To: [email protected] Subject: [c-nsp] how not to write a release note Seems cisco is getting lazy.. SXI3 is out and this has to be one of the worst release notes ever: CSCta14457 - A Cisco device may report alignment errors "%ALIGN-3-TRACE" error messages accompanied with a traceback may be reported. Does not say anything about what may trigger it, eg: mtu, packet fragmentation, etc.. - Jared -- Jared Mauch | pgp key available via finger from [email protected] clue++; | http://puck.nether.net/~jared/ My statements are only mine. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
