[j-nsp] EX4550 and 3rd Party SFP-1GE-LX
Joe Wooller
joe at waia.asn.au
Thu Jun 6 06:40:59 EDT 2013
Thanks for the reply,
This is basically what is happening (i think) the PFE becomes unusable until you reboot. Is there a way to see what ports are on what PFE?
I have spoken to a number of SFP suppliers here and this is exactly what they suspect too. I have a JTAC logged so I will see what they come back with.
My biggest issue with this now is having remote hands work on a site, install a 3rd party optic (by mistake for argument sake) and have a whole PFE crash.
I personally think they should have some way of dealing with that without having to reboot. (Maybe they do, I just don't know what it is).
Cheers
Joe
On 06/06/2013, at 6:29 PM, Saku Ytti <saku at ytti.fi> wrote:
> On (2013-06-06 15:57 +0800), Joe Wooller wrote:
>
> Hey Joe,
>
>> Apr 10 04:44:48 sw01chassism[1298]: Error(2):I2C read of EEPROM failed for Port 14 at offset 0x0
>
>> I would be interested to see if anyone else has encountered this?
>> So far I can not replicate the issue with 3rd party Copper SPF;s or 10Gig SFP+'s.
>
> I have some SFPs which crash Trio PFE because they don't respond to I2C
> queries fast enough and read failure error condition is not handled so the
> whole PFE crashes.
>
> I guess your optics microcontroller isn't up to snuff.
>
> Some might say that even official optic might get HW fault which causes I2C
> read problems and that you always need to handle errors, but those people
> didn't handle my JTAC case.
>
> --
> ++ytti
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> !DSPAM:1,51b0649d67084670529228!
>
>
More information about the juniper-nsp
mailing list