<\/p>\n
<\/p>\n
Before You Begin: The QSFP28 Troubleshooting Toolkit<\/strong><\/h2>\nWhat You Need to Check a QSFP28 Module<\/a><\/strong><\/h3>\nGood troubleshooting starts with the right tools. Keep these items accessible in your data center or network operations center:<\/p>\n
\n- \u2022<\/span>Fiber inspection microscope or probe<\/strong>\u2014 to check connector end-face quality<\/li>\n
- \u2022<\/span>Optical power meter<\/strong>\u2014 to measure actual Tx and Rx power levels<\/li>\n
- \u2022<\/span>Light source or loopback module<\/strong>\u2014 to isolate cable vs module failures<\/li>\n
- \u2022<\/span>Lint-free wipes and IPA cleaning fluid<\/strong>\u2014 for connector cleaning<\/li>\n
- \u2022<\/span>Switch CLI access<\/strong>\u2014 to read DDM values, error counters, and port status<\/li>\n<\/ul>\n
<\/p>\n
Most QSFP28 troubleshooting cases are resolved with one or two of these tools. The key is working through diagnostics in the correct order so that you do not chase symptoms instead of root causes.<\/p>\n
<\/p>\n
Understanding DDM and Alarm Thresholds<\/strong><\/h3>\nThe DDM function is your best help in addressing any unwanted behavior in a QSFP28 module. It provides real-time values such as temperature, supply voltage, Tx bias current, Tx optical power, and Rx optical power, and triggers alarms when parameters exceed defined thresholds.<\/p>\n
Understanding DDM thresholds helps determine whether the issue is related to the module itself, dirty connectors, fiber link problems, or switch thermal conditions. The following sections introduce specific alarm scenarios.<\/p>\n
<\/p>\n
<\/p>\n
Problem 1: QSFP28 Module Not Detected<\/strong><\/h2>\nPhysical Seating and Connector Checks<\/b><\/strong><\/h3>\nIf the switch says that the transceiver is not present, you must start with the physical layer. Power is not required for QSFP28 modules for power down, but partially seating will prevent electrical connectivity.<\/p>\n
Remove the module and inspect for debris, bent pins, or damage in the connector or cage. Reinsert it firmly until you hear a click. If the issue persists, try a different port or a known-good module. This simple swap helps isolate whether the issue is with the module, port, or switch.<\/p>\n
<\/p>\n
Switch CLI Verification (Cisco, Arista, Juniper)<\/strong><\/h3>\nEach platform has a standard command to list inserted transceivers.<\/p>\n
Cisco Nexus:<\/strong><\/p>\nshow interface ethernet 1\/1 transceiver<\/p>\n
Arista EOS:<\/strong><\/p>\nshow interfaces transceiver<\/p>\n
Juniper JunOS:<\/strong><\/p>\nshow chassis hardware<\/p>\n
If the CLI shows “Not present” or “Empty” after reseating, the switch is not reading the module EEPROM. Move to the next step.<\/p>\n
<\/p>\n
EEPROM and Vendor Compatibility Issues<\/strong><\/h3>\nQSFP28 modules store identification data in an EEPROM chip. The switch reads this data upon insertion to verify compatibility. If the EEPROM is unreadable, or if the switch vendor enforces a whitelist, the module may be physically present but logically undetected.<\/p>\n
On some Cisco platforms, third-party modules require the hidden command:<\/p>\n
service unsupported-transceiver<\/p>\n
On Arista, most third-party modules are accepted, though certain firmware versions may flag unknown vendors. On Juniper, refer to the official compatibility matrix.<\/p>\n
If you are deploying third-party modules and encounter detection issues across multiple switches, contact our engineers to verify EEPROM encoding and compatibility.<\/p>\n
<\/p>\n
<\/p>\n
Problem 3: QSFP28 Link Flapping or Intermittent Connectivity<\/strong><\/h2>\nIdentifying Cable and Connector Problems<\/strong><\/h3>\nTwo most mortifying moments when QSFP28\u00a0troubleshooting can seem to be totally justified by link flapping. The link goes up, passes traffic and then goes down without warning. Mostly, the root cause is marginal connection \u2013 it may physically look good but fail under vibration, temperature, or traffic load.<\/p>\n
Have a look at the fiber connectors under a microscope. Look to see scratches, pits, chips, or contamination. It is amazing how many times something so small can cause enough reflection or loss to upset a 25G NRZ lane.<\/p>\n
Be very observant of the bend radius. One single tight bend with 30 mm radius (on single mode fiber) can give an additional 0.5 dB or more in loss. That may be enough to bring the flapping on a long-reach link from stable.<\/p>\n
<\/p>\n
![\"QSFP28](\"https:\/\/ascentoptics.com\/blog\/wp-content\/uploads\/2026\/04\/QSFP28\u63a5\u53e3.png\")
<\/p>\n
<\/p>\n
FEC and Signal Integrity Issues<\/strong><\/h3>\nWe find that in some DAC cables or worse than marginal fiber technology cases, the link needs the forward error correction (FEC) to obtain stability. In case the bit error rate goes near the FEC threshold, the link comes up and down as the receiver reaches for a threshold lock.<\/p>\n
Check switch error counters for pre-FEC or post-FEC errors; a rising number of pre-FEC errors is generally indicative of a physic ally layer problem, while post-FEC error rise indicates link is working on the edge of operability and is in need of cable or module replacement.<\/p>\n
<\/p>\n
Autonegotiation and Speed Mismatches<\/strong><\/h3>\nTypically, QSFP28 connections do not autonegotiate speeds. One end must be manually setup for 100G, and the other end should also be manually configured to 100G. If the ends are set to 100G and 40G or 100G and auto, please note that in this case, the link might flap continuously or stay down. Verify configuration on both ends of the links before blaming the QT.<\/p>\n
<\/p>\n
<\/p>\n
Problem 4: QSFP28 High Temperature Alarms<\/strong><\/h2>\nNormal Operating Ranges by Module Type<\/b><\/strong><\/h3>\nDDM temperature alarms are common in high-density switches. Before reacting, know what normal looks like. Commercial-grade QSFP28 modules are typically rated for 0\u00b0C to 70\u00b0C case temperature.<\/p>\n
<\/p>\n
Good troubleshooting starts with the right tools. Keep these items accessible in your data center or network operations center:<\/p>\n
- \n
- \u2022<\/span>Fiber inspection microscope or probe<\/strong>\u2014 to check connector end-face quality<\/li>\n
- \u2022<\/span>Optical power meter<\/strong>\u2014 to measure actual Tx and Rx power levels<\/li>\n
- \u2022<\/span>Light source or loopback module<\/strong>\u2014 to isolate cable vs module failures<\/li>\n
- \u2022<\/span>Lint-free wipes and IPA cleaning fluid<\/strong>\u2014 for connector cleaning<\/li>\n
- \u2022<\/span>Switch CLI access<\/strong>\u2014 to read DDM values, error counters, and port status<\/li>\n<\/ul>\n
<\/p>\n
Most QSFP28 troubleshooting cases are resolved with one or two of these tools. The key is working through diagnostics in the correct order so that you do not chase symptoms instead of root causes.<\/p>\n
<\/p>\n
Understanding DDM and Alarm Thresholds<\/strong><\/h3>\n
The DDM function is your best help in addressing any unwanted behavior in a QSFP28 module. It provides real-time values such as temperature, supply voltage, Tx bias current, Tx optical power, and Rx optical power, and triggers alarms when parameters exceed defined thresholds.<\/p>\n
Understanding DDM thresholds helps determine whether the issue is related to the module itself, dirty connectors, fiber link problems, or switch thermal conditions. The following sections introduce specific alarm scenarios.<\/p>\n
<\/p>\n
<\/p>\n
Problem 1: QSFP28 Module Not Detected<\/strong><\/h2>\n
Physical Seating and Connector Checks<\/b><\/strong><\/h3>\n
If the switch says that the transceiver is not present, you must start with the physical layer. Power is not required for QSFP28 modules for power down, but partially seating will prevent electrical connectivity.<\/p>\n
Remove the module and inspect for debris, bent pins, or damage in the connector or cage. Reinsert it firmly until you hear a click. If the issue persists, try a different port or a known-good module. This simple swap helps isolate whether the issue is with the module, port, or switch.<\/p>\n
<\/p>\n
Switch CLI Verification (Cisco, Arista, Juniper)<\/strong><\/h3>\n
Each platform has a standard command to list inserted transceivers.<\/p>\n
Cisco Nexus:<\/strong><\/p>\n
show interface ethernet 1\/1 transceiver<\/p>\n
Arista EOS:<\/strong><\/p>\n
show interfaces transceiver<\/p>\n
Juniper JunOS:<\/strong><\/p>\n
show chassis hardware<\/p>\n
If the CLI shows “Not present” or “Empty” after reseating, the switch is not reading the module EEPROM. Move to the next step.<\/p>\n
<\/p>\n
EEPROM and Vendor Compatibility Issues<\/strong><\/h3>\n
QSFP28 modules store identification data in an EEPROM chip. The switch reads this data upon insertion to verify compatibility. If the EEPROM is unreadable, or if the switch vendor enforces a whitelist, the module may be physically present but logically undetected.<\/p>\n
On some Cisco platforms, third-party modules require the hidden command:<\/p>\n
service unsupported-transceiver<\/p>\n
On Arista, most third-party modules are accepted, though certain firmware versions may flag unknown vendors. On Juniper, refer to the official compatibility matrix.<\/p>\n
If you are deploying third-party modules and encounter detection issues across multiple switches, contact our engineers to verify EEPROM encoding and compatibility.<\/p>\n
<\/p>\n
<\/p>\n
Problem 3: QSFP28 Link Flapping or Intermittent Connectivity<\/strong><\/h2>\n
Identifying Cable and Connector Problems<\/strong><\/h3>\n
Two most mortifying moments when QSFP28\u00a0troubleshooting can seem to be totally justified by link flapping. The link goes up, passes traffic and then goes down without warning. Mostly, the root cause is marginal connection \u2013 it may physically look good but fail under vibration, temperature, or traffic load.<\/p>\n
Have a look at the fiber connectors under a microscope. Look to see scratches, pits, chips, or contamination. It is amazing how many times something so small can cause enough reflection or loss to upset a 25G NRZ lane.<\/p>\n
Be very observant of the bend radius. One single tight bend with 30 mm radius (on single mode fiber) can give an additional 0.5 dB or more in loss. That may be enough to bring the flapping on a long-reach link from stable.<\/p>\n
<\/p>\n
<\/p>\n<\/p>\n
FEC and Signal Integrity Issues<\/strong><\/h3>\n
We find that in some DAC cables or worse than marginal fiber technology cases, the link needs the forward error correction (FEC) to obtain stability. In case the bit error rate goes near the FEC threshold, the link comes up and down as the receiver reaches for a threshold lock.<\/p>\n
Check switch error counters for pre-FEC or post-FEC errors; a rising number of pre-FEC errors is generally indicative of a physic ally layer problem, while post-FEC error rise indicates link is working on the edge of operability and is in need of cable or module replacement.<\/p>\n
<\/p>\n
Autonegotiation and Speed Mismatches<\/strong><\/h3>\n
Typically, QSFP28 connections do not autonegotiate speeds. One end must be manually setup for 100G, and the other end should also be manually configured to 100G. If the ends are set to 100G and 40G or 100G and auto, please note that in this case, the link might flap continuously or stay down. Verify configuration on both ends of the links before blaming the QT.<\/p>\n
<\/p>\n
<\/p>\n
Problem 4: QSFP28 High Temperature Alarms<\/strong><\/h2>\n
Normal Operating Ranges by Module Type<\/b><\/strong><\/h3>\n
DDM temperature alarms are common in high-density switches. Before reacting, know what normal looks like. Commercial-grade QSFP28 modules are typically rated for 0\u00b0C to 70\u00b0C case temperature.<\/p>\n
<\/p>\n
- \u2022<\/span>Optical power meter<\/strong>\u2014 to measure actual Tx and Rx power levels<\/li>\n
![\"QSFP28](\"https:\/\/ascentoptics.com\/blog\/wp-content\/uploads\/2026\/04\/Q28-Breakout.png\")
<\/p>\n![\"Reading](\"https:\/\/ascentoptics.com\/blog\/wp-content\/uploads\/2026\/04\/DDM.png\")
<\/p>\n![\"QSFP28](\"https:\/\/ascentoptics.com\/blog\/wp-content\/uploads\/2026\/04\/trobuleshooting.png\")
<\/p>\n