Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
On 19/11/13 22:51, Tim Durack wrote: Second that. The more people buy 3rd party (coded if you want) the better. Vendors only listen to sales. In fact I would go further. Mandate that the device interoperate with 3rd party optics in your procurement, and have the suppler sign a contact. Enforce that contract. Don't buy from vendors who won't do it. This is what we do (and in fact, did in our N7k procurement!) For current gen equipment which is still locked, start buying transceivers from vendors who blow CISCO into the EEPROM, and tell your account manager you'll be doing it, and that you won't buy one more transceiver from them. Optics locking is outright anti-competitive behaviour, and I wish one of the various regulators would step on it, hard. Unless and until that happens, we need to discourage it. Anyone who surrenders and buys the vendor optics is doing themselves and everyone else a huge disservice. Fight it, hard, or we'll still be having the conversation 10 years from now! Regards, Phil ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
On 11/19/2013 11:57 PM, Jared Mauch wrote: +1 to that. We recently ran across some 3rd-party CODED DOM-supporting optics that have worked (thus far) in both Ciscos and Brocades. When you can issue a show int trans and get results from 3rd-parties while Ciscos remain silent, it speaks volumes :) Exactly, We use a local vendor and have a guy there who can code just about anything into the firmware for us so we never have problems with unsupported transceivers and the show int trans or sh controller pops out plethora of useful information, we use XFP, SFP+ and SFP in different platforms no with issues whatsoever. And the prices are just incomparable to Cisco prices. adam ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Things will get worse if they start to solder crytoprocs with mask-programmed vendor-signed certificates into the gbic/sfp/.. instead of the serial eeprom. Also the real-time clock helps to limit the lifetime of devices to just a little longer than warrenty time. show transceiver lifetime remaining show transceiver certificate path (for those on h3c-omware: display transceiver ...) Just my 0.01 $, Juergen. On 11/19/2013 11:57 PM, Jared Mauch wrote: +1 to that. We recently ran across some 3rd-party CODED DOM- supporting optics that have worked (thus far) in both Ciscos and Brocades. When you can issue a show int trans and get results from 3rd-parties while Ciscos remain silent, it speaks volumes :) Exactly, We use a local vendor and have a guy there who can code just about anything into the firmware for us so we never have problems with unsupported transceivers and the show int trans or sh controller pops out plethora of useful information, we use XFP, SFP+ and SFP in different platforms no with issues whatsoever. And the prices are just incomparable to Cisco prices. adam ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Jeff, We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. As it has been awhile since we ran 6.1 so I do not know if the issue began with 6.2 or not. I do not know if this helps. But, I feel better after venting. :-) -- Christina Klam Network Engineer Institute for Advanced Study Email: ck...@ias.edu Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
On 19/11/2013 13:54, Christina Klam wrote: We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. Can't say I'm surprised. If Cisco is going to do stupid customer-hating stuff like locking transceivers, they ought to expect to shoot themselves in the foot from time to time. Pity that it's the customers who end taking the bullet though. 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/ Nick ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgpCJCKuNK0qX.pgp Description: PGP signature ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Christina, are you running on sup-2E ? We are running many non-CISCO transceivers on nexus 7k running 6.1.3 but when I did the upgrade to 6.2.2a NO GOOD. We also ran across issue with 6.2.2a on sup-2E that you cannot overwrite slot0: file. Delete but no overwrite. TAC case open. Jeff On Nov 19, 2013, at 8:54 AM, Christina Klam ck...@ias.edu wrote: Jeff, We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. As it has been awhile since we ran 6.1 so I do not know if the issue began with 6.2 or not. I do not know if this helps. But, I feel better after venting. :-) -- Christina Klam Network Engineer Institute for Advanced Study Email: ck...@ias.edu Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ___ cisco-nsp mailing list cisco-nsp@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
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 g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Jeff, They are plain ole N7K-SUP2 with N7K-M224XP-23L line cards. I just accepted the fact that we will have to pay the Cisco tax. Regards, Christina On 11/19/2013 02:45 PM, Jeffrey G. Fitzwater wrote: Christina, are you running on sup-2E ? We are running many non-CISCO transceivers on nexus 7k running 6.1.3 but when I did the upgrade to 6.2.2a NO GOOD. We also ran across issue with 6.2.2a on sup-2E that you cannot overwrite slot0: file. Delete but no overwrite. TAC case open. Jeff On Nov 19, 2013, at 8:54 AM, Christina Klam ck...@ias.edu wrote: Jeff, We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. As it has been awhile since we ran 6.1 so I do not know if the issue began with 6.2 or not. I do not know if this helps. But, I feel better after venting. :-) -- Christina Klam Network Engineer Institute for Advanced Study Email: ck...@ias.edu Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- Christina Klam Network Engineer Institute for Advanced Study Email: ck...@ias.edu Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Did you happen to try to overwrite a slot0:file , even though this is unrelated to the transceiver issue. In my case its just another bug with 6.2.2a on sup-2E. Jeff On Nov 19, 2013, at 2:59 PM, Christina Klam ck...@ias.edu wrote: Jeff, They are plain ole N7K-SUP2 with N7K-M224XP-23L line cards. I just accepted the fact that we will have to pay the Cisco tax. Regards, Christina On 11/19/2013 02:45 PM, Jeffrey G. Fitzwater wrote: Christina, are you running on sup-2E ? We are running many non-CISCO transceivers on nexus 7k running 6.1.3 but when I did the upgrade to 6.2.2a NO GOOD. We also ran across issue with 6.2.2a on sup-2E that you cannot overwrite slot0: file. Delete but no overwrite. TAC case open. Jeff On Nov 19, 2013, at 8:54 AM, Christina Klam ck...@ias.edu wrote: Jeff, We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. As it has been awhile since we ran 6.1 so I do not know if the issue began with 6.2 or not. I do not know if this helps. But, I feel better after venting. :-) -- Christina Klam Network Engineer Institute for Advanced Study Email: ck...@ias.edu Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- Christina Klam Network Engineer Institute for Advanced Study Email: ck...@ias.edu Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
service unsupported-transceiver works for us on 6.2.2a. On Tue, Nov 19, 2013 at 2:49 PM, Jeffrey G. Fitzwater jf...@princeton.eduwrote: 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 g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
What sup and what EPLD ver. Interesting ! Jeff On Nov 19, 2013, at 3:10 PM, Tim Durack tdur...@gmail.commailto:tdur...@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 jf...@princeton.edumailto:jf...@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 g...@greenie.muc.demailto:g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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 g...@greenie.muc.demailto:g...@greenie.muc.de fax: +49-89-35655025tel:%2B49-89-35655025 g...@net.informatik.tu-muenchen.demailto:g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.netmailto:cisco-nsp@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@puck.nether.netmailto:cisco-nsp@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
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 tdur...@gmail.commailto:tdur...@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 jf...@princeton.edumailto:jf...@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 g...@greenie.muc.demailto:g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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 g...@greenie.muc.demailto:g...@greenie.muc.de fax: +49-89-35655025tel:%2B49-89-35655025 g...@net.informatik.tu-muenchen.demailto:g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.netmailto:cisco-nsp@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@puck.nether.netmailto:cisco-nsp@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
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-boun...@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@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 tdur...@gmail.commailto:tdur...@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 jf...@princeton.edumailto:jf...@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 g...@greenie.muc.demailto:g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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 g...@greenie.muc.demailto:g...@greenie.muc.de fax: +49-89-35655025tel:%2B49-89-35655025 g...@net.informatik.tu-muenchen.demailto:g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.netmailto:cisco-nsp@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@puck.nether.netmailto:cisco-nsp@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
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-...@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-boun...@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@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 tdur...@gmail.commailto:tdur...@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 jf...@princeton.edumailto:jf...@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 g...@greenie.muc.demailto:g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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 g...@greenie.muc.demailto:g...@greenie.muc.de fax: +49-89-35655025tel:%2B49-89-35655025 g...@net.informatik.tu-muenchen.demailto:g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.netmailto:cisco-nsp@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@puck.nether.netmailto:cisco-nsp@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Does the command exist in 6.1(3)? I don't have a box that I can test with. -Original Message- From: Jeffrey G. Fitzwater [mailto:jf...@princeton.edu] Sent: Tuesday, November 19, 2013 3:19 PM To: James Slepicka (c-nsp) Cc: Jeffrey G. Fitzwater; Tim Durack; Gert Doering; Christina Klam; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E 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-...@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-boun...@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@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 tdur...@gmail.commailto:tdur...@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 jf...@princeton.edumailto:jf...@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 g...@greenie.muc.demailto:g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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 g...@greenie.muc.demailto:g...@greenie.muc.de fax: +49-89-35655025tel:%2B49-89-35655025 g...@net.informatik.tu-muenchen.demailto:g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.netmailto:cisco-nsp@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@puck.nether.netmailto:cisco-nsp@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
It does accept the command in 6.1.3, but non CISCO transceivers still work without running it, and its NOT in the config even with the command “show run all” if I run the command “no service unsupported-transceiver” and do an interface SHUT NO SHUT the non CISCO still work. Hmmm…. So CISCO must have changed something in 6.2.2a to require the command for non CISCO transceivers. This makes me a little nervous running 6.2.2a with this caveat. Sure I can save it in config, but what happens in next release. I’ll discuss this with my SE and see what they say. Jeff On Nov 19, 2013, at 4:24 PM, James Slepicka (c-nsp) cisco-...@slepicka.net wrote: Does the command exist in 6.1(3)? I don't have a box that I can test with. -Original Message- From: Jeffrey G. Fitzwater [mailto:jf...@princeton.edu] Sent: Tuesday, November 19, 2013 3:19 PM To: James Slepicka (c-nsp) Cc: Jeffrey G. Fitzwater; Tim Durack; Gert Doering; Christina Klam; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E 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-...@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-boun...@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@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 tdur...@gmail.commailto:tdur...@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 jf...@princeton.edumailto:jf...@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 g...@greenie.muc.demailto:g...@greenie.muc.de wrote: Hi, On Tue, Nov 19, 2013 at 03:59:06PM +, 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 g...@greenie.muc.demailto:g...@greenie.muc.de fax: +49-89-35655025tel:%2B49-89-35655025 g...@net.informatik.tu-muenchen.demailto:g...@net.informatik.tu-muenchen.de ___ cisco-nsp mailing list cisco-nsp@puck.nether.netmailto:cisco-nsp@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@puck.nether.netmailto:cisco-nsp@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
On Nov 19, 2013, at 10:59 AM, Nick Hilliard n...@foobar.org wrote: On 19/11/2013 13:54, Christina Klam wrote: We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. Can't say I'm surprised. If Cisco is going to do stupid customer-hating stuff like locking transceivers, they ought to expect to shoot themselves in the foot from time to time. Pity that it's the customers who end taking the bullet though. The failure of Cisco to support their own first party optics correctly is a significant problem we have faced. We’ve done many rounds with them on this topic and it’s not gone well for them. The optics folks have been borderline arrogant and ignorant of the software-side problems that exist. My suggestion: Speak with your wallet and discontinue purchasing them. You can save lots of $$$. When you type “show” commands on a device, make sure you map them back to the SFF-8472 MSA fields. If the software platform doesn’t display all of them, insist it’s basic support of the optics and their optics and software are substandard. Regarding Twinax cables. You really shouldn’t need these as the optics are fairly inexpensive via 3rd party, and you can use a fiber cable for “cheap” as well. Look at places like monoprice, champion one, osihardware and many others out there. Most places have better warranty support than Cisco with paid support in my experience. - Jared ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
Second that. The more people buy 3rd party (coded if you want) the better. Vendors only listen to sales. On Tuesday, November 19, 2013, Jared Mauch wrote: On Nov 19, 2013, at 10:59 AM, Nick Hilliard n...@foobar.orgjavascript:; wrote: On 19/11/2013 13:54, Christina Klam wrote: We have been running 6.2(2) since the summer. In the last six months, I had to return some third-party Cisco compatible twinax cables because they were Invalid on our M2s. And, I just had to swap out some official Cisco SFP-10G-LR because they were version 1 which also do not work with our M2 cards. Can't say I'm surprised. If Cisco is going to do stupid customer-hating stuff like locking transceivers, they ought to expect to shoot themselves in the foot from time to time. Pity that it's the customers who end taking the bullet though. The failure of Cisco to support their own first party optics correctly is a significant problem we have faced. We’ve done many rounds with them on this topic and it’s not gone well for them. The optics folks have been borderline arrogant and ignorant of the software-side problems that exist. My suggestion: Speak with your wallet and discontinue purchasing them. You can save lots of $$$. When you type “show” commands on a device, make sure you map them back to the SFF-8472 MSA fields. If the software platform doesn’t display all of them, insist it’s basic support of the optics and their optics and software are substandard. Regarding Twinax cables. You really shouldn’t need these as the optics are fairly inexpensive via 3rd party, and you can use a fiber cable for “cheap” as well. Look at places like monoprice, champion one, osihardware and many others out there. Most places have better warranty support than Cisco with paid support in my experience. - Jared ___ cisco-nsp mailing list cisco-nsp@puck.nether.net javascript:; https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- Tim: ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new, NX-OS 6.2.2a on sup-2E
On 11/19/2013 5:51 PM, Tim Durack wrote: Second that. The more people buy 3rd party (coded if you want) the better. Vendors only listen to sales. +1 to that. We recently ran across some 3rd-party CODED DOM-supporting optics that have worked (thus far) in both Ciscos and Brocades. When you can issue a show int trans and get results from 3rd-parties while Ciscos remain silent, it speaks volumes :) We still keep branded spares for any surprise issues. But I don't think we would have enough to survive a software upgrade enforced transceiver refusal such as the one being discussed... so I remain skeptical, and disgruntled over the whole branded issue. Could you imagine if you could stick a vendor PROM in an ethernet cable? We don't tolerate such silliness with any other interfaces... Jeff ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Third party transceivers that fail only with new NX-OS 6.2.2a on sup-2E
Since CISCO TECH will probably not touch this because its not CISCO, I see if anybody has solution. We are running nx-os 6.1.3 on 7k with sup-2E on a new chassis that will go into production soon. We wanted to run the 6.2.2a to fix some other issues with logging and found out the channel ports failed to come up due to transceiver Invalid. ——- ( Eth1/1 core-ns ch xcvrInval trunk autoauto 10Gbase-LR) ——- Backing out to 6.1.3 and all comes back to life. Has anybody else sent his issue with third party transceivers? I’ll probably open a TAC case just to see what they say anyway. Thanks for any help. Jeff Fitzwater OIT Network System Princeton University ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Third party transceivers that fail only with new NX-OS 6.2.2a on sup-2E
On Mon, 18 Nov 2013, Jeffrey G. Fitzwater wrote: Since CISCO TECH will probably not touch this because its not CISCO, I see if anybody has solution. Backing out to 6.1.3 and all comes back to life. Has anybody else sent his issue with third party transceivers? I don't know if Cisco's stance on running third-party optics changed between NX-OS 6.1 and 6.2, but that's certainly possible. I'm running NX-OS 6.2.2 in production on a few of our 7Ks, but we don't have any non-Cisco optics to test with. jms ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
