Cisco 9300 won't recognize sfps after reboot

[kevinfowler]

So I installed a 48 port cisco 9300 and all the sfps that we inserted into the slots were recognized.    I had to reboot the switch and now ports 33-48 don't recognize any SFPs we place in the slots.  Any suggestions?

[eniola2010]

I am having a similar problem, we just bought a C9300-48U switch running IOS-XE 17.06.03, it has an C9300-NM-4G network module. We inserted a GLC-LH-SMD SFP and the port does not recognize the SFPs. Have you been able to resolve the issue, or do we continue to upgrade to higher IOS-XE until we hit the jackpot that do not have this bug.

Please let me know, thanks.

[kevinfowler]

I found that I had bad SFP that would be recognized initially but after a reboot would not be recognizable as well as disable all of the other SFP's that were good.    I didtake the advice and upgrade to 17.3.6 and so far so good.   

[hemmerling]

We are having the same issue with a new batch of 9300L switches, Cisco SFPs that have been rock solid in 3650's running 16.x for years, now when we reboot the switches, they come back up with the ports in down/down state, shut no/shut will sometimes bring the link up, but sometimes we need to do the attached switch directly. They do this on both 17.3.6 and 17.6.5.
Funny part is it's mostly the Cisco SFPs that are doing it.

NAME: "Gi1/1/1", DESCR: "10/100/1000BaseTX SFP"
PID: GLC-T , VID: , SN: 00000MTCxxx

NAME: "Gi1/1/2", DESCR: "1000BaseSX SFP"
PID: GLC-SX-MMD , VID: V01 , SN: AGV190xxxxx (GLC-SX-MMD++=)

NAME: "Gi1/1/3", DESCR: "1000BaseLX SFP"
PID: GLC-LH-SM , VID: V01 , SN: TCLXAxxxxxx

NAME: "Gi1/1/4", DESCR: "1000BaseLX SFP"
PID: GLC-LH-SMD , VID: V02 , SN: OPG262xxxxx (GLC-LH-SMD++=)

I have older 9300s and 9300Ls that are working fine and have been, it's only the newer ones and only on devices 6 hours away.
Any ideas?

[eniola2010]

Hi hemmerling,

We had a similar problem some months back with C9300-48U model. The switch came preloaded with IOS-XE 17.06.03 and it was not recognizing Cisco SFPs. We had to upgrade the code to 17.06.05 to resolve the issue, I would suggest you upgrade to the next higher stable release of IOS-XE code available for the switch. Let us know how it goes and all the best.