[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

A case against vendor-locking optical modules

Subject: A case against vendor-locking optical modules
From: SNaslund at medline.com (Naslund, Steve)
Date: Tue, 18 Nov 2014 00:39:50 +0000
In-reply-to: <CAK_-TSYwgepHWRRGnGU4bSZHm7222vp55SJpErBronhZT0if1w@mail.gmail.com>
References: <[email protected]> <CAHgd+38_7D_-57D9TMKQMjm1k12wJG4vh_=YwXzh3xbtybsJVw@mail.gmail.com> <9578293AE169674F9A048B2BC9A081B401572055E9@MUNPRDMBXA1.medline.com>, <CAK_-TSYwgepHWRRGnGU4bSZHm7222vp55SJpErBronhZT0if1w@mail.gmail.com>

Our experience using that command has been mixed enough to be unreliable for production.  Problems include error disabled interfaces refusing to come back online and the command not surviving a power cycle.  Use with caution.

Steven Naslund
Chicago IL

> On Nov 17, 2014, at 2:11 PM, "ryanL" <ryan.landry at gmail.com> wrote:
> 
> there's a reason why cisco introduced "service unsupported-transceiver",
> which still remains an undocumented command. i have arista gear as well.
> kinda wish they had a similar undocumented command.

References:
- A case against vendor-locking optical modules
  - From: jerome at ceriz.fr (Jérôme Nicolle)
- A case against vendor-locking optical modules
  - From: svoll.voip at gmail.com (Scott Voll)
- A case against vendor-locking optical modules
  - From: SNaslund at medline.com (Naslund, Steve)
- A case against vendor-locking optical modules
  - From: ryan.landry at gmail.com (ryanL)

Prev by Date: A case against vendor-locking optical modules
Next by Date: DNS Lookup - Filter "localhost"
Previous by thread: A case against vendor-locking optical modules
Next by thread: A case against vendor-locking optical modules
Index(es):
- Date
- Thread