[96164] in North American Network Operators' Group
Re: BGP Problem on 04/16/2007
daemon@ATHENA.MIT.EDU (Stephen Wilcox)
Fri Apr 20 11:11:15 2007
Date: Fri, 20 Apr 2007 16:05:14 +0100
From: Stephen Wilcox <steve@telecomplete.co.uk>
To: Daniele Arena <daniele.arena@gmail.com>
Cc: "Elmar K. Bins" <elmi@4ever.de>, nanog@merit.edu
In-Reply-To: <f8f07cf00704200752j3d0b62a1l12852db0a06d26d2@mail.gmail.com>
Errors-To: owner-nanog@merit.edu
On Fri, Apr 20, 2007 at 04:52:04PM +0200, Daniele Arena wrote:
>
> >> I remember this because I had such a reload and it was during a period
> >of heavy cosmic activity.. as the hardware had always been reliable and
> >was reliable after this was beleived to be the cause
> >
> >We have also started to use this as the standard excuse.
> >Up to now, people believe us...
>
> Well, there is some documentation on Cisco containing references to
> cosmic rays and parity errors:
>
> http://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a00800942e0.shtml
>
> Cisco 7200 Parity Error Fault Tree
>
> "As with all computer and networking devices, the NPE is susceptible
> to the rare occurrence of parity errors in processor memory. Parity
> errors may cause the system to reset and can be a transient Single
> Event Upset (SEU or soft error) or can occur multiple times (often
> referred to as hard errors) due to damaged hardware. SEUs or soft
> errors are caused by "noise" most frequently due to high-energy
> neutrons generated in the atmosphere by cosmic rays. For more
> information on SEUs, refer to the Increasing Network Availability
> page.
yup, thats the reference i was referring to.. we indeed had a single event upset on an NPE :)
Steve
