Let's apply logic...
1 - What changed prior to the 'events'?
2 - What's common to all the impacted devices experiencing the
'events'? Location, vendor, etc
3 - Which other devices could be experiencing similar 'events' but
aren't.
Eninja
On Apr 29, 2010, at 8:13 AM, Mike <mike-
[email protected]> wrote:
For an additonal data point, the error has not recurred. HOWEVER,
all across my network (wireless ISP), I have been having 'events'
with all sorts of malfunctioning equipment; I've had blown out
microwave point to point links, locked up wireless access points and
strange rebootings, all in devices that otherwise have been up and
running for years now without issue. There's been so much stuff I've
been seriously considering the possibility of sabotage, except that
the types of issues and the types of gear simply don't lend
themselves to any sort of sabotage scenario I can think up short of
someone with an x-matter-mitter standing on the moon shooting alpha
particles at us.
Anyone else experiencing 'odd' failures lately??
Mike-
Tony wrote:
What's really strange is that we had a sup720 failover to the
redundant Sup in a 7609 recently. I opened a TAC case and the
reason I got for it from Cisco was:
=========
the device experienced a CPU parity error
...
These occur when an energy level within the chip (for example, a
one or a zero) changes - most often the result of cosmic
radiation. =========
The "resolution" was to monitor it for 48hrs and if it didn't
happen again it was a once off cause by cosmic radiation and
nothing they could do about it. The error didn't recur and so case
was closed.
_______________________________________________
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/
