You could connect a console and just leave it logging until the next reload. I haven't seen it on switches, but I've see other boxes crash without writing a crashinfo file. If it crashes or reloads for any software related reason it will probably show something in the console.
-Pete On Tue, Jan 11, 2011 at 2:25 PM, Jeff Kell <[email protected]> wrote: > On 1/11/2011 11:29 AM, Seth Mattinen wrote: >> The cisco-nsp mailing list is often much more helpful than TAC. > > On that note... does this ring any bells? > > Have a 3750E that has had spurious reloads (4 since Friday), was > switch-1 of a 3-member stack, initially was the master, now switch-2 has > taken over as master. Show version on the failing one just shows > >> FunnyFarm-1 uptime is 17 hours, 48 minutes >> System returned to ROM by power-on > > The other members have 23-week uptimes. > > There's no crashinfo in the logs, no "software forced reload" type > reload events. > > TAC insists power was cut to the switch (four times?). > > Stack members are in a pair of self-contained, self-cooling Liebert > racks, 240v PDUs, different phases of a 3-phase supply, dual UPS, > generator backup, it's your "above average" server room. There are > dozens of servers in these racks (3 x 48-port 3750Es full, mostly > dual-connected) and nothing has burped whatsoever. > > Running 12.2(53)SE2 IPServices. Stack has been up almost 6 months > (switch-3, a 3750X, was added about 4 months ago and has a 19-week > uptime). No incidents until Friday, and no changes then that we can > identify. > > Jeff > > _______________________________________________ > 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/
