[c-nsp] Chassis Switch "Parity Errors"

[Blake Pfankuch - Mailing List]

We thought about the memory, but the one switch had been up and running for 7 years prior, and the second one was functioning for 2 before the crash.  As far as just waiting to see if it reoccurs, that's the conclusion we came to as well.  At this point we are blaming it on 7-10 year old hardware, and trying to hold out until next year when we are slated to replace everything.  

Thanks for confirming what I was thinking :)

Blake

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Phil Mayers
Sent: Wednesday, May 8, 2013 3:47 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Chassis Switch "Parity Errors"

On 05/08/2013 10:42 AM, Blake Pfankuch - Mailing List wrote:
> Ok, this could get a little silly... I have 6 4000/6000 series chassis 
> switches.  The first crash was a WS-C6509-NEB-A on Tuesday at
> 0216 last week.  This morning (Wednesday) at 0233 I had a WS-C4506 
> crash.  Crash info on both devices cites a parity error as reason for 
> reboot.
>
> Aside from radiation shielding in the datacenter to block solar 
> flares, any suggestions on further debugging or prevention of these 
> errors?

In theory it could be bad hardware; a bad batch of RAM or something. But IMO it's unlikely.

If they're "real" parity errors, there's nothing to be done - it's a statistical thing, and you just have to live wth / ignore them.

Also, it need not be solar flares; ambient ionising radiation comes from many sources, depending on your local geography (amongst other things).
_______________________________________________
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/