[c-nsp] 6500 having a seizure

[ck]

sounds similar to CSCsi49150

On Thu, Feb 4, 2010 at 4:40 AM, Drew Weaver <drew.weaver at thenap.com> wrote:

> Hey Randy,
>
> 12.2(18)SXF17
>
> -Drew
>
> -----Original Message-----
> From: Randy McAnally [mailto:rsm at fast-serv.com]
> Sent: Wednesday, February 03, 2010 9:18 PM
> To: Drew Weaver; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] 6500 having a seizure
>
> What software release?
>
> --
> Randy
>
> ---------- Original Message -----------
> From: Drew Weaver <drew.weaver at thenap.com>
> To: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
> Sent: Wed, 3 Feb 2010 18:18:33 -0500
> Subject: [c-nsp] 6500 having a seizure
>
> > Hey all...
> >
> > So we've been having issues with this 6500 for awhile now, just
> > doing random stuff so we replaced the chassis and one of the Sups,
> > so today while I was at lunch (doesn't it always happen this way)
> >  the switch had one of these:
> >
> > System returned to ROM by Stateful Switchover (SP by bus error at PC
> > 0x402DF924, address 0x0)
> >
> > Good times, so after the switch finally "recovered" I noticed this
> > in my log:
> >
> > .Feb  3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/41 was
> > bounced by Consistency Check IDBS Up.
> > .Feb  3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/42 was
> > bounced by Consistency Check IDBS Up.
> > .Feb  3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/43 was
> > bounced by Consistency Check IDBS Up.
> > .Feb  3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/44 was
> > bounced by Consistency Check IDBS Up.
> > .Feb  3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/45 was
> > bounced by Consistency Check IDBS Up.
> > .Feb  3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/46 was
> > bounced by Consistency Check IDBS Up.
> > ..Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/48 was
> > bounced by Consistency Check IDBS Up.
> > Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/41 was
> > bounced by Consistency Check IDBS Down.
> > .Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/42 was
> > bounced by Consistency Check IDBS Down.
> > .Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/43 was
> > bounced by Consistency Check IDBS Down.
> > .Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/44 was
> > bounced by Consistency Check IDBS Down.
> > .Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/45 was
> > bounced by Consistency Check IDBS Down
> > .Feb  3 15:47:00.304 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/47 was
> > bounced by Consistency Check IDBS Down.
> > .Feb  3 15:47:00.304 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/48 was
> > bounced by Consistency Check IDBS Down
> >
> > Since then we replaced the other supervisor which we suspect might
> > be bad, but we're trying to figure out if there is an actual REASON
> > for that:
> >
> > Feb  3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/41 was
> > bounced by Consistency Check IDBS Down.
> >
> > error... We had to go in and shut/no shut interfaces 3/41 - 3/48
> > manually before the VLANs would come back up...
> >
> > We would like to avoid any more epilepsy from this box if possible,
> >  any ideas?
> >
> > thanks,
> > -Drew
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> ------- End of Original Message -------
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>