Re: [j-nsp] Sporadic LUCHIP IDMEM read errors

2017-09-27 Thread Michael Hare 
Yes, I see them as well.  I've never bothered contacting jtac, nor have I seen 
a detectable impact from these.

Between production and lab/sparing we have ~50 MX104s and 3 MX2010s.   Below 
data is for 2017.

#occurrences, chassis descr, date

 26 MX104 #10 - 2017-01-06
 12 MX104  #3 - 2017-06-15
  8 MX2010 #3 - 2017-04-23
  8 MX104  #2 - 2017-02-16
  5 MX2010 #1 - 2017-07-07
  4 MX2010 #3 - 2017-04-25
  4 MX104  #6 - 2017-06-13
  2 MX2010 #3 - 2017-05-31
  2 MX2010 #3 - 2017-04-27
  2 MX2010 #2 - 2017-05-01
  2 MX2010 #1 - 2017-08-25
  2 MX104  #9 - 2017-05-12
  2 MX104  #8 - 2017-08-21
  2 MX104  #8 - 2017-07-30
  2 MX104  #7 - 2017-02-05
  2 MX104  #5 - 2017-02-03
  2 MX104  #4 - 2017-04-29
  2 MX104  #1 - 2017-01-29

-Michael

> -Original Message-
> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
> Of Sebastian Wiesinger
> Sent: Tuesday, September 26, 2017 3:15 AM
> To: Juniper NSP 
> Subject: [j-nsp] Sporadic LUCHIP IDMEM read errors
> 
> Hello,
> 
> we're seeing sporadic LUCHIP IDMEM read errors like these (from two
> routers):
> 
> fpc5 LUCHIP(0) IDMEM[112821] read error
> 
> tfeb0 LUCHIP(0) IDMEM[303084] read error
> 
> It is a single error and does not impact traffic in any measurable way
> for us. It appears to be random on different router models (MX960,
> MX480, MX80) and JunOS versions. It seems these have increased in the
> last few weeks. At least one other provider I asked is seeing them as
> well.
> 
> Is anyone here seeing these? Has anyone found a reason for it or has
> already a case open for this?
> 
> Best Regards
> 
> Sebastian
> 
> --
> GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0
> B9CE)
> 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE
> SCYTHE.
> -- Terry Pratchett, The Fifth Elephant
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Sporadic LUCHIP IDMEM read errors

2017-09-26 Thread Sebastian Wiesinger 
* Olivier Benghozi  [2017-09-26 12:42]:
> Maybe 
> http://news.nationalgeographic.com/2017/09/sun-solar-flare-strongest-auroras-space-science/
>  
> 
>  ?

I was actually thinking something like that, but I'm not sure how
realistic that is. I know that Cisco has some errors that plainly
state that they can be caused by "cosmic rays". :)

Regards

Sebastina

-- 
GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0 B9CE)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.
-- Terry Pratchett, The Fifth Elephant
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Sporadic LUCHIP IDMEM read errors

2017-09-26 Thread Olivier Benghozi 
Maybe 
http://news.nationalgeographic.com/2017/09/sun-solar-flare-strongest-auroras-space-science/
 

 ?

> On 26 sept. 2017 at 09:14, Sebastian Wiesinger  wrote :
> 
> Hello,
> 
> we're seeing sporadic LUCHIP IDMEM read errors like these (from two
> routers):
> 
> fpc5 LUCHIP(0) IDMEM[112821] read error
> 
> tfeb0 LUCHIP(0) IDMEM[303084] read error
> 
> It is a single error and does not impact traffic in any measurable way
> for us. It appears to be random on different router models (MX960,
> MX480, MX80) and JunOS versions. It seems these have increased in the
> last few weeks. At least one other provider I asked is seeing them as
> well.
> 
> Is anyone here seeing these? Has anyone found a reason for it or has
> already a case open for this?
> 
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] Sporadic LUCHIP IDMEM read errors

2017-09-26 Thread Sebastian Wiesinger 
Hello,

we're seeing sporadic LUCHIP IDMEM read errors like these (from two
routers):

fpc5 LUCHIP(0) IDMEM[112821] read error

tfeb0 LUCHIP(0) IDMEM[303084] read error

It is a single error and does not impact traffic in any measurable way
for us. It appears to be random on different router models (MX960,
MX480, MX80) and JunOS versions. It seems these have increased in the
last few weeks. At least one other provider I asked is seeing them as
well.

Is anyone here seeing these? Has anyone found a reason for it or has
already a case open for this?

Best Regards

Sebastian

-- 
GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0 B9CE)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.
-- Terry Pratchett, The Fifth Elephant
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp