Identifying the exact Small Form-Factor Pluggable (SFP) transceivers installed in your Cisco switches and routers is a routine requirement for capacity planning, fiber troubleshooting, and hardware audits. Without physically pulling optics from live ports—which causes link flaps and network downtime—you can inspect media types, Cisco Product IDs (PIDs), serial numbers, and real-time optical power levels directly from the command-line interface (CLI).
This guide walks through the exact CLI commands to check SFP types in Cisco IOS and IOS-XE, how to inspect Digital Optical Monitoring (DOM) telemetry, how command syntax differs across NX-OS and IOS-XR, how to verify part numbers against Cisco’s official compatibility tools, and how to resolve unrecognized module errors or automate audits across an entire network fleet.
Table of Contents
Step-by-Step Guide to Checking SFP Type and Serial Number in Cisco IOS
When working on Cisco Catalyst switches or ISR/ASR routers running Cisco IOS or IOS-XE, three primary CLI commands provide progressively deeper visibility into your installed transceivers—ranging from basic media classification to raw EEPROM vendor data.
Step 1: Check the Active Media Type with show interfaces status
To quickly see the optical or copper standard operating on each port without sifting through detailed hardware logs, run show interfaces status. Focus on the Type column on the far right:
Switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Gi1/0/1 Uplink_Core_01 connected trunk a-full a-1000 1000BaseSX SFP
Gi1/0/2 Uplink_Core_02 connected trunk a-full a-1000 1000BaseLX SFP
Gi1/0/3 Backup_Link notconnect 1 auto auto No Transceiver
Te1/1/1 Wan_Edge connected routed full 10G SFP-10GBase-LR
- What it solves: Instantly confirms whether a slot is populated (
No Transceivervs. an active module) and identifies the IEEE physical layer specification (such as1000BaseSX,1000BaseLX, orSFP-10GBase-LR). - Limitation: It does not display the exact orderable Cisco part number or hardware serial number.
Step 2: Retrieve the Exact PID and Serial Number with show inventory
To obtain the orderable Cisco Product ID (PID), Version ID (VID), and factory Serial Number (SN) required for RMA replacements or asset tracking, run show inventory:
Switch# show inventory
NAME: "Switch 1", DESCR: "Cisco Catalyst 9300 48-port data only"
PID: C9300-48T , VID: V02 , SN: FCW2211G0AB
NAME: "Gi1/0/1", DESCR: "1000BaseSX SFP"
PID: GLC-SX-MMD , VID: V01 , SN: FNS1928104B
NAME: "Te1/1/1", DESCR: "SFP-10GBase-LR"
PID: SFP-10G-LR-S , VID: V01 , SN: AVD2104X991
- Tip: On high-density chassis switches, filter the output for a specific interface by piping the command:
show inventory | section Gi1/0/1orshow inventory | include Gi1/0/1|PID.
Step 3: Inspect Raw EEPROM Attributes with show idprom interface
If you need deeper physical specifications—such as laser wavelength, connector type, or original manufacturer metadata burned into the transceiver’s internal EEPROM (IDPROM)—use show idprom interface <interface-id>:
Switch# show idprom interface gigabitEthernet 1/0/1
General SFP Information
-----------------------------------------------
Identifier : 0x03 (SFP/SFP+/SFP28)
Connector : 0x07 (LC)
Transceiver : 1000BASE_SX (0x01)
Encoding : 0x01 (8B10B)
BR, Nominal : 1300 Mbps
Vendor Name : CISCO-FINISAR
Vendor Part Number : FTLF8519P3BNL-C6
Vendor Revision : A
Vendor Serial Number : FNS1928104B
Cisco Part Number : 10-2626-01
Cisco Product ID : GLC-SX-MMD
Laser Wavelength : 850 nm
- Alternative on select Catalyst platforms: If
show idpromis unavailable on your specific IOS-XE release, runshow controllers ethernet-controller <interface-id> phyto extract the same vendor EEPROM registers.
Key Takeaway: Use show interfaces status for rapid media identification, show inventory for asset PIDs and serial numbers, and show idprom interface for granular wavelength and OEM hardware attributes.
How to Check Optical Power Levels and DOM Telemetry
Once you have confirmed the physical SFP type installed in a port, the next logical step during link troubleshooting is verifying whether the laser is transmitting and receiving light within specification via Digital Optical Monitoring (DOM).
Step 1: Confirm the SFP Supports DOM
Not all legacy transceivers contain internal diagnostic sensors. Using the PID gathered from show inventory above, verify that the module supports DOM—typically indicated by a D suffix on 1G modules (e.g., GLC-SX-MMD, GLC-LH-SMD) or built natively into modern 10G/25G SFP+ and SFP28 modules.
Step 2: View Summary Optical Metrics Across Interfaces
Run show interfaces transceiver to view a concise table of real-time temperature, voltage, bias current, transmit (Tx) power, and receive (Rx) power across all DOM-capable ports:
Switch# show interfaces transceiver
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.
Optical Optical
Temperature Voltage Current Tx Power Rx Power
Port (Celsius) (Volts) (mA) (dBm) (dBm)
--------- ----------- ------- -------- -------- --------
Gi1/0/1 34.2 3.29 6.1 -5.1 -5.8
Te1/1/1 41.8 3.31 32.4 -2.3 -15.4 -
Notice the - flag next to Te1/1/1‘s Rx Power (-15.4 dBm), which immediately alerts you to a low-warning receive power condition caused by fiber attenuation or dirty patch cords.
Step 3: Inspect Detailed Thresholds with show interfaces transceiver detail
To compare live optical readings against the module’s factory-programmed High/Low Alarm and Warning thresholds, append the detail keyword for a specific interface:
Switch# show interfaces tengigabitethernet 1/1/1 transceiver detail
ITU Channel not available (Wavelength not available),
Transceiver is internally calibrated.
mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.
++ : high alarm, + : high warning, - : low warning, -- : low alarm.
High Alarm High Warn Low Warn Low Alarm
Temperature Threshold Threshold Threshold Threshold
Port (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)
--------- ------------------ ---------- --------- --------- ---------
Te1/1/1 41.8 75.0 70.0 0.0 -5.0
High Alarm High Warn Low Warn Low Alarm
Optical Threshold Threshold Threshold Threshold
Port Rx Power (dBm) (dBm) (dBm) (dBm)
--------- ------------------ ---------- --------- --------- ---------
Te1/1/1 -15.4 - 0.5 -1.0 -14.4 -18.4
Step 4: Interpret the Diagnostic Values
- Optical Tx Power (dBm): Measures the laser output leaving the local switch. If Tx power falls below the Low Alarm threshold, the local SFP transceiver is failing and must be replaced.
- Optical Rx Power (dBm): Measures incoming light from the remote device. If Rx power is marked with
-(low warning) or--(low alarm) while the remote device’s Tx power is normal, inspect the fiber path for excessive bends, faulty splices, or contaminated LC connectors. On short runs with long-range optics (e.g.,SFP-10G-ZR), Rx power marked with+or++indicates optical overload requiring an inline optical attenuator.
Key Takeaway: Always pair show interfaces <interface> transceiver detail with threshold markers (++, +, -, --) to isolate whether a link issue stems from a degraded local SFP or high loss along the physical fiber plant.
SFP Check Commands Across Cisco IOS, NX-OS, and IOS-XR
While Cisco IOS and IOS-XE share the commands covered above, data center switches running Cisco NX-OS (Nexus series) and service provider routers running Cisco IOS-XR (ASR 9000, NCS series) use different syntax structures. Use the comparison table below to translate SFP inspection commands across platforms.
| Inspection Task | Cisco IOS / IOS-XE (Catalyst, ISR/ASR 1000) | Cisco NX-OS (Nexus 9000, 7000, 5000, 3000) | Cisco IOS-XR (ASR 9000, NCS 5500/540) |
|---|---|---|---|
| Quick Media Type Summary | show interfaces status | show interface status or show interface brief | show interfaces brief |
| Hardware PID & Serial Number | show inventory | show inventory or show interface <intf> transceiver | show inventory or admin show inventory |
| Detailed Transceiver EEPROM / Vendor Info | show idprom interface <intf> | show interface <intf> transceiver details | show controllers <intf> phy |
| DOM Optical Power & Thresholds | show interfaces <intf> transceiver detail | show interface <intf> transceiver details | show controllers <intf> phy |
| Transceiver Calibration Data | Included in transceiver detail output | show interface <intf> transceiver calibrations | Included in show controllers <intf> phy |
| Verify Port Speed & Capabilities | show interfaces <intf> capabilities | show interface <intf> capabilities | show controllers <intf> all |
Key Takeaway: On Nexus (NX-OS), show interface <intf> transceiver details consolidates hardware inventory, vendor EEPROM, and DOM power levels into a single command, whereas IOS-XR centralizes physical-layer and optical telemetry under show controllers <intf> phy.
Cisco TMG Compatibility Matrix and Transceiver PID Reference
Once you extract a Cisco Product ID (PID) from the CLI, you can verify its physical reach, wavelength, and platform support using Cisco’s official hardware documentation.
Cisco Transceiver Module Group (TMG) Compatibility Matrix
The Cisco Transceiver Module Group (TMG) Compatibility Matrix (https://tmgmatrix.cisco.com) is Cisco’s authoritative database mapping transceiver PIDs to supported switch/router models, line cards, and minimum required OS versions.
- Lookup Parameters: Query by Transceiver Product ID (e.g.,
GLC-SX-MMD), Form Factor (SFP,SFP+,SFP28,QSFP28), or Host Platform Series (e.g.,Catalyst 9300). - Returned Specifications: Minimum software release (IOS-XE, NX-OS, IOS-XR), DOM support status, operating temperature range, cable type, core size, modal bandwidth, and maximum reach.
Common Cisco SFP and SFP+ PID Nomenclature
Use the reference specifications below to decode the most common transceiver PIDs returned by show inventory:
GLC-SX-MMD(1000BASE-SX):- Media & Wavelength: Multimode Fiber (MMF), 850 nm.
- Maximum Reach: 550 m on OM2/OM3/OM4 (275 m on FDDI/OM1).
- Attributes: LC duplex connector, Extended temperature (
-5°C to 85°C), DOM enabled (D). GLC-LH-SMD(1000BASE-LX/LH):- Media & Wavelength: Single-Mode Fiber (SMF) or MMF (with mode-conditioning patch cord), 1310 nm.
- Maximum Reach: 10 km over SMF (550 m over MMF).
- Attributes: LC duplex connector, Extended temperature, DOM enabled.
GLC-ZX-SMD(1000BASE-ZX):- Media & Wavelength: Single-Mode Fiber (SMF), 1550 nm.
- Maximum Reach: Approximately 70 km to 100 km depending on link loss budget.
- Attributes: LC duplex connector, DOM enabled.
GLC-TE/GLC-T(1000BASE-T):- Media & Wavelength: Category 5e/6 unshielded twisted-pair copper cable.
- Maximum Reach: 100 m.
- Attributes: RJ-45 connector, Extended temperature (
GLC-TE), no optical DOM. SFP-10G-SR/SFP-10G-SR-S(10GBASE-SR):- Media & Wavelength: Multimode Fiber (MMF), 850 nm.
- Maximum Reach: 300 m on OM3, 400 m on OM4.
- Attributes: SFP+ form factor, DOM enabled (
-Sdenotes S-Class enterprise version without OTN/WAN-PHY features). SFP-10G-LR/SFP-10G-LR-S(10GBASE-LR):- Media & Wavelength: Single-Mode Fiber (SMF), 1310 nm.
- Maximum Reach: 10 km.
- Attributes: SFP+ form factor, DOM enabled.
Key Takeaway: Always cross-reference the PID found in show inventory against the Cisco TMG Compatibility Matrix before migrating optics between chassis to ensure the target line card and software release support that specific module revision.
Troubleshooting “Unknown” or “Unsupported Transceiver” Errors
When checking SFP types in the CLI, you may encounter ports showing unknown in the Type column, missing DOM metrics, or interfaces shut down in an err-disabled (gbic-invalid) state. Below are solutions to the most common transceiver recognition problems.
Why does show interfaces status show unknown or unrecognized for the SFP type?
An unknown or unrecognized media type typically occurs for one of three reasons:
1. Software Version Mismatch: The installed Cisco IOS/IOS-XE release predates the release of a newer SFP hardware revision (for example, inserting an SFP-10G-SR-S or GLC-TE into an older switch running legacy code). Upgrade the switch software according to the TMG Matrix.
2. Speed Mismatch on Multi-Rate Ports: Inserting a 1G SFP into a 10G/25G uplink port may require manual speed configuration (speed 1000 or speed nonegotiate) before the port initializes the transceiver properly.
3. Corrupted EEPROM or Physical Seating Issue: Reseat the transceiver and inspect the gold edge connector Inside the SFP cage for dust or bent pins.
How do I fix %PHY-4-UNSUPPORTED_TRANSCEIVER and err-disabled (gbic-invalid)?
When you insert a third-party or non-Cisco coded SFP, the switch validates the cryptographic checksum stored in the transceiver’s EEPROM. If validation fails, the switch logs %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR or %PHY-4-UNSUPPORTED_TRANSCEIVER and places the port into an err-disabled state.
To bypass this check and bring the interface online, enter the following undirected (hidden) commands in global configuration mode:
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 reseller,
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)# interface gigabitEthernet 1/0/1
Switch(config-if)# shutdown
Switch(config-if)# no shutdown
Switch(config-if)# end
Note: The command service unsupported-transceiver does not support Tab auto-completion in the CLI; you must type the entire command manually.
Why does show interfaces transceiver return nothing or N/A on a working SFP?
If a port is up and passing traffic, but optical power output is blank or shows N/A:
* Verify the PID is not a non-DOM variant (such as the older GLC-SX-MM or GLC-LH-SM).
* On certain Catalyst platforms, DOM polling is disabled by default to conserve CPU cycles. Enable it globally with:
text
Switch(config)# transceiver type all
Switch(config-xcvr-type)# monitoring
Switch(config-xcvr-type)# monitoring interval 300
Key Takeaway: While service unsupported-transceiver and no errdisable detect cause gbic-invalid allow third-party optics to link up and report their EEPROM types, Cisco TAC may require you to reproduce physical-layer issues using genuine Cisco optics before opening a hardware RMA.
Automating Bulk SFP Audits via SNMP and Ansible
Logging into switches one by one to run show inventory is impractical across large enterprise networks. Use the SNMP OID template or the Ansible playbook below to extract and export SFP transceiver inventories across your entire Cisco fleet.
Option 1: SNMP ENTITY-MIB OID Template
Cisco switches expose installed SFP modules as physical entities within the standard ENTITY-MIB (1.3.6.1.2.1.47). Query these four OIDs using snmpwalk or your network monitoring system (NMS) to correlate port names with SFP part numbers and serial numbers:
# ENTITY-MIB Base OIDs for SFP Inventory
entPhysicalDescr : 1.3.6.1.2.1.47.1.1.1.1.2 # Media description (e.g., "1000BaseSX SFP")
entPhysicalName : 1.3.6.1.2.1.47.1.1.1.1.7 # Interface name (e.g., "Gi1/0/1")
entPhysicalSerialNum : 1.3.6.1.2.1.47.1.1.1.1.11 # Transceiver Serial Number
entPhysicalModelName : 1.3.6.1.2.1.47.1.1.1.1.13 # Cisco PID (e.g., "GLC-SX-MMD")
Run the following shell one-liner to query all installed hardware PIDs from a target switch:
# Replace <COMMUNITY> and <SWITCH_IP> with your SNMPv2c credentials or use SNMPv3 flags
snmpwalk -v2c -c <COMMUNITY> <SWITCH_IP> 1.3.6.1.2.1.47.1.1.1.1.13 | grep -E "GLC-|SFP-|QSFP-"
Option 2: Ansible Playbook to Export SFP Inventory to CSV
Save the following playbook as audit_cisco_sfp.yml. It connects to all switches in your [cisco_switches] inventory group, executes show inventory, parses out SFP/QSFP modules using regular expressions, and compiles a consolidated sfp_inventory_report.csv file:
---
- name: Audit and Export Cisco SFP Transceiver Inventory
hosts: cisco_switches
gather_facts: no
connection: network_cli
vars:
csv_output_path: "./sfp_inventory_report.csv"
tasks:
- name: Initialize CSV header on localhost
ansible.builtin.copy:
content: "Hostname,Interface_Name,Description,PID,Serial_Number\n"
dest: "{{ csv_output_path }}"
delegate_to: localhost
run_once: true
- name: Run show inventory on Cisco IOS/IOS-XE devices
cisco.ios.ios_command:
commands:
- show inventory
register: inv_output
- name: Parse SFP entries and append to CSV
ansible.builtin.lineinfile:
path: "{{ csv_output_path }}"
line: "{{ inventory_hostname }},{{ item.0 }},{{ item.1 }},{{ item.2 }},{{ item.3 }}"
insertafter: EOF
delegate_to: localhost
loop: "{{ inv_output.stdout[0] | regex_findall('NAME:\\s*\"((?:Gi|Te|TwentyFiveGigE|Fo|Hu|Ethernet)[^\"]+)\",\\s*DESCR:\\s*\"([^\"]+)\"\\s*\\nPID:\\s*(\\S+)\\s*,\\s*VID:[^,]+,\\s*SN:\\s*(\\S+)') }}"
Run the playbook from your control node:
ansible-playbook -i hosts.ini audit_cisco_sfp.yml
Key Takeaway: Polling entPhysicalModelName (1.3.6.1.2.1.47.1.1.1.1.13) via SNMP or parsing show inventory with Ansible eliminates manual CLI checks and keeps your transceiver asset database continuously updated.
Conclusion
Checking SFP types in Cisco environments starts with knowing which command matches your immediate diagnostic goal: show interfaces status for a rapid port-by-port media overview, show inventory for exact Cisco PIDs and serial numbers, and show interfaces transceiver detail (or its NX-OS and IOS-XR equivalents) for live optical health metrics. By combining these CLI checks with the Cisco TMG Compatibility Matrix and automated SNMP or Ansible collection, you can proactively validate hardware compatibility, isolate physical fiber issues in seconds, and maintain an accurate inventory across every switch in your network.











Comments