Light Level / dBm Reference
What an optical power reading actually tells you, how to interpret it against the applicable spec, and what to do when it comes back low.
dBm is optical power expressed on a logarithmic scale referenced to one milliwatt. It is an absolute measurement: a single number describing how much light is present at that point.
Values above 0 dBm mean more than a milliwatt; values below 0 dBm mean less. Field readings on access networks are usually negative, so the sign confuses people — −10 dBm is ten times more power than −20 dBm. Closer to zero is stronger.
Optical power (dBm) is a level. Optical loss (dB) is a difference between two levels. Mixing them up is the most common reporting error in the field: "−22" and "22 dB of loss" describe completely different situations.
Power reads at or above the healthy end of the design window for that port and wavelength. Note it and move on.
Power falls inside the engineered window. Compare against the record rather than a remembered number.
Power is below expectation but service may still be up. Treat it as a defect to investigate, not a pass.
Power is far below expectation or absent. Service is typically affected or about to be.
Reference ranges vary by network architecture, optics, ONT/OLT specifications, splitter configuration, wavelength, and carrier engineering standards. Always verify against the applicable network specification.
Receive power at the ONT depends on OLT launch power, splitter ratio and cascade, distance, splice and connector count, and wavelength. Two homes on the same street can have legitimately different expected levels.
No splitter loss, so expected receive power is driven mostly by optic type, distance, and connector/splice count. Windows are usually tighter and easier to predict from the link budget.
Per-channel power, total composite power, amplifier gain and OSNR all matter. A single-channel power meter reading rarely tells the whole story — use the applicable per-channel spec and OSA/OTS data.
Generally reads as a healthy receive level on many access links. It tells you the optical path is broadly intact — it does not tell you the link has margin unless you compare it to the engineered window for that port and wavelength.
These examples are educational reasoning aids, not universal pass/fail thresholds. The only correct threshold is the one in the applicable specification for that network, port, and wavelength.
Unexpectedly Low Power
- 01Verify test setup — right meter, right wavelength, right units, calibrated and zeroed.
- 02Inspect connectors — scope the end faces before you trust any reading.
- 03Clean connectors — dry then wet-dry as appropriate, then re-inspect.
- 04Check patch cords and jumpers — substitute a known-good cord.
- 05Check bends — look for macrobends, tight loops, staples, crush, and pinch points.
- 06Check a known-good port or piece of equipment when it is appropriate and permitted.
- 07Compare expected vs measured — use the record or link budget, not memory.
- 08Escalate toward OTDR testing when the fault is not local and distance matters.
Four Measurements, Four Questions
An absolute reading of how much light is present at a point, in dBm. Answers: how much light is here?
The difference in power caused by inserting a component or span, in dB. Answers: how much light did this path take away?
How much light is reflected back toward the source, in dB. Poor connections and end-face problems commonly show up here first.
Loss attributed to a specific event at a specific distance, derived from backscatter. Useful for locating, but it is an estimate — not a substitute for an end-to-end power or loss test.
Scope before you clean, clean before you blame the plant, and compare against the record before you call anything a failure. Most "low light" calls end at a dirty end face or a bad jumper.
Never eye a live fiber or connector. Treat every fiber as energized until you have confirmed otherwise.
Use this at an ONT, a NID, a cabinet, or a panel when you have a power reading in hand and need to decide whether it's healthy, marginal, or a fault — and what to check next.