When a 100 Gbps SR4 link exhibits intermittent loss, the first step is to confirm whether the link is native 100G or a 4×25 G breakout. Native SR4 uses a single MPO‑12 connector with four lanes bundled, while a breakout typically presents four separate SFP‑28 ports on the host side. Checking the transceiver model number (e.g., Cisco QSFP‑SR4‑L or Mellanox MT_100G_SR4) and the host NIC configuration can eliminate ambiguity.

Next, verify MPO Type B polarity. A mismatched polarity causes one or more lanes to report out‑of‑spec Rx power. The transceiver datasheet lists the expected polarity mapping; a quick visual inspection of the keying on the MPO connector (flat vs. key) can confirm correct orientation. If the host supports it, enable per‑lane diagnostics (e.g., "show interface transceiver detail" on Cisco or "ethtool -m" on Linux) to read the DOM Rx power for each lane.

Typical per‑lane Rx power for a healthy SR4 link is between –8 dBm and –2 dBm. Values outside this window often indicate fiber macro‑bends, dirty connectors, or a faulty MPO block. Use an optical power meter to compare the DOM reading with an independent measurement; a discrepancy greater than 1 dB suggests a measurement path issue.

Finally, run a lane‑by‑lane eye‑diagram capture if the NIC supports it. A widened eye or high jitter on a specific lane points to a physical defect rather than a MAC‑level problem. After confirming the physical layer, proceed to check flow control settings and any QoS shaping that might be throttling traffic.

What diagnostic tool or command have you found most reliable for isolating a single‑lane fault on a 100 Gbps SR4 link?