<div>I am being told this is a SW bug, more specifically it is a corruption of the DNS cache entry. When this entry is accessed for aging, the system reset. Workaround is to diable DNS resoultion for now. We will see</div>
<div>if this fixes the problem.</div>
<div> </div>
<div>mike<br><br></div>
<div class="gmail_quote">On Wed, Sep 23, 2009 at 10:32 PM, Tammy A. Wisdom <span dir="ltr"><<a href="mailto:tammy-lists@wiztech.biz">tammy-lists@wiztech.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">has anyone looked closely @ the BI/FI boards to see if the capacitors are leaking? the gunk they dump out when they leak eats the traces & is conductive. If anyone wants to send me one for autopsy I'd be more than willing to look at it under high magnification to see if there is signs of leaking. Catch me off list if you have one you could let me autopsy :)<br>
Thanks,<br><br>--Tammy<br>
<div>
<div></div>
<div class="h5"><br>----- "Aaron Wendel" <<a href="mailto:aaron@wholesaleinternet.net">aaron@wholesaleinternet.net</a>> wrote:<br><br>> Same thing. Had a BI start rebooting randomly, finally degraded into<br>
> every minute or two. A management card replacement fixed it. Also had<br>> an issue recently with random IPs not working. Turned out to be a bad<br>> card.<br>><br>><br>><br>> Aaron<br>><br>><br>
><br>><br>><br>><br>><br>> From: <a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a><br>> [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] On Behalf Of Joseph<br>
> Hardeman<br>> Sent: Wednesday, September 23, 2009 7:25 PM<br>> To: harbor235<br>> Cc: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>> Subject: Re: [f-nsp] CRASH<br>><br>
><br>><br>> Hi Mike,<br>><br>> I had the same issue with an FI a few months ago, it started rebooting<br>> on its own and I was getting Warm Restart in my syslog server. I don't<br>> remember what the trap reason was, but I ended up replacing the<br>
> management card and its been fine ever since. Only the people at<br>> Brocade have the tools to debug the output, which is unfortunate.<br>><br>> Joe<br>><br>> harbor235 wrote:<br>><br>><br>> I recently had a crash on a BigIron, can anyone offer any assistance<br>
> on how to troubleshoot<br>><br>><br>> this problem, is Brocade the only resource? Here is some info on the<br>> crash, has anyone else seen this?<br>><br>><br>><br>><br>><br>> ACTIVE CPU MODULE:<br>
> There have been 2 reboots since power on or last counter reset<br>> Crashed image: Version 08.0.01tT53,<br>> Compiled on Mar 04 2009 at 22:12:06 labeled as B2R08001t<br>> Crash time: 20:12:00 GMT-05 Mon Sep 21 2009<br>
><br>><br>> EXCEPTION VECTOR :0x00000300<br>> TRAP REASON - Data Access Exception<br>> The address of the instruction that caused the exception is stored in<br>> SRR0<br>><br>><br>> The system had been up for 24738 minutes<br>
> General Registers:<br>> 2022fbc4 20a5bfa0 20944390 00000000 00000000 000060a2 208ef814<br>> 00000000<br>> 00000020 00000240 00000000 00000000 2670487d 20a50ae0 ff0001ff<br>> 20000000<br>> 20000000 00000000 10000000 20000104 22341fad 00000200 003ad9fc<br>
> 003ad9de<br>> 00800200 20a5017c 00000001 3fffffe0 00000000 000060a2 00000002<br>> ffffffff<br>><br>><br>> halt = 3ffff000, extra = 3ffff13c, output = 3ffff714, stack =<br>> 3ffff800<br>> **srr0 = 2022fbd0, srr1 = 00009030, msr = 57d555f5, hid0 =<br>
> 8000c000<br>> pc = 5f7d75fd, dsisr = 40000000, dar = ffffffff, sdr1 =<br>> 2180001f<br>> ibat0u = 000001ff, ibat0l = 00000001, ibat1u = 20000fff, ibat1l =<br>> 20000002<br>> ibat2u = ff0001ff, ibat2l = ff000022, ibat3u = 00000000, ibat3l =<br>
> 00000000<br>> dbat0u = 00000000, dbat0l = 00000000, dbat1u = 020003ff, dbat1l =<br>> 0200001a<br>><br>><br>><br>><br>><br>><br>><br>><br>> thank you,<br>><br>><br>><br>><br>
><br>> Mike<br>> _______________________________________________ foundry-nsp mailing<br>> list <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> _______________________________________________<br>> foundry-nsp mailing list<br>> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<br></div></div>******************************************************************************<br>Disclaimer:<br><br>This e-mail may contain trade secrets or privileged, undisclosed or<br>otherwise confidential information. If you have received this e-mail<br>
in error, you are hereby notified that any review, copying or<br>distribution of it is strictly prohibited. Please inform us<br>immediately and destroy the original transmittal. Thank you for your<br>cooperation.<br><br>******************************************************************************<br>
<br></blockquote></div><br>