[191089] in North American Network Operators' Group
RE: Arista unqualified SFP
daemon@ATHENA.MIT.EDU (Ryan DiRocco)
Thu Aug 18 03:15:06 2016
X-Original-To: nanog@nanog.org
From: Ryan DiRocco <ryan.dirocco@totalserversolutions.com>
To: "Ryan, Spencer" <sryan@arbor.net>, Stanislaw <me@nek0.net>,
"nanog@nanog.org" <nanog@nanog.org>
Date: Wed, 17 Aug 2016 20:33:12 +0000
In-Reply-To: <DM2PR0101MB121636A44982656A4B887E83B0140@DM2PR0101MB1216.prod.exchangelabs.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Exactly this, get your unlock key that is tied to your company and you are =
off to the races, bake it into your standard config. Your SE or support te=
am should be able to get this to you :)
-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Ryan, Spencer
Sent: Wednesday, August 17, 2016 3:53 PM
To: Stanislaw; nanog@nanog.org
Subject: Re: Arista unqualified SFP
Yes, email support and ask for the unlock code, they will make you agree th=
at you know that 3rd party optics may explode the switch and it's not their=
fault.
The command they give you will have a key/hash built into it (but will work=
on any switch) that ties the "unlock" to your org.
Ours looks like this:
service unsupported-transceiver DescriptionOfKeyFromAristaGoesHere 00000000=
00 (hex key)
Spencer Ryan | Senior Systems Administrator | sryan@arbor.net<mailto:sryan@=
arbor.net>
Arbor Networks
+1.734.794.5033 (d) | +1.734.846.2053 (m)
www.arbornetworks.com<http://www.arbornetworks.com/>
________________________________
From: NANOG <nanog-bounces@nanog.org> on behalf of Stanislaw <me@nek0.net>
Sent: Wednesday, August 17, 2016 3:50:12 PM
To: nanog@nanog.org
Subject: Arista unqualified SFP
Hi all,
Is there a way for unlocking off-brand transceivers usage on Arista switche=
s?
I've got an Arista 7050QX switch with 4.14 EOS version. Then it has been fo=
und out that Arista switches seem to not have possibility to unlock off-bra=
nd xcievers usage (by some service command or so).
I've patched /usr/lib/python2.7/site-packages/XcvrAgent.py, made the checki=
ng function bypass the actual check and it helped: ports are not in errdisa=
ble state anymore. But despite of xceivers are detected correctly, links ar=
en't coming up (they are in notconnect state).
If anyone possibly have does have a sacred knowledge of bringing off-brande=
d transceivers to life on Arista switches, your help'd be very appreciated.=
Thanks.
