CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Tracking the serial numbers of Small Form-factor Pluggable (SFP, SFP+, and QSFP) transceivers is a routine requirement for network asset audits, Smart Net warranty renewals, Return Material Authorizations (RMAs), and counterfeit hardware checks. Because transceivers are hot-swappable field-replaceable units (FRUs) with their own internal EEPROM chips, you do not need to unplug fibers or schedule maintenance windows to read physical labels. Instead, you can query the module’s serial number directly from the Cisco command-line interface (CLI) or poll it remotely across your network.

Step-by-Step Guide to Checking SFP Serial Numbers on Cisco IOS and IOS-XE

On standard Cisco Catalyst switches and ISR/ASR routers running Cisco IOS or IOS-XE, retrieving an SFP serial number requires querying the system’s hardware inventory or reading the module’s EEPROM directly. Follow these sequential steps to locate the port and extract the transceiver’s unique identifier.

Step 1: Identify Active Transceiver Ports

Before querying hardware details, confirm which switch interfaces currently hold a plugged-in module and verify their media types. Run the following command from privileged EXEC mode:

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     notconnect   1          auto    auto   1000BaseLX SFP
Te1/1/1      Storage-Node       connected    10         full    10G    SFP-10GBase-SR

Look at the Type column. Any port displaying a media type (such as 1000BaseSX SFP or SFP-10GBase-SR) rather than Not Present has a detected transceiver installed.

Step 2: Retrieve the Serial Number via Hardware Inventory

Once you know which ports contain optics, execute the show inventory command. This command reads the standard Cisco Entity MIB data and outputs the Product ID (PID), Version ID (VID), and Serial Number (SN) for the chassis, power supplies, and every recognized transceiver:

Switch# show inventory
NAME: "Switch 1", DESCR: "Cisco Catalyst 9300 48-port data only"
PID: C9300-48T         , VID: V02  , SN: FOC2314L0AA

NAME: "GigabitEthernet1/0/1", DESCR: "1000BaseSX SFP"
PID: GLC-SX-MMD        , VID: V01  , SN: FNS19420B7K

NAME: "TenGigabitEthernet1/1/1", DESCR: "SFP-10GBase-SR"
PID: SFP-10G-SR-S      , VID: V01  , SN: AVD2133C91P

On modular chassis or dense switch stacks with dozens of optics, filter the output to a specific interface using regular expressions or interface arguments:

Switch# show inventory | section GigabitEthernet1/0/1

Step 3: Query the Transceiver EEPROM Directly with IDPROM

If you need deeper vendor metadata—such as the original optic manufacturer’s name, part number, date code, and raw serial number—query the Identification Programmable Read-Only Memory (IDPROM) on the specific interface:

Switch# show idprom interface GigabitEthernet1/0/1
General SFP Information
-----------------------------------------------
Identifier            : 03h (SFP/SFP+)
Connector             : 07h (LC)
Transceiver           : 1000Base-SX
Vendor Name           : CISCO-FINISAR
Vendor Part Number    : FTLF8519P3BNL-C2
Vendor Revision       : A
Vendor Serial Number  : FNS19420B7K
Cisco Extended ID     : 04h
Cisco Part Number     : 10-2626-01
Cisco Product ID      : GLC-SX-MMD

Section Takeaway: Use show inventory for fast, switch-wide serial number lookups on Cisco IOS/IOS-XE, and use show idprom interface <interface-id> when you need to inspect raw factory EEPROM fields for a specific port.


Comparing Cisco Transceiver Inspection Commands

A common point of confusion on Cisco IOS and IOS-XE platforms is assuming that optical diagnostic commands also display hardware serial numbers. While show interfaces transceiver is essential for checking light levels, it omits the serial number on many Catalyst platforms. The comparison table below breaks down the exact capabilities of each Cisco transceiver command so you can choose the right tool for your workflow.

CommandOutputs Serial Number (SN)?Outputs Cisco PID & Vendor Info?Outputs DOM Optical Levels (Tx/Rx)?Primary Use Case & Platform Behavior
show inventoryYesYes (PID and VID)NoStandard command across IOS, IOS-XE, NX-OS, and IOS-XR to list all recognized hardware assets and serial numbers.
show idprom interface <id>Yes (Vendor SN)Yes (Full OEM & Cisco Part #)NoReads raw SFF-8472 EEPROM registers on a per-port basis in IOS and IOS-XE; ideal for verifying genuine optics.
show interfaces transceiver [detail]Platform-dependent (No on IOS/IOS-XE; Yes on NX-OS)Platform-dependent (Basic type on IOS; Full PID/Vendor on NX-OS)Yes (Temp, Voltage, Current, Tx/Rx dBm)Monitors Digital Optical Monitoring (DOM) health thresholds. Only outputs serial numbers on Nexus (NX-OS) switches.
show interfaces statusNoPartial (Displays media type only)NoQuick verification of port operational status (connected/notconnect/err-disabled), speed, and transceiver form factor.

Section Takeaway: On Catalyst IOS/IOS-XE switches, pair show inventory (for asset serial numbers) with show interfaces transceiver detail (for optical power budgets); on Nexus switches, a single transceiver command can provide both.


How to Check SFP Serial Numbers on Cisco NX-OS, ACI, and IOS-XR

While the show inventory command works across almost all Cisco operating systems, data center and service provider platforms offer specialized commands and object queries tailored to their architectures. Follow the platform-specific syntax below when working outside standard Catalyst environments.

Step 1: Retrieve SFP Serial Numbers on Cisco Nexus (NX-OS)

On Cisco Nexus switches, you can view SFP serial numbers either globally via show inventory or per-interface using the transceiver command, which—unlike IOS—dumps the entire EEPROM alongside DOM readings:

Nexus9K# show interface ethernet 1/1 transceiver details
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 AVD2118A3B9
    nominal bitrate is 10300 MBit/sec
    cisco id is 3
    cisco extended id number is 4
    cisco part number is 10-2415-03
    cisco product id is SFP-10G-SR
    cisco vendor id is V03

To get a clean list of all installed optics and their serial numbers across the entire Nexus chassis at once, filter show inventory:

Nexus9K# show inventory | grep -E "Ethernet|PID"

Step 2: Query Fabric-Wide SFP Serial Numbers in Cisco ACI

In a Cisco Application Centric Infrastructure (ACI) environment, you do not need to SSH into every leaf and spine switch individually. Instead, log into the APIC CLI and use the Managed Object Query (moquery) utility to inspect the ethpmFcot ( Fibre Channel / Optical Transceiver) class across the entire fabric:

apic1# moquery -c ethpmFcot -f 'ethpm.Fcot.guiCiscoPID!=""' | egrep "dn|guiCiscoPID|guiName|guiSN"
dn          : topology/pod-1/node-101/sys/phys-[eth1/1]/phys/fcot
guiCiscoPID : SFP-10G-SR
guiName     : CISCO-FINISAR
guiSN       : FNS22091K4L

The dn (Distinguished Name) tells you the exact pod, leaf node ID (node-101), and physical interface (eth1/1), while guiSN provides the transceiver’s serial number.

Step 3: Inspect Optics on Service Provider Routers (Cisco IOS-XR)

On Cisco ASR 9000, NCS 5500, and 8000 Series routers running IOS-XR, transceiver modules are indexed by port name in show inventory (or show inventory raw). To inspect a specific interface’s hardware EEPROM and optical controller directly, run the show controllers phy command:

RP/0/RP0/CPU0:ASR9K# show controllers TenGigE0/0/0/1 phy
SFP EEPROM Summary:
        Transceiver Type: SFP+ 10GBASE-LR
        Cisco PID: SFP-10G-LR
        Vendor Name: CISCO-OPNEXT
        Vendor Serial Number: OPN1844029A
        Vendor Part Number: TRF5014EN-GA400

Section Takeaway: Use show interface ethernet <slot/port> transceiver details on NX-OS, moquery -c ethpmFcot on ACI APICs for fabric-wide discovery, and show controllers <interface> phy on IOS-XR routers.


Troubleshooting Missing SFP Serial Numbers in Cisco CLI

Sometimes an SFP module is physically plugged into a switch port, yet its serial number does not appear in standard show inventory output. The questions below address the most common causes and fixes for undetectable transceivers.

Why is a plugged-in SFP missing from show inventory, and how does show inventory raw fix it?

Standard show inventory only displays hardware components that have passed Cisco’s FRU initialization and PID validation checks. If a transceiver has an unrecognized Product ID, blank PID fields, or is plugged into an unprovisioned port, the operating system hides it from standard output. Running show inventory raw forces the switch to dump every internal Entity MIB index and I2C sensor detected on the backplane, revealing the serial number of modules omitted from the filtered view:

Switch# show inventory raw | include Gi1/0/2|SN:

How do I view the serial number of a third-party or “unsupported” SFP module?

When you insert a non-Cisco or uncoded third-party SFP, the switch may generate a %PM-4-ERR_DISABLE: gbic-invalid error detected syslog message and shut down the port. While in this state, the SFP is often excluded from show inventory. First, try reading the raw EEPROM directly via show idprom interface <interface-id>. If the switch blocks I2C polling until the port is initialized, enable unsupported transceivers in global configuration mode and bounce the port:

Switch# configure terminal
Switch(config)# service unsupported-transceiver
Switch(config)# no errdisable detect cause gbic-invalid
Switch(config)# interface GigabitEthernet1/0/2
Switch(config-if)# shutdown
Switch(config-if)# no shutdown

(Note: Using service unsupported-transceiver generates a disclaimer stating that Cisco TAC may require you to reproduce link issues with genuine Cisco optics before providing hardware support.)

Why does an SFP fail to appear in both show inventory raw and show idprom?

If neither command detects the module, the switch’s I2C bus cannot communicate with the transceiver’s EEPROM chip. Check three physical and configuration factors:
1. Incomplete physical seating: Reseat the transceiver firmly until the latch clicks, and inspect the SFP cage for bent backplane pins.
2. Port speed/group mismatch: On dual-rate uplink modules (such as 1G/10G or 10G/25G port groups), inserting a 1G SFP into a port group locked to 10G/25G mode may prevent initialization until speed 1000 or speed nonegotiate is configured.
3. Dead EEPROM: Check show logging | include transceiver|SFP|GBIC while inserting the module. If no insertion event triggers in the logs, the module’s EEPROM or power circuitry is likely defective.

Section Takeaway: When an optic is missing from standard CLI outputs, bypass software filters using show inventory raw or show idprom interface, and check show logging to see if third-party security checks have err-disabled the port.


Bulk SFP Serial Number Collection via SNMP and Automation Templates

When auditing hundreds of switches, manually running CLI commands on each device is impractical. You can automate bulk SFP serial number discovery across your network using SNMP polling against the standard ENTITY-MIB or by running a Python script.

1. SNMP OIDs and snmpwalk Template

Cisco exposes all hardware inventory fields—including SFP serial numbers—under the standard ENTITY-MIB (1.3.6.1.2.1.47):
* entPhysicalDescr (1.3.6.1.2.1.47.1.1.1.1.2): Port name or transceiver description (e.g., SFP-10GBase-SR).
* entPhysicalName (1.3.6.1.2.1.47.1.1.1.1.7): Interface identifier (e.g., TenGigabitEthernet1/1/1).
* entPhysicalSerialNum (1.3.6.1.2.1.47.1.1.1.1.11): Hardware serial number.
* entPhysicalModelName (1.3.6.1.2.1.47.1.1.1.1.13): Cisco Product ID (PID).

Use this snmpwalk template from a Linux management host to pull all hardware serial numbers from a switch:

# SNMPv2c bulk serial number walk
snmpwalk -v2c -c <SNMP_COMMUNITY> <SWITCH_IP> 1.3.6.1.2.1.47.1.1.1.1.11

# Correlate interface names (.7) and serial numbers (.11) using snmptable
snmptable -v2c -c <SNMP_COMMUNITY> -Ci <SWITCH_IP> 1.3.6.1.2.1.47.1.1.1

2. Python Netmiko Script for Multi-Switch CSV Export

Use the runnable Python script below to SSH into a list of Cisco switches, parse show inventory for transceiver interfaces, and export all SFP serial numbers to a single CSV file:

import csv
import re
from netmiko import ConnectHandler

SWITCHES = ["10.10.1.10", "10.10.1.11", "10.10.1.12"]
USERNAME = "admin"
PASSWORD = "YOUR_PASSWORD"

INVENTORY_REGEX = re.compile(
    r'NAME:\s*"(?P<name>[^"]+)",\s*DESCR:\s*"(?P<descr>[^"]+)"\s*\n'
    r'PID:\s*(?P<pid>\S*)\s*,\s*VID:\s*(?P<vid>\S*)\s*,\s*SN:\s*(?P<sn>\S+)',
    re.MULTILINE
)

SFP_KEYWORDS = ("Ethernet", "Gi", "Te", "Tw", "Fo", "Hu", "Eth", "SFP", "QSFP")

with open("cisco_sfp_serials.csv", mode="w", newline="") as file:
    writer = csv.writer(file)
    writer.writerow(["Switch_IP", "Interface", "Description", "PID", "VID", "Serial_Number"])

    for ip in SWITCHES:
        device = {
            "device_type": "cisco_ios",
            "host": ip,
            "username": USERNAME,
            "password": PASSWORD,
        }
        with ConnectHandler(**device) as conn:
            output = conn.send_command("show inventory")
            for match in INVENTORY_REGEX.finditer(output):
                name = match.group("name")
                descr = match.group("descr")
                if any(k in name or k in descr for k in SFP_KEYWORDS):
                    writer.writerow([
                        ip,
                        name,
                        descr,
                        match.group("pid"),
                        match.group("vid"),
                        match.group("sn")
                    ])

Section Takeaway: Poll OID 1.3.6.1.2.1.47.1.1.1.1.11 (entPhysicalSerialNum) via your NMS or run the Python Netmiko parser above to compile an enterprise-wide SFP serial number inventory in seconds.


Official Cisco Reference Tools for Serial Number Validation and Compatibility

Once you have retrieved the PID, VID, and SN values from your switches, use the official Cisco specifications and verification portals below to validate transceiver authenticity, check warranty status, and verify platform compatibility.

Cisco 11-Character Serial Number Format Specification

Genuine Cisco transceivers adhere to a strict 11-character alphanumeric serial number format (LLLYYWWXXXX) burned into the EEPROM and printed on the physical pull-tab label:
* Characters 1–3 (LLL — Manufacturing Location Prefix): Identifies the Cisco-contracted factory. Common valid codes include FOC (Foxconn, Shenzhen), FNS (Finisar), JPE (Jabil, Malaysia), JSH (Jabil, Shanghai), JAB (Jabil, Florida), CTH (Celestica, Thailand), and AVD (Avago/Broadcom).
* Characters 4–5 (YY — Year Code): Indicates the manufacturing year relative to Cisco’s base year of 1996 (for example, 26 = $1996 + 26 = 2022$; 28 = $1996 + 28 = 2024$).
* Characters 6–7 (WW — Work Week): Two-digit manufacturing week of the year (01 through 52).
* Characters 8–11 (XXXX — Unique Sequence ID): Four-character alphanumeric production lot identifier (uppercase letters and numbers, excluding I and O to avoid confusion with 1 and 0).

Official Cisco Verification and Compatibility Portals

  • Cisco Transceiver Module Group (TMG) Compatibility Matrix (https://tmgmatrix.cisco.com): The authoritative interactive database mapping Cisco SFP, SFP+, SFP28, QSFP+, and QSFP28 PID values against supported switch models, line cards, and minimum required IOS-XE, NX-OS, or IOS-XR software releases.
  • Cisco Optics-to-Optics Interoperability Matrix (https://tmgmatrix.cisco.com/iop): Official reference tool used to confirm whether two different Cisco transceiver PIDs (for example, a breakout QSFP+ on a core switch and an SFP+ on an access switch) are optically compatible across a link.
  • Cisco Serial Number Check Tool (https://cway.cisco.com/sncheck): Requires a Cisco.com (CCO) login. Allows administrators to input up to 50 serial numbers at a time to confirm whether a transceiver serial number is recognized in Cisco’s global manufacturing database, verify active warranty coverage, and check Smart Net contract eligibility.
  • Cisco Brand Protection (brandprotection@cisco.com): Official verification channel for reporting suspected counterfeit transceivers when the CLI serial number (show idprom interface) does not match the physical housing label or fails the 11-character format specification.

Section Takeaway: Cross-reference your collected SFP PID and SN data against the 11-character LLLYYWWXXXX structure, the Cisco TMG Compatibility Matrix (tmgmatrix.cisco.com), and the Cisco Serial Number Check portal (cway.cisco.com/sncheck) to verify hardware legitimacy and supportability.


Conclusion

Checking an SFP serial number on Cisco hardware starts with selecting the right command for your operating system: show inventory and show idprom interface on Cisco IOS/IOS-XE, show interface transceiver details on NX-OS, moquery -c ethpmFcot on ACI, and show controllers phy on IOS-XR. If a module fails to appear in standard outputs, inspecting raw hardware indexes with show inventory raw or checking for err-disabled third-party optic restrictions quickly isolates the cause. By combining these CLI techniques with SNMP ENTITY-MIB polling and Cisco’s official validation tools, you can maintain an accurate, verifiable inventory of every optical transceiver in your network.

Please follow and like us:
Last modified: November 18, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.