[j-nsp] SFP Compatibility

[Evan Williams]

I had no issues using other vendors SFP in a NIT environment and concur that 
the only symptom of using a non-Juniper SFP was that the platform recognised 
it was a non--juniper SFP. This was especially useful when we were supplied 
with only LH and we needed to use SH due to the provision of the 'wrong 
mode' fibre. In an ideal world I would have used vendor specific SFP.

As an aside, when working with another vendor I was able to discover a very 
useful 'secret command' that allowed the use of the of SFP in their routers, 
other than those supplied by that vendor.


----- Original Message ----- 
From: "Richard A Steenbergen" <ras at e-gerbil.net>
To: "Eric Van Tol" <eric at atlantech.net>
Cc: <juniper-nsp at puck.nether.net>
Sent: Thursday, January 10, 2008 10:01 PM
Subject: Re: [j-nsp] SFP Compatibility


> On Thu, Jan 10, 2008 at 04:46:13PM -0500, Eric Van Tol wrote:
>> Hi all,
>> Is anyone using Transition Networks' SFPs in their Junipers?  If so,
>> have you had any problems with them?  I'm looking at possibly using the
>> TN-SFP-LX12
>> (http://www.transition.com/TransitionNetworks/Products2/Product.aspx?ID=
>> 26601&CategoryName=tnsfp) and I'd like to know if it works.  I'm not
>> aware of Juniper imposing 'err-disable'-like "features" yet on their
>> SFP-based GE PICs, but you never know.
>
> Much to their credit, Juniper plays no vendor locking games with optics.
>
> The worst you'll get is NON-JNPR instead of a part number in show chassis
> hardware, like so:
>
>    Xcvr 0                NON-JNPR     K6S00Y5           XFP-10G-LR
>
> -- 
> Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>