Optical transport and troubleshooting
Optical telemetry: read values against the data sheet
DOM or DDM readings can help explain a link drop or alarm. Their usefulness depends on the module, host and capture time. Retain the values with their units and compare them with the exact part’s documentation.
Identify what the assembly can report
Record the host model and firmware, port, module part number and diagnostic support. An absent or N/A field does not mean zero power or prove that a laser is off.
For multiple optical channels, retain each lane’s identity. Do not treat an aggregate reading as verification of every channel. The cited Juniper documentation distinguishes field availability on EX/QFX platforms.
Compare value, threshold and operating condition
Record TX/RX in the displayed units, plus temperature, voltage and bias current when available. Include high/low warning and alarm thresholds and compare them with the module’s data sheet and conditions.
A warning does not necessarily mean immediate link failure; an alarm does not identify the failed part by itself. Low RX can call for reviewing the remote endpoint and route; abnormal TX directs attention toward the local module or host. Incorrect sensor readings are also possible.
Capture a useful diagnostic sequence
Relate the time, port state, errors or loss of usable signal to readings at both endpoints. A capture showing normal readings after a failure does not necessarily explain what happened during it. Preserve timestamps and time zones in existing logs.
Depending on the readings, continue logging without changes or arrange an optical measurement or compatible replacement during an agreed maintenance window. Keep the thresholds unchanged so alarms remain visible: DOM supports troubleshooting but does not certify link loss.
Information for a link review
| Item | What to record | Purpose |
|---|---|---|
| Identity | Host, firmware, port, module and lane | Choose limits and interpret each reading |
| Measurements | Available TX/RX, units, temperature, voltage and current | Keep the full value, not just status color |
| Context | Time, thresholds, alarms, errors and usable signal | Compare before, during and after the symptom |
Before approaching an optical connection
Do not look into optical ports or fiber ends, even when no light is visible. Inspection, cleaning and measurement require the manufacturer’s tools and procedures. If the assembly is hybrid and also carries power, identify the complete system and arrange work with qualified personnel.
Technical questions
Is there a universal “good” RX value?
No. The valid window depends on the part, application and operating conditions. A value accepted by another module may be unsuitable here.
Does no alarm mean the link has been verified?
No. Review counters, stability and usable signal too. The system may miss a brief variation or lack the required diagnostic support.
Can I subtract two DOM captures to obtain loss?
The difference can be a clue, but conditions, channels and accuracy must be comparable. It does not replace a documented insertion-loss measurement.
Further documentation
- Juniper — show interfaces diagnostics optics — DOM diagnostics on EX/QFX; fields and alarms depend on module support.
- Cisco — Troubleshoot Fiber Links on Catalyst 9000 Series Switches — Module and fiber compatibility and TX/RX interpretation on Catalyst 9000.
- Fluke Networks — 5 Vital Safety Rules for Fiber Optic Cables — Optical safety and suitable tools.
Third-party field experience: useful questions, without specification or safety authority.
- Networking — Optical SFP monitoring and light level warnings — Question about threshold origin and its relationship to errors.