[191108] in North American Network Operators' Group
Re: Arista unqualified SFP
daemon@ATHENA.MIT.EDU (Youssef Bengelloun-Zahr)
Thu Aug 18 13:40:06 2016
X-Original-To: nanog@nanog.org
From: Youssef Bengelloun-Zahr <youssef@720.fr>
In-Reply-To: <239960167-1471519756-cardhu_decombobulator_blackberry.rim.net-2145176334-@b16.c1.bise6.blackberry>
Date: Thu, 18 Aug 2016 13:41:07 +0200
To: dovid@telecurve.com
Cc: NANOG <nanog-bounces@nanog.org>, nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Hello all,
At my actual job, some colleagues bought Arista switchs very recently. They a=
sked the question about 3rd party transceivers and their SE told them exactl=
y what has been said before :
"we do accept 3rd party transceivers but we don't support them. If you still=
want to use them willingly, you'll have to sign a discharge paper and we'll=
provide you with a key to activate on your equipement".
That's Arista's official policy regarding 3rd party transceivers.
HTH.
BR.
> Le 18 ao=C3=BBt 2016 =C3=A0 13:29, Dovid Bender <dovid@telecurve.com> a =C3=
=A9crit :
>=20
> And I was about to jump on to the Arista train.....
>=20
> Regards,
>=20
> Dovid
>=20
> -----Original Message-----
> From: Stanislaw <me@nek0.net>
> Sender: "NANOG" <nanog-bounces@nanog.org>Date: Thu, 18 Aug 2016 13:24:05=20=
> To: nanog list<nanog@nanog.org>
> Subject: Re: Arista unqualified SFP
>=20
> Hi all,
> If somebody is following my epic adventure of getting uqualified SFP to=20=
> work on Aristas, here is the unhappy end of it.
>=20
> I've written to Arista support and got the following dialogue:
> Support guy:
> Hi,
> Thank you for contacting Arista Support. My name is **** and I'll be=20
> assisting you on this case.
> Could you please provide the "show version" output from this switch?
>=20
> Me:
> Hi,
> Here it is:
> <show version output here>
>=20
> Support guy:
> Hi,
> Thank you for the information.
> Unfortunately, we are unable to activate your 3rd party components. To=20
> ensure ongoing quality, Arista devices are designed to support only=20
> properly qualified transceivers.
> Please let me know if you have any other questions.
>=20
> Me:
> I do not understand,
> But there is a command which allows using non-Arista transceivers. Why=20
> have you implemented it but don't provide an access key to your=20
> customers when they ask for it?
> If it is required to sign some papers which declare that I am aware of=20
> all the risks and losing my warranty - I agree with that, lets do it.=20
> Any way what are the conditions to receive that access key?
>=20
> Support guy:
> I'm afraid that there is nothing I'm able to do regarding this=20
> situation. If you have any other questions regarding enabling 3rd party=20=
> options in Arista switches, I suggest to contact your local account team=20=
> (or sales) for further discussion on this matter.
>=20
>=20
> Next, i've tried inserting various QSFP+ DAC cables I have - none of=20
> them has been even detected on the switch, it was acting like nothing=20
> has been inserted. I guess that even if I get the key, most of my=20
> transceivers/DAC (which work like a champ in Juniper or Extreme=20
> switches) cables wouldnt work.
>=20
> I'm writing this post to make somebody who considers buying their=20
> switches be aware of what they'd get. Just buy Juniper instead.
>=20
>=20
> Stanislaw wrote at 2016-08-17 23:25:
>> Hi Tim,
>>=20
>> Thanks for your expressive answer. Will try it :)
>>=20
>> Tim Jackson =D0=BF=D0=B8=D1=81=D0=B0=D0=BB 2016-08-17 22:57:
>>=20
>>> I'd suggest bitching and moaning at your account team & support until=20=
>>> they give you the key to unlock them..
>>>=20
>>> --
>>> Tim
>>>=20
>>>> On Wed, Aug 17, 2016 at 2:50 PM, Stanislaw <me@nek0.net> wrote:
>>>>=20
>>>> Hi all,
>>>> Is there a way for unlocking off-brand transceivers usage on Arista=20
>>>> switches?
>>>>=20
>>>> I've got an Arista 7050QX switch with 4.14 EOS version. Then it has=20
>>>> been found out that Arista switches seem to not have possibility to=20
>>>> unlock off-brand xcievers usage (by some service command or so).
>>>>=20
>>>> I've patched /usr/lib/python2.7/site-packages/XcvrAgent.py, made the=20=
>>>> checking function bypass the actual check and it helped: ports are=20
>>>> not in errdisable state anymore. But despite of xceivers are detected=20=
>>>> correctly, links aren't coming up (they are in notconnect state).
>>>>=20
>>>> If anyone possibly have does have a sacred knowledge of bringing=20
>>>> off-branded transceivers to life on Arista switches, your help'd be=20
>>>> very appreciated. Thanks.
