[c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E

[Jeffrey G. Fitzwater]

In 6.1.3 I never had to add the command;  but now with 6.2.2a I have to.

Are we having fun yet..




Jeff

On Nov 19, 2013, at 3:46 PM, James Slepicka (c-nsp) <cisco-nsp at slepicka.net> wrote:

> Just talked to my SE.  He reports that, in previous versions, some 3rd party transceivers (mine included, apparently) work without "service unsupported-transceiver".  This was 'fixed' in 6.2(2)...
> 
> Thanks for reporting this, Jeff.  We'll be upgrading soon and this saved me from a big headache.
> 
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jeffrey G. Fitzwater
> Sent: Tuesday, November 19, 2013 2:33 PM
> To: Tim Durack
> Cc: Gert Doering; Christina Klam; <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
> 
> My error.   Yes it does exist.  Not sure what I did wrong.
> 
> i am going back and try new code with command.
> 
> 
> Thanks
> 
> Jeff
> On Nov 19, 2013, at 3:10 PM, Tim Durack <tdurack at gmail.com<mailto:tdurack at gmail.com>> wrote:
> 
> "service unsupported-transceiver" works for us on 6.2.2a.
> 
> 
> On Tue, Nov 19, 2013 at 2:49 PM, Jeffrey G. Fitzwater <jfitz at princeton.edu<mailto:jfitz at princeton.edu>> wrote:
> I don't see the  "service unsupported-transceiver" command nor does it run (in case its hidden).     That would imply its not there on 7k 6.1.3 or 6.2.2a.
> 
> 
> Can you imagine us doing an upgrade on one of our core 7k and having all the transceivers fail.
> 
> Jeff
> 
> On Nov 19, 2013, at 12:25 PM, Gert Doering <gert at greenie.muc.de<mailto:gert at greenie.muc.de>> wrote:
> 
>> Hi,
>> 
>> On Tue, Nov 19, 2013 at 03:59:06PM +0000, Nick Hilliard wrote:
>>> I would love to condemn the product managers who make this sort of 
>>> rage-inducing decision to an eternity of dealing with 02:00 
>>> maintenance windows where you're stuck in a data centre with severe 
>>> time constraints, the network is down because of transceiver issues 
>>> and you only have the wrong brand of transceiver to hand, and there's 
>>> no reason it shouldn't work other than vendor politics.  <RAGE/>
>> 
>> Amen.
>> 
>> (The "service unsupported-transceiver" thing used to be a reasonable 
>> compromise.  It gave customers the freedom of choice, while making it 
>> clear that TAC could refuse to support issues with 3rd party transceivers.
>> Sorry to hear that the Nexus BU is now competing with the Stupid BU 
>> for the "most annoying BU CY2013" title...)
>> 
>> gert
>> --
>> USENET is *not* the non-clickable part of WWW!
>>                                                          //www.muc.de/~gert/<http://www.muc.de/~gert/>
>> Gert Doering - Munich, Germany                             gert at greenie.muc.de<mailto:gert at greenie.muc.de>
>> fax: +49-89-35655025<tel:%2B49-89-35655025>                        gert at net.informatik.tu-muenchen.de<mailto:gert at net.informatik.tu-muenchen.de>
>> _______________________________________________
>> cisco-nsp mailing list  
>> cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 
> 
> --
> Tim:>
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/