[j-nsp] SFP Compatibility

[Jonas Frey]

I know of a dozen vendors in taiwan/china that will ask you which eeprom
code you want on your SFP if you order there. They do have almost any
code available, be it HP or Cisco or whatever. The SFPs will be
correctly detected by the device and work just like a original. (However
the SFPs do have white labels on them of course).
This apparently is now a standard "service" by most SFP vendors.

Jonas

On Wed, 2008-01-16 at 14:25, Tim Durack wrote:
> I have to wonder if vendors are subsidizing line cards with GBIC/SFP sales.
> Once one vendor does it, everybody else has to follow to stay "competitive."
> 
> Either that or it such a huge cash-cow they wont let it go.
> 
> I guess the compatible design of GBIC/SFPs benefits the vendor not the
> end-user, as the vendor can switch OEM at a moments notice, as long as
> they get the eprom programmed with the magic vendor code (I notice the
> latest "C" rev HP SFPs are mechanically different and shipping out of
> China instead of Malaysia.)
> 
> Tim:>
> 
> On Jan 15, 2008 9:19 PM, David Ball <davidtball at gmail.com> wrote:
> >    I was speaking with someone from Foundry just this afternoon and
> > asked this very question.  They indicated that they had considered
> > doing this some time ago (forcing the use of Foundry SFPs), but first
> > polled some of their customer base for a reaction.  Not surprisingly,
> > it was overwhelmingly negative, so they decided against it.  That is
> > not to say that they won't do it in the future, and I suppose that
> > goes for any vendor.
> >   Sound advice from Kevin, about testing code upgrades with various
> > optics in the lab prior to production deployment to avoid being
> > bitten.
> >
> > David
> >
> >
> >
> > On 15/01/2008, Paul Civati <paul at xciv.org> wrote:
> > > Kevin Day <toasty at dragondata.com> wrote:
> > >
> > > > We escalated this as high as they'd let us. The reply from high up
> > > > was that they were sorry for the inconvenience, but there is no
> > > > workaround, and that it's for our own protection.
> > >
> > > I think this was brought about because they provide a lot of free
> > > lifetime replacement warranty (which is in itself a whole other
> > > story) with their networking products.
> > >
> > > It's very annoying that aside from not supporting non-HP SFPs they
> > > also prevent you from using any other vendor, even as an unsupported
> > > part (it's fairly easy to view the installed transceivers from the
> > > cli to verify what's installed).
> > >
> > > Anyway, getting very off-topic now..
> > >
> > > -Paul-
> > >
> > > _______________________________________________
> > > 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