Third-Party Optics with IOS XE 17.12.04

[kurt_faeh]

Hello,

We are using Cisco Switch modells C9200, C9300 and C9500 and planing to move to the IOS XE Version 17.12.04. In the Release notes for the Version 17.12.04 I found the following remark.

Software Features in Cisco IOS XE Dublin 17.12.4

 Feature NameDescription

Enabling Third-Party Optics During AutoInstall

During AutoInstall, the system will detect, third-party optics automatically. Unlike the default boot up process, the third-party optics will not move to err-disabled state during AutoInstall. In the default boot up process, you need to configure the service unsupported-transceiver command to detect the third party optics after system boot. When AutoInstall is successful, the third-party optics are enabled. In all other cases, these optics will be in the err-disabled state. The service unsupported transceiver command is not saved into the startup configuration, and when the configuration is saved using the write memory command, and the system is reloaded, the third-party optics will move into the err-disabled state. This feature is enabled by default. You can use the no service unsupported-transceiver command to disable the third-party optics, after the auto install is complete.

I have done tests with Third-Party Optics and I could not see the problem yet. But if that happens to my colleagues from the project department they will kill me.
Is there really a chance that we have to activate Third-Party Optics after every Switch reboot or is that only a missunderstanding on my side?

All the best    kurt

[balaji.bandi]

That command is global level once you run the command and save it.

Not all of them works, but if your SFP working, then you can install and use it no harm, but when you have issue Open a TAC case, Cisco TAC may not support that SFP and they may ask you to change to cisco to fix the issue.

[marce1000]

  - To me it seems that these notes  are related to the initial installation process, once the switch has a production
     configuration you should be able to use and save the      service unsupported transceiver command to. So the device
     can execute it during  the next reboot.

    M.

[Leo Laohoo]

We are upgrading all our switches to 17.12.4 and we use 3rd party optics. 

We have not seen any issues to those that have already moved to 17.12.4.

[kurt_faeh]

Hello everyone
thanks for the reply.
I checked the 3rd party optics I could get my hands on and no problem so far. In addition I executed the cli command "no service unsupported-transceiver" and nothing happend. I will pass on the information to my colleagues and tell them to check if there is an issue if they using 3rd party optics.

I reckon that is all I can do. Thanks for your support and have a nice day    kurt

[Glitch66]

We DO have this problem, with C9500X's on 17.12.4 (and 17.12.5).  Every time we boot up all our 3rd party SFPs go into err-disabled mode until we MANUALLY RESEAT EACH ONE (arrgggg).  It's killing us.  We've had a TAC case open for over a week but nothing's worked yet.

[Leo Laohoo]

---

@Glitch66 wrote:
We've had a TAC case open for over a week but nothing's worked yet.

---

Unless this network happens to be a very big "whale", TAC is not going to lift a finger investigating 3rd party optics.  

I am, however, curious as to the brand of the optics used.  Please post the complete output to the command "sh idprom interface <PORT>".

Talk to FS[.]com.  I think the ID prom of the existing optics may have been coded differently and FS[.]com would be able to send  different ones that would help.