Networking: Interface down — SFP transceiver Loss of Signal / no receive light
A fibre or SFP link is down because the transceiver receives no light.
SFP link downLoss of Signal LOSRx power -40 dBmInterface down: no light%PM-4-ERR_DISABLE: Unsupported SFP Meaning
Clean and reseat both SFPs, check the fibre polarity (TX goes to RX), confirm both ends use the same wavelength and fibre type (SR vs LR, multimode vs single-mode) and read the optical power with show interfaces transceiver or ethtool -m. Replace a failed transceiver or damaged patch cable.
Common causes
- Dirty or damaged fibre connector
- TX/RX polarity swapped
- Mismatched SFP type, wavelength or fibre (SR on single-mode)
- Failed or unsupported transceiver (vendor lock)
- Fibre cut or too much attenuation
⚡ Quick fix
- Clean connectors and reseat the SFPs
- Swap TX/RX at one end
- Read optical power:
ethtool -m eth1orshow interfaces transceiver
Detailed fix by platform
Linux
sudo ethtool -m eth1 | grep -iE "rx power|tx power|laser"
How to diagnose
- Rx power — Within range?
- Polarity — TX to RX?
- SFP types — Matching?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- arp -a shows (incomplete) Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
- Duplex mismatch: late collisions / CRC errors Networking: Duplex mismatch — late collisions, runts and CRC errors on the switch port
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
- Idle connections silently dropped by firewall/NAT Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026