Monday, January 20, 2020

Getting a Cisco Nexus 9236c to work with third-party optics

Hello! I am working on a new lab setup and I'm running into what seems like an unusual problem. My external connectivity is via a 10G single-mode LR fiber link. I need to plug this into my Nexus 9236c switch. The switch only has QSFP+ ports, so I got this QSA adapter and a Finisar 10G SFP+ optic I had lying around, both of which are specifically advertised as being compatible with Cisco. I was expecting to have to jiggle the handle a bit to get everything working but I have run into a roadblock I can't get past after a few days of fooling with it.

I am quite certain that this is a Cisco/third-party compatibility problem because I have a 1G Cisco SFP optic here too. The switch recognizes that optic as soon as I plug it into the QSA adapter, and everything plays nice.

When I connect the Finisar 10G SFP+ optic, the Nexus 9236c turns off the interface and gives me the following error:

2020 Jan 20 19:05:50 SBE_Lab %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/1, hardware type changed to 10G 2020 Jan 20 19:05:50 SBE_Lab %ETHPORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface Ethernet1/1 is not supported 

I did some research on the question and found a possible answer:

SBE_Lab(config)# service unsupported-transceiver SBE_Lab(config)# show run | include trans SBE_Lab(config)# show start | include trans SBE_Lab(config)# 

The switch accepts the service unsupported-transceiver command without protest, but as you can see, the configuration does not appear to be applied to anything. Nothing changes with the port's behavior, either:

SBE_Lab(config)# show interface eth1/1 Ethernet1/1 is down (Link not connected) ... 

A coworker witnessed this and suggested that my switch may be haunted. If so, I'm going to have to learn to live with the ghosts, because their dwelling was kinda pricy.

The switch is running NXOS version 7.0(3)I7(4). My support contract isn't in place yet so I can't download NXOS version 7.0(3)I7(7) to update. That doesn't feel like it's the issue, though, because we're only out of date by a year and I can find forum threads discussing the service unsupported-transceiver command going back to four or five years ago.

I think that there is something weird going on here but I will freely admit that I'm new to installing fiber-based networks and configuring Cisco hardware. Has anyone ever dealt with this problem or seen something like it? Any guidance would be very helpful.



No comments:

Post a Comment