the specific bug that caused my issue is *CSCta02715* Now, I find it scary that a command element related to logging could take down an array of 6500's. Furthermore, we had been running the SXH5 code with the "logging count" command element enabled on two of the four core switches for 30 days (the code had actually been running for three months+)
logging count is a way to quickly check log messages on a switch/router, and provides simple output that can be used to identify recurring and troubling issues. see: http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_logging_count.html On Mon, Sep 21, 2009 at 10:00 AM, Mark Tinka <[email protected]>wrote: > On Monday 21 September 2009 09:31:48 pm Steven Fischer > wrote: > > > as an aside, the TAC engineer (Indian engineer #4) stuck > > with it, and has found the bug that was causing the > > meltdown. Credit certainly needs to be given for that. > > Good stuff. > > Grateful if you could kindly share any technical experiences > about this issue, in case any of us go through the same with > our 6500 platforms. Thanks. > > Cheers, > > Mark. > -- To him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
