L
Member
When troubleshooting a 100 GbE SR4 link, the first step is to confirm whether the interface is a native 100 GbE (four lanes of 25 Gbps on a single MPO) or a 4×25 GbE breakout (four independent 25 Gbps ports sharing the same MPO). The port description in the switch OS (e.g., "speed 100g" vs "speed 25g" on sub‑interfaces) usually indicates the mode. If a breakout is intended, verify that the transceiver configuration matches the expected logical mapping (e.g., "breakout mode 4x25g" on the host side).
Next, inspect the MPO connector type. SR4 modules typically use MPO‑12 with Type B polarity. A mismatch (Type A vs Type B) will cause lane‑to‑lane inversion and result in low or zero Rx power. Physical inspection of the connector keying and, if available, a label on the transceiver can confirm the polarity.
After confirming polarity, collect per‑lane diagnostics via the Digital Optical Monitoring (DOM) interface. Typical Rx power for a clean SR4 link is –8 dBm to –4 dBm per lane; values below –12 dBm often indicate a bad fiber, dirty connector, or faulty transceiver. Check Tx power as well; a large Tx/Rx imbalance (> 6 dB) suggests a possible attenuation issue.
Finally, run a lane‑by‑lane error counter reset and monitor for CRC or alignment errors. Persistent errors on a single lane while others are clean point to a specific fiber pair or transceiver defect.
What diagnostic tool or script do you use to automate per‑lane DOM collection and error‑counter resets for SR4 links in your environment?
Next, inspect the MPO connector type. SR4 modules typically use MPO‑12 with Type B polarity. A mismatch (Type A vs Type B) will cause lane‑to‑lane inversion and result in low or zero Rx power. Physical inspection of the connector keying and, if available, a label on the transceiver can confirm the polarity.
After confirming polarity, collect per‑lane diagnostics via the Digital Optical Monitoring (DOM) interface. Typical Rx power for a clean SR4 link is –8 dBm to –4 dBm per lane; values below –12 dBm often indicate a bad fiber, dirty connector, or faulty transceiver. Check Tx power as well; a large Tx/Rx imbalance (> 6 dB) suggests a possible attenuation issue.
Finally, run a lane‑by‑lane error counter reset and monitor for CRC or alignment errors. Persistent errors on a single lane while others are clean point to a specific fiber pair or transceiver defect.
What diagnostic tool or script do you use to automate per‑lane DOM collection and error‑counter resets for SR4 links in your environment?

