[j-nsp] QFX3500 optics lock?
OBrien, Will
ObrienH at missouri.edu
Sat Jan 7 20:48:40 EST 2012
I'd make darn sure that Juniper knows that this is an issue for you.
I'm half torn on the optics issue - I can half understand the argument for certified optics, but I've also been in the position of being short on 'blessed' optics while having other vendors hardware on hand.
With a sfp+ to sfp+ cable, there isn't an excuse for this - It's all copper and it's a friggin network port. Eesh.
That said, even cisco does this with the unsupported optics command.
On Jan 7, 2012, at 2:58 PM, Brandon Ross wrote:
> On Sat, 7 Jan 2012, Phil Mayers wrote:
>
>> The device must support generic / unbranded transceivers. Any device which prevents use of, or restricts features based on transceiver vendor will be immediately disqualified.
>
> I'm very glad to see people doing this in their procurement. I'm also happy to see that a majority of the RFPs that I see, mostly BTOP ones, also include some sort of requirement for support of 3rd party optics.
>
> Preventing 3rd party optics from working in the QFX immediately disqualifies it from a majority of the new network builds I see and I would never recommend a product to my customers that won't work with 3rd party optics.
>
> --
> Brandon Ross AIM: BrandonNRoss
> +1-404-635-6667 ICQ: 2269442
> Skype: brandonross Yahoo: BrandonNRoss
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list