CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Verifying the health of fiber optic uplinks on a Cisco switch requires more than checking whether the physical port LED is green. Because fiber links rely on laser transceivers (SFP, SFP+, QSFP+) and delicate glass strands, links can suffer from signal attenuation, dirty ferrules, polarity mismatches, or transceiver firmware blocks even when the interface configuration looks clean.

By combining basic Cisco CLI inventory commands with Digital Optical Monitoring (DOM), you can inspect installed transceiver modules, measure real-time optical transmit and receive power in decibel-milliwatts (dBm), and isolate physical layer faults before they cause packet loss or link flaps.

Essential CLI Commands to Check Fiber Port Status and SFP Inventory

Before inspecting optical light levels, verify which fiber interfaces are active and confirm the hardware specifications of the installed Small Form-Factor Pluggable (SFP/SFP+) modules. Use the following Cisco IOS / IOS-XE CLI command template to audit link status, media type, vendor part numbers, and serial numbers:

! 1. Check link state, VLAN assignment, speed, and detected SFP media type
Switch# show interfaces status | include SFP|10G|connected

Port         Name               Status       Vlan       Duplex  Speed Type
Gi1/0/49     Uplink-Core-01     connected    trunk      a-full  a-1000 1000BaseSX SFP
Gi1/0/50     Uplink-Core-02     notconnect   1          auto    auto   1000BaseLX SFP
Te1/1/1      WAN-Distribution   connected    trunk      full    10G    SFP-10GBase-LR
Te1/1/2      Backup-Link        err-disabled 1          auto    auto   unknown

! 2. List Product IDs (PID), Vendor IDs, and Serial Numbers for all plugged-in SFPs
Switch# show inventory | begin TenGigabitEthernet|GigabitEthernet

NAME: "GigabitEthernet1/0/49", DESCR: "1000BaseSX SFP"
PID: GLC-SX-MMD        , VID: V03  , SN: AGM2145XXXX

NAME: "TenGigabitEthernet1/1/1", DESCR: "SFP-10GBase-LR"
PID: SFP-10G-LR        , VID: V02  , SN: FNS2310YYYY

! 3. Confirm hardware capabilities and media type on a specific fiber port
Switch# show interfaces TenGigabitEthernet1/1/1 capabilities

TenGigabitEthernet1/1/1
  Model:                 C9300-24T
  Type:                  SFP-10GBase-LR
  Speed:                 10000
  Duplex:                full
  Trunk encap. type:     802.1Q

! 4. Read the raw SFP EEPROM (IDPROM) for wavelength, vendor, and manufacturing data
Switch# show idprom interface GigabitEthernet1/0/49 | include Product|Vendor|Wavelength|Serial

  Product Identifier               = SFP/SFP+
  Vendor Name                      = CISCO-AVAGO
  Vendor Part Number               = SFBR-5715APZ-CS2
  Vendor Serial Number             = AGM2145XXXX
  Laser Wavelength                 = 850 nm

Running these four commands establishes whether the switch recognizes the physical transceiver hardware (Type and PID) before you move on to optical signal testing.

How to Check Fiber Light Levels and Optical Power (DOM)

Once you confirm the switch detects the transceiver, the next step is measuring the actual laser signal across the fiber strand using Digital Optical Monitoring (DOM). DOM allows the switch to read real-time diagnostic metrics directly from the transceiver’s onboard sensor chip.

Step 1: Verify DOM Hardware Support

Not all legacy transceivers contain optical diagnostic sensors. Ensure your installed Cisco modules support DOM—most modern modules marked with a -D suffix (such as GLC-SX-MMD or GLC-LH-SMD) and standard 10G/25G/40G/100G modules (SFP-10G-SR, SFP-10G-LR, SFP-10G-S-ac) include built-in SFF-8472 optical monitoring.

Step 2: Enable Transceiver Monitoring in Global Configuration

On many Cisco Catalyst switches, DOM polling is enabled by default, but on certain IOS platforms it must be turned on globally to populate sensor data:

Switch# configure terminal
Switch(config)# transceiver type all
Switch(config-xcvr-type)# monitoring
Switch(config-xcvr-type)# monitoring interval 300
Switch(config-xcvr-type)# end

The monitoring interval defines how often (in seconds, from 300 to 3600) the switch polls the transceiver sensors for updated readings.

Step 3: Check Summary Optical Power Levels Across All Fiber Ports

Run show interfaces transceiver to view a concise table of internal temperature, supply voltage, laser bias current, Transmit (Tx) power, and Receive (Rx) power for every DOM-capable port on the switch:

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  Tx Power  Rx Power
Port       (Celsius)    (Volts)  (dBm)     (dBm)
---------  -----------  -------  --------  --------
Gi1/0/49     38.2       3.29      -5.1      -6.4
Te1/1/1      41.5       3.31      -2.3     -15.8 --

Step 4: Inspect Granular Per-Port Thresholds

If a port shows questionable light levels, append the detail keyword to compare current readings against the transceiver’s factory-programmed High and Low alarm thresholds:

Switch# show interfaces TenGigabitEthernet1/1/1 transceiver detail

ITU Channel not available (Wavelength not available),
Transceiver is internally calibrated.
mA: milliamperes, dBm: decibels (milliwatts).
                                 High       High        Low         Low
           Current               Alarm      Warning     Warning     Alarm
           Measurement           Threshold  Threshold   Threshold   Threshold
Port       (dBm)                 (dBm)      (dBm)       (dBm)       (dBm)
---------  --------------------  ---------  ----------  ----------  ---------
Te1/1/1
  Tx Power   -2.3                    0.5       -1.0        -8.2       -10.2
  Rx Power  -15.8 --                 0.5       -1.0       -14.4       -16.4

Measuring both ends of a fiber circuit with show interfaces transceiver detail lets you calculate total path loss by subtracting the far-end Rx power from the local Tx power.

Interpreting Optical Power Output and Normal dBm Ranges

Having the raw dBm numbers from the CLI is only useful if you know what healthy signal levels look like for your specific optic type. Optical power is measured on a logarithmic scale relative to 1 milliwatt (0 dBm = 1 mW), meaning values closer to 0 (such as -2.5 dBm) represent a stronger signal than more negative values (such as -18.0 dBm), and every 3 dB drop represents a 50% loss in optical power.

Use the table below to compare healthy Tx and Rx operating ranges across the most common Cisco SFP and SFP+ fiber modules:

Transceiver Module (PID)Fiber Mode & WavelengthNormal Tx Power Range (dBm)Acceptable Rx Power Range (dBm)Receiver Overload / Floor Limits
GLC-SX-MMD (1000BASE-SX)Multimode (MMF), 850 nm-9.5 to -3.0 dBm-17.0 to 0.0 dBmOverload > 0.0 dBm; Drop < -17.0 dBm
GLC-LH-SMD (1000BASE-LX/LH)Single-Mode (SMF) / MMF, 1310 nm-9.5 to -3.0 dBm-20.0 to -3.0 dBmOverload > -3.0 dBm; Drop < -20.0 dBm
SFP-10G-SR (10GBASE-SR)Multimode (MMF), 850 nm-7.3 to -1.0 dBm-9.9 to -1.0 dBmOverload > -1.0 dBm; Drop < -9.9 dBm
SFP-10G-LR (10GBASE-LR)Single-Mode (SMF), 1310 nm-8.2 to +0.5 dBm-14.4 to +0.5 dBmOverload > +0.5 dBm; Drop < -14.4 dBm
SFP-10G-ER (10GBASE-ER)Single-Mode (SMF), 1550 nm-4.7 to +4.0 dBm-15.8 to -1.0 dBmOverload > -1.0 dBm (requires attenuator on short runs)

In addition to raw dBm ranges, Cisco switches append flag symbols next to readings that breach factory thresholds:

Cisco CLI FlagMeaningOperational Impact & Recommended Action
(No symbol)Normal Operating RangeOptical power is within specification; no action required.
+High WarningSignal is approaching receiver saturation. Verify if high-powered long-range optics (ER/ZR) are connected over a short patch cable without an optical attenuator.
++High AlarmCritical receiver overload. Risk of permanent photodiode damage and high CRC errors; install an inline optical attenuator immediately.
-Low WarningSignal is degrading toward the receiver sensitivity floor. Clean fiber patch cord ferrules and inspect patch panels for tight bends.
--Low AlarmSignal is below minimum receiver sensitivity (or -40.0 dBm indicating total loss of light). Expect link flaps, input errors, or a notconnect state.

Always evaluate Rx power alongside the threshold flags: a reading of -13.5 dBm is perfectly healthy on a 10GBASE-LR single-mode link, but would indicate a dead link on a 10GBASE-SR multimode optic.

Platform Syntax Reference: Cisco Catalyst (IOS/IOS-XE) vs. Nexus (NX-OS)

While the underlying SFF-8472 optical telemetry standards are identical, command syntax and hardware verification workflows differ between campus Cisco Catalyst switches (running IOS or IOS-XE) and data center Cisco Nexus switches (running NX-OS).

CLI Command Equivalency Specification

  • Optical Summary Status:
  • Catalyst IOS / IOS-XE: show interfaces transceiver
  • Nexus NX-OS: show interface transceiver
  • Detailed Threshold & Alarm Output:
  • Catalyst IOS / IOS-XE: show interfaces [<interface-id>] transceiver detail (singular detail)
  • Nexus NX-OS: show interface [<interface-id>] transceiver details (plural details)
  • EEPROM / Serial PROM Hardware Inspection:
  • Catalyst IOS / IOS-XE: show idprom interface <interface-id>
  • Nexus NX-OS: show interface <interface-id> transceiver sprom
  • Optical Sensor Calibration Inspection:
  • Catalyst IOS / IOS-XE: show interfaces transceiver calibration
  • Nexus NX-OS: show interface transceiver calibrations
  • Transceiver Presence & Port Mapping:
  • Catalyst IOS / IOS-XE (Catalyst 9000 Series): show platform software fed switch active ifm mappings
  • Nexus NX-OS (Nexus 9000 Series): show interface status or show hardware internal tah interface <interface-id>

Official Compatibility and Documentation Matrices

  • Cisco Transceiver Module Group (TMG) Compatibility Matrix: The authoritative lookup database (tmgmatrix.cisco.com) defining supported SFP/SFP+/QSFP28 Product IDs, minimum required IOS-XE or NX-OS software versions, and DOM support capabilities per switch chassis and line card.
  • Cisco Catalyst 9000 Series Configuration Guides: Documented under Interface and Hardware Component Configuration Guide -> Configuring Transceiver Modules, detailing DOM polling intervals and Dual-Rate port configuration.
  • Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide: Specifies Layer 1 optical diagnostics, breakout cable channel mapping (Ethernet1/1/1 through 1/1/4), and DOM SNMP trap generation.

Referencing the correct OS syntax ensures scripts and operational runbooks execute cleanly across mixed Catalyst and Nexus environments.

Troubleshooting a Cisco Fiber Port Not Coming Up or Err-Disabled

When a fiber port shows notconnect or enters an err-disabled state despite having a patch cord plugged in, follow this sequential diagnostic workflow to isolate and fix the root cause.

Step 1: Check for err-disabled State and System Logs

Run show interfaces status err-disabled and inspect recent syslog messages to see why the switch shut down the port:

Switch# show interfaces status err-disabled

Port      Name               Status       Reason               Err-disabled Vlans
Te1/1/2   Backup-Link        err-disabled gbic-invalid

Switch# show logging | include Te1/1/2|TRANSCEIVER
%PHY-4-UNSUPPORTED_TRANSCEIVER: Unsupported transceiver found in Te1/1/2
%PM-4-ERR_DISABLE: gbic-invalid error detected on Te1/1/2, putting Te1/1/2 in err-disabled state

Step 2: Bypass Unsupported Third-Party SFP Blocks (gbic-invalid)

If you are using a non-Cisco or third-party SFP module and the port drops into err-disabled (gbic-invalid), you can instruct Cisco IOS/IOS-XE to allow third-party transceivers using two undocumented global commands (note that Cisco TAC may request authentic Cisco optics during support cases):

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

Step 3: Fix Rolled Fiber Polarity (TX/RX Cross-Over)

If the port status is notconnect and show interfaces transceiver (as covered above) shows normal Tx Power on both switches, but Rx Power reads -40.0 dBm (-- Low Alarm) on both ends, the fiber strands are almost certainly rolled.
* Why it happens: Fiber links require the Transmit (Tx) laser on Switch A to connect to the Receive (Rx) photodiode on Switch B. If a straight-through patch cord is used where a crossover is needed, both lasers fire into each other on one strand while both receivers listen to dark glass on the other.
* How to fix it: Pop the plastic clip on one end of the duplex LC connector, swap the two fiber boots so Strand A and Strand B cross over, and re-insert the connector. Verify immediately with show interfaces transceiver to see if Rx power jumps into the normal range.

Step 4: Verify Wavelength Matching and Clean Dirty Connectors

If swapping fiber polarity does not restore Rx light, or if Rx power remains stuck in the -- Low Alarm zone (for example, -22.0 dBm), check for physical mismatch or contamination:
* Wavelength/Mode Mismatch: Confirm via show interfaces status on both switches that an 850 nm multimode SFP (GLC-SX-MMD or SFP-10G-SR) is not plugged into a 1310 nm single-mode SFP (GLC-LH-SMD or SFP-10G-LR) on the far end, and verify the patch cord jacket matches the transceiver mode (Aqua/Orange for MMF; Yellow for SMF).
* Contaminated Ferrules: Dust or skin oils on the fiber tip can cause 3 dB to 10+ dB of attenuation. Clean both the patch cord tips and the SFP internal bores using a dry One-Click fiber optic cleaner.

Step 5: Resolve Speed and Auto-Negotiation Mismatches

Occasionally, DOM shows healthy Tx and Rx power on both ends (for example, -4.5 dBm), yet the port remains notconnect. This indicates a Layer 1 framing or negotiation mismatch rather than a light problem:
* Check speed nonegotiate: On 1000BASE-X fiber links, IEEE 802.3z auto-negotiation exchanges link pulses before bringing the interface up. If one switch has speed nonegotiate configured on the interface and the far-end switch (or media converter) has auto-negotiation enabled, the link will remain down. Either remove speed nonegotiate on both sides or configure it identically on both ends.
* Lock Speed on Dual-Rate SFP+ Slots: When plugging a 1G SFP module (GLC-SX-MMD) into a 10G/25G port, explicitly configure speed 1000 (or duplex full depending on platform) on both switches if auto-detection fails to negotiate the downshift.

Walking through these five checks systematically separates administrative software locks, physical cable breaks, and link-negotiation mismatches in minutes.

Best Network Monitoring Tools to Track Cisco Fiber Port Optical Levels via SNMP

Rather than waiting for a fiber link to fail and running manual CLI commands, network teams can poll Cisco DOM telemetry automatically via SNMP. Cisco exposes optical dBm, temperature, and bias current metrics through the CISCO-ENTITY-SENSOR-MIB (specifically entSensorValue at OID 1.3.6.1.4.1.9.9.91.1.1.1.1.4 and entSensorThresholdValue at 1.3.6.1.4.1.9.9.91.1.2.1.1.4), linked to interface names in the ENTITY-MIB (entPhysicalDescr).

Here are the top network monitoring platforms capable of tracking Cisco SFP optical power levels and alerting on laser degradation automatically:

  1. LibreNMS
  2. How it handles Cisco DOM: Automatically discovers CISCO-ENTITY-SENSOR-MIB optical sensors during standard device discovery without requiring manual OID mapping.
  3. Key advantage: Reads the factory High/Low warning and alarm thresholds directly from the switch via SNMP, plots historical dBm graphs per fiber interface, and triggers alerts as soon as light levels begin drifting downward.
  4. Paessler PRTG Network Monitor
  5. How it handles Cisco DOM: Uses the built-in SNMP Cisco System Health sensor or customizable SNMP Custom Table sensors pointed at the Entity Sensor MIB.
  6. Key advantage: Allows granular per-channel threshold tuning so administrators can trigger warning tickets if a critical WAN fiber circuit loses more than 2 dB of Rx power over a 30-day window.
  7. SolarWinds Network Performance Monitor (NPM)
  8. How it handles Cisco DOM: Polls transceiver health natively through its Hardware Health monitoring engine on supported Catalyst and Nexus platforms, supplemented by Universal Device Pollers (UnDP) for custom MIB tables.
  9. Key advantage: Correlates optical dBm drops directly alongside interface CRC/input error rate spikes on a single timeline view.
  10. Zabbix
  11. How it handles Cisco DOM: Includes official Cisco IOS and NX-OS SNMP templates equipped with Low-Level Discovery (LLD) rules that automatically enumerate DOM-capable transceivers.
  12. Key advantage: Highly scalable and open-source; dynamically creates items and triggers for newly inserted SFP+ modules without manual reconfiguration.
  13. Checkmk
  14. How it handles Cisco DOM: Features dedicated built-in check plugins (cisco_temperature_dom and optical power sensor checks) that parse entity sensor states during routine SNMP walks.
  15. Key advantage: Extremely low polling overhead for large campus or data center deployments with thousands of active fiber ports, automatically flagging any port that crosses its hardware warning flag.

Deploying automated SNMP polling alongside periodic CLI audits gives you full visibility into your Cisco fiber infrastructure—allowing you to spot degrading patch cords, failing lasers, and dirty patch panels long before they cause an outage.

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

Author

Comments

Write a Reply or Comment

Your email address will not be published.