[j-nsp] Juniper dead J series?
Clay Haynes
chaynes at centracomm.net
Fri Aug 2 00:15:11 EDT 2013
On 8/1/13 8:22 PM, "James Baker" <james at jgbaker.co.nz> wrote:
>+1
>
>Occurred with a SSG520; exact same problems
>
>RMA was the only solution (Fun at 3am Monday Morning)
>
>
>
>>-----Original Message-----
>>From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf
>>Of Adam Leff
>>Sent: Friday, 2 August 2013 8:17 a.m.
>>To: David Gee
>>Cc: juniper-nsp at puck.nether.net
>>Subject: Re: [j-nsp] Juniper dead J series?
>>
>>David-
>>
>>I've experienced this about 7 times in the past two years, all on
>>J-series
>>routers purchased in the 2008-2009 time period... whether it was a
>>clean/coordinating power-off or if it was an unexpected power loss / UPS
>>run-
>>out.
>>
>>JTAC originally thought it was a memory issue, as there is a PSN about a
>>known
>>memory problem on a particular batch of J-series routers. However, I've
>>still
>>had boxes with replaced memory die as you have described.
>> Current indications from JTAC are that it's a CPU/BIOS issue - we don't
>>even
>>get output on the console or anything resembling POST during boot.
>> Our latest failure has been sent to Juniper's manufacturing partner for
>>further
>>analysis.
>>
>>The only solution for us so far is to keep RMA'ing the dead boxes. Very
>>frustrating, indeed.
>>
>>~Adam
>>
>>
>>
>>On Thu, Aug 1, 2013 at 1:19 PM, David Gee <dave at infiltr8.com> wrote:
>>
>>> Hi all,
>>>
>>>
>>>
>>> Second post from me in the same month! Scary.
>>>
>>>
>>>
>>> So, long story short. Router went offline after a power outage. Didn't
>>> come back. Remote hands consoled in and reported back:
>>>
>>>
>>>
>>> "All four LED's are on permanently. We've unplugged, plugged it back
>>> in, rebooted and rebooted some more. No console output".
>>>
>>>
>>>
>>> I've had a quick look around but can't find anything specific. I'm
>>> thinking at this point it's either, RAM, CPU or possibly compact
>>> flash? The DC is a few miles away, so contemplating jumping on Ebay
>>> and buying some spares to cover as many realistic outcomes as
>>> possible. Any thoughts or experience with this?
>>>
>>>
>>>
>>> Thanks
>>>
>>> David
>>>
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>_______________________________________________
>>juniper-nsp mailing list juniper-nsp at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp
I've had this happen on many (20+) SSG520m and/or SSG550m we deployed at
%DAYJOB%. Every single one would reboot (core-dump, power loss) and never
come back online. Even loading firmware manually wouldn't fix the problem.
Only thing you could do was RMA them.
More information about the juniper-nsp
mailing list