Verifying the operational health of Small Form-Factor Pluggable (SFP) transceivers is a fundamental task when provisioning fiber links or diagnosing physical-layer connectivity on Cisco switches. Whether you are confirming that a newly inserted module is recognized by the chassis, measuring real-time optical power levels, or resolving port shutdown errors, Cisco provides a comprehensive set of command-line tools and hardware indicators to inspect every layer of transceiver operation.
Table of Contents
Core Cisco IOS CLI Commands to Check SFP Status and Inventory
To verify whether an SFP module is physically detected, properly seated, and passing traffic on a Cisco Catalyst switch (running Cisco IOS or IOS-XE), use the following privileged EXEC templates. Replace <interface-id> with your target port (for example, GigabitEthernet1/0/1 or TenGigabitEthernet1/1/1).
! 1. Verify port link state and detected SFP media type
Switch# show interfaces <interface-id> status
Port Name Status Vlan Duplex Speed Type
Gi1/0/1 Uplink-Core connected trunk a-full a-1000 1000BaseSX SFP
Gi1/0/2 Backup-Link notconnect 1 auto auto Not Present
! 2. Retrieve SFP Product ID (PID), Version (VID), and Serial Number (SN)
Switch# show inventory | include <interface-id>|PID
NAME: "Gi1/0/1", DESCR: "1000BaseSX SFP"
PID: GLC-SX-MMD , VID: V01 , SN: FNS19280ABC
! 3. Confirm hardware media capabilities recognized by the switch port
Switch# show interfaces <interface-id> capabilities
GigabitEthernet1/0/1
Model: WS-C3850-24T
Type: 1000BaseSX SFP
Speed: 1000
Duplex: full
! 4. Read raw EEPROM (IDPROM) vendor and wavelength data from the module
Switch# show idprom interface <interface-id>
General SFP Information
-----------------------
Identifier : 0x03 (SFP/SFP+/SFP28)
Connector : 0x07 (LC)
Transceiver : 1000Base-SX
Vendor Name : CISCO-AVAGO
Vendor Part Number : SFBR-5715PZ-CS2
Wavelength : 850 nm
If the Type column in show interfaces status displays 1000BaseSX SFP (or your corresponding fiber standard) and show inventory outputs a valid PID and SN, the switch has successfully read the module’s EEPROM. Once basic hardware recognition is confirmed, the next step is inspecting the quality of the optical signal itself.
How to Check SFP Light Levels and Optical Power (DOM)
Confirming that a switch recognizes an SFP module does not guarantee that the fiber strand is intact or clean. Digital Optical Monitoring (DOM) allows you to measure real-time optical transmit (Tx) and receive (Rx) power levels, internal temperature, voltage, and laser bias current directly from the CLI.
Follow these sequential steps to enable and inspect DOM readings on a Cisco Catalyst switch:
Enable Transceiver Monitoring (If Required)
While modern Catalyst 9000 Series switches running IOS-XE enable DOM automatically for supported modules, older Catalyst platforms require manual activation in global configuration mode:
ios
Switch# configure terminal
Switch(config)# transceiver type all
Switch(config-xcvr-type)# monitoring
Switch(config-xcvr-type)# monitoring interval 300
Switch(config-xcvr-type)# endCheck Summary Optical Power and Environmental Values
Run the basetransceivercommand to view current operating metrics across one or all optical interfaces:
“`ios
Switch# show interfaces GigabitEthernet1/0/1 transceiver
ITU Channel not available (Wavelength not available),
Transceiver is internally calibrated.
If device is externally calibrated, only calibrated values are printed.
++ : high alarm, + : high warning, – : low warning, — : low alarm.
NA or N/A: not applicable, Tx: transmit, Rx: receive.
mA: milliamperes, dBm: decibels (milliwatts).
Optical Optical
Temperature Voltage Tx Power Rx Power
Port (Celsius) (Volts) (dBm) (dBm)
Gi1/0/1 36.4 3.29 -5.1 -5.8
“`
Inspect Detailed DOM Thresholds
Append thedetailskeyword to compare current real-time readings against the transceiver’s factory-programmed warning and alarm boundaries:
ios
Switch# show interfaces GigabitEthernet1/0/1 transceiver details
This output generates separate tables for Temperature, Voltage, Current, Optical Transmit Power, and Optical Receive Power, showing exactHigh Alarm,High Warn,Low Warn, andLow Alarmcutoffs.Evaluate Tx and Rx Power Levels
Verify that bothOptical Tx PowerandOptical Rx Powersit comfortably between theHigh WarnandLow Warnvalues. IfTx Poweris normal (for example,-5.1 dBm) butRx Powerdrops to-30.0 dBmor-40.0 dBm, the local laser is transmitting properly, but no light is arriving from the remote switch due to a broken patch cord, dirty LC connector, or unpatched fiber pair.
While these commands apply to campus Catalyst switches, data center environments running Cisco Nexus switches use a slightly different command structure.
Checking SFP Transceiver Status on Cisco Nexus (NX-OS) Switches
In data center environments running Cisco NX-OS (such as Nexus 9000, 7000, or 5000 Series switches), use the singular show interface syntax and dedicated transceiver subcommands to inspect inventory, DOM readings, and calibration profiles.
! 1. Check SFP presence, part number, serial number, and nominal bitrate
Nexus-Switch# show interface ethernet 1/1 transceiver
Ethernet1/1
transceiver is present
type is 10Gbase-SR
name is CISCO-AVAGO
part number is SFBR-709SMZ-CS1
revision is G4.1
serial number is AVD21149XYZ
nominal bitrate is 10300 MBit/sec
cisco id is 3
cisco extended id number is 4
! 2. View real-time DOM diagnostics and threshold tables on NX-OS
Nexus-Switch# show interface ethernet 1/1 transceiver details
Ethernet1/1
transceiver is present
type is 10Gbase-SR
...
SFP Detail Diagnostics Information (internal calibration)
----------------------------------------------------------------------------
Alarms Warnings
High Low High Low
----------------------------------------------------------------------------
Temperature 39.2 C 75.0 C -5.0 C 70.0 C 0.0 C
Voltage 3.31 V 3.63 V 2.97 V 3.46 V 3.13 V
Current 6.12 mA 11.50 mA 2.00 mA 10.50 mA 3.00 mA
Tx Power -2.31 dBm 1.69 dBm -11.30 dBm -1.30 dBm -7.30 dBm
Rx Power -2.85 dBm 1.99 dBm -13.97 dBm -1.00 dBm -9.91 dBm
Transmit Fault Count = 0
----------------------------------------------------------------------------
Note: ++ high-alarm; -- low-alarm; + high-warning; - low-warning
! 3. Verify DOM calibration status across interfaces
Nexus-Switch# show interface ethernet 1/1 transceiver calibrations
Ethernet1/1
calibration is internal
Whether you are reviewing CLI outputs on NX-OS or IOS-XE, or inspecting the switch faceplate in a wiring closet, accurately interpreting the status flags and physical indicators is essential for rapid diagnosis.
Understanding SFP Port LED States and CLI Threshold Alarms
What do the physical SFP port LED colors and blinking states mean on a Cisco switch?
When inspecting the switch chassis in person, the port status LED next to the SFP cage provides immediate Layer 1 and Layer 2 feedback (assuming the switch is in default STAT LED mode):
* Off: No link is detected, no transceiver is inserted, or the port is administratively shut down.
* Solid Green: An active physical link is established and operational, with no traffic currently traversing the port.
* Blinking Green: The link is up and normal network traffic is actively being transmitted or received.
* Solid Amber: The port is operational at the physical layer but blocked by Spanning Tree Protocol (STP) to prevent a bridging loop, or the port has been placed into an err-disabled state.
* Blinking Amber: The port is blocked by STP while actively receiving BPDUs, or a hardware/transceiver fault has been detected on the interface.
* Alternating Green and Amber: A physical link fault is occurring, such as excessive symbol/CRC errors, a remote fault indication (RFI), or a duplex mismatch.
How do I read the High/Low Alarm and Warning flags in the CLI output?
In the transceiver details output, Cisco appends symbols next to any metric that breaches factory thresholds: + (High Warning), - (Low Warning), ++ (High Alarm), and -- (Low Alarm).
* Warnings (+ or -): Indicate the module is operating outside its optimal range—for example, elevated chassis temperature or slight signal attenuation from a dusty fiber ferrule. The link usually stays up, but preventive maintenance is needed.
* Alarms (++ or --): Indicate the measurement has crossed critical operational limits. A Low Alarm on Rx Power (--) usually causes link flapping or total loss of signal, while a High Alarm on Rx Power (++) on long-range optics without an optical attenuator can permanently burn out the receiving photodiode.
Why do negative dBm numbers look smaller in the Low Alarm column?
Optical power is measured in decibel-milliwatts (dBm) on a logarithmic scale where 0 dBm equals 1 mW of power. Values below 1 mW are expressed as negative numbers. Consequently, -3.0 dBm represents a much stronger light signal than -15.0 dBm. If your Low Warn threshold is -9.9 dBm and your Low Alarm is -13.9 dBm, a reading of -18.5 dBm falls below the -13.9 dBm threshold and triggers a Low Alarm (--).
When a physical LED turns solid amber or the CLI reports an interface failure before DOM metrics can even be read, you must transition from monitoring to active port recovery.
How to Troubleshoot Unrecognized or Err-Disabled SFP Modules
If an SFP module fails to appear in show interfaces status or immediately forces the port into an err-disabled state, follow this step-by-step diagnostic procedure to isolate and resolve the issue:
- Check the Err-Disabled Reason and Syslog Events
Verify why the switch disabled the port and inspect the system log for cryptographic or security validation errors:
“`ios
Switch# show interfaces status err-disabled
Port Name Status Reason Err-disabled Vlans
Gi1/0/1 Uplink-Core err-disabled gbic-invalid
Switch# show logging | include Gi1/0/1|TRANSCEIVER|GBIC
%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/1 has bad crc
%PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/1, putting Gi1/0/1 in err-disabled state
“`
- Inspect Physical Seating and Speed/Form-Factor Mismatches
If the port showsNot Presentrather thanerr-disabledand generates no syslog messages: - Reseat the transceiver firmly until the bale clasp latches.
- Confirm you have not inserted a 10G
SFP+module into a 1G-onlySFPslot (many 1G uplink slots cannot power or read 10G-only optics). If a 1G SFP is inserted into a 10G SFP+ port, manually hardcode the speed if required by the platform (
speed 1000orspeed nonegotiate).Enable Third-Party or Unsupported Transceivers (If Applicable)
Ifshow interfaces status err-disabledlistsgbic-invalidbecause you are using a third-party transceiver in a lab or non-critical environment, bypass the EEPROM vendor check in global configuration mode. Note that these commands are hidden in Cisco IOS (?tab completion will not display them) and must be typed in full:
ios
Switch# configure terminal
Switch(config)# service unsupported-transceiver
Warning: When Cisco determines that a fault or defect can be traced to
the use of third-party transceivers installed by a customer or partner,
then, at Cisco's discretion, Cisco may withhold support under warranty or
a Cisco support program.
Switch(config)# no errdisable detect cause gbic-invalid
Switch(config)# endBounce the Interface to Clear the Error State
After resolving the hardware mismatch or applying the unsupported transceiver configuration, reset the port to bring the link online:
ios
Switch# configure terminal
Switch(config)# interface GigabitEthernet1/0/1
Switch(config-if)# shutdown
Switch(config-if)# no shutdown
Switch(config-if)# end
If a genuine Cisco SFP module still fails to initialize or refuses to display DOM metrics after troubleshooting, the module or IOS release may lack hardware support on that specific switch model.
Verifying Hardware and DOM Support with the Cisco TMG Compatibility Matrix
The Cisco Transceiver Module Group (TMG) Compatibility Matrix is Cisco’s official technical reference database used to validate hardware, software, and diagnostic compatibility between Cisco optical transceivers and network platforms. Accessible via the official Cisco web portal (tmgmatrix.cisco.com), the tool provides authoritative specifications for every SFP, SFP+, SFP28, QSFP+, and QSFP28 module.
When querying the TMG Compatibility Matrix for an SFP module, verify the following four attributes:
- Product ID (PID) and Form Factor: Searches can be filtered by exact transceiver part number (such as
GLC-SX-MMD,GLC-LH-SMD, orSFP-10G-SR) or by switch chassis model (such asCatalyst 9300orNexus 9300). - Minimum Software Release: Specifies the exact minimum Cisco IOS, IOS-XE, or NX-OS version required for the switch supervisor or line card to recognize the transceiver’s IDPROM.
- DOM Support Status: Explicitly indicates whether Digital Optical Monitoring is supported for the selected switch-and-transceiver pairing. Older Cisco SFP part numbers lacking a
-D,-MMD, or-Ssuffix (for example, legacyGLC-SX-MMorGLC-Tcopper modules) do not contain internal DOM diagnostic hardware and will returnN/Aor unsupported errors when runningshow interfaces transceiver. - Port and Line Card Restrictions: Details slot-specific limitations, such as whether an SFP module is supported on fixed downlink ports, modular network uplink modules, or both.
Conclusion
Checking SFP status on a Cisco switch follows a structured progression from basic hardware detection to deep optical diagnostics. By starting with show interfaces status and show inventory to confirm physical presence, using show interfaces transceiver details to monitor real-time dBm light levels against DOM thresholds, and cross-referencing port LEDs with the Cisco TMG Compatibility Matrix, network administrators can quickly pinpoint and resolve fiber connectivity issues across both Catalyst and Nexus environments.











Comments