Showing results for 
Search instead for 
Did you mean: 

Nexus 5000 SFP No-Transceiver issue

I'm looking at an issue on our Nexus 5548, where a 10G dark fiber link was encountering interface errors. After changing SFPs, the switch now logs "hardware type changed to No-Transceiver" for any port we configure and place the interface into. We've tried different trancsievers and cables. The same brand of transceiver has been working fine for many months now previously, and we're not seeing any SFP validation errors. Any pointers welcome.


Config for the port is a simple trunk.


Syslog message:

%ETHPORT-5-IF_HARDWARE: Interface Ethernet1/11, hardware type changed to No-Transceiver


Transceiver details


show interface ethernet 1/11 transceiver details
transceiver is present
type is 10Gbase-LR
name is FS
part number is SFP-10GLR-31
revision is
serial number is G1909069459
nominal bitrate is 10300 MBit/sec
Link length supported for 9/125um fiber is 10 km
cisco id is --
cisco extended id number is 4

show interface ethernet 1/11
Ethernet1/11 is down (Link not connected)
Dedicated Interface

Hardware: 1000/10000 Ethernet, address: 0005.73cc.cc72 (bia 0005.73cc.cc72)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is trunk
auto-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped never
Last clearing of "show interface" counters never
0 interface resets
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
0 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
0 jumbo packets 0 storm suppression bytes
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
0 unicast packets 0 multicast packets 0 broadcast packets
0 output packets 0 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause


System version: 7.3(3)N1(1)









it doesnt seem to be a problem with the fiber, maybe go ahead and try another SFP. If not probably a reboot. check for any changes on the other side too (physical).

Please mark it helpfull if it was the case, and i have this problem too. Double touchdown is amazing. Thanks to make Engineering easy.
Content for Community-Ad