[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Arista unqualified SFP
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 team should be able to get this to you :)
From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Ryan, Spencer
Sent: Wednesday, August 17, 2016 3:53 PM
To: Stanislaw; nanog at nanog.org
Subject: Re: Arista unqualified SFP
Yes, email support and ask for the unlock code, they will make you agree that 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 0000000000 (hex key)
Spencer Ryan | Senior Systems Administrator | sryan at arbor.net<mailto:sryan at arbor.net>
+1.734.794.5033 (d) | +1.734.846.2053 (m)
From: NANOG <nanog-bounces at nanog.org> on behalf of Stanislaw <me at nek0.net>
Sent: Wednesday, August 17, 2016 3:50:12 PM
To: nanog at nanog.org
Subject: Arista unqualified SFP
Is there a way for unlocking off-brand transceivers usage on Arista switches?
I've got an Arista 7050QX switch with 4.14 EOS version. Then it has been found out that Arista switches seem to not have possibility to unlock off-brand xcievers usage (by some service command or so).
I've patched /usr/lib/python2.7/site-packages/XcvrAgent.py, made the checking function bypass the actual check and it helped: ports are not in errdisable state anymore. But despite of xceivers are detected correctly, links aren't coming up (they are in notconnect state).
If anyone possibly have does have a sacred knowledge of bringing off-branded transceivers to life on Arista switches, your help'd be very appreciated. Thanks.