FTTH support guide

GPON ONT optical levels: a support guide

Read the light level before booking a fibre visit. Separate ONT receive power from transmit power, check the optical class, and use a five-step phone check to collect useful evidence.

Check TR-069 device coverage
Worked example · manual triage

Read the direction first

example ONT Rx
−25 dBm
example ONT Tx
+2 dBm
assumed class
B+
Rx2 dB above assumed sensitivityMarginal
TxWithin reference launch rangeCheck upstream Rx
NextRecord trend and LOS stateEscalate evidence
Teaching example, not a product screen. An ISPAgents optics verdict is planned; these bands are manual support guidance.
Page type
Guides
Primary search
GPON ONT optical levels
Updated
2026-10-16

Rx and Tx: which end is measuring?

ONT Rx is light arriving at the customer's optical network terminal from the operator's optical line terminal (OLT). ONT Tx is light leaving that ONT towards the OLT. The OLT also has its own Tx reading and a separate upstream Rx reading for each ONT. Never compare an OLT Rx value with an ONT Rx threshold.

Downstream: OLT Tx → feeder → splitter → drop fibre → ONT Rx
Upstream:   OLT Rx ← feeder ← splitter ← drop fibre ← ONT Tx

Power is reported in dBm; loss or a change in power is expressed in dB. A more negative dBm number is weaker: −25 dBm is weaker than −20 dBm. A positive Tx value is not a fault by itself. Record the sign, unit, direction and timestamp alongside every reading.

This is a manual support workflow for conventional GPON. It is not an XGS-PON threshold sheet or a replacement for the matched OLT/ONT datasheets. For remote parameter access, start with TR-069 CPE coverage.

Typical B+ and C+ reference limits

For 2.488 Gbit/s downstream / 1.244 Gbit/s upstream GPON, the reference values below come from ITU-T G.984.2 (08/2019), Table A.1 (B+) and Table V.1 (single-sided extended C+). These are interface limits, not universal service-health bands.

MeasurementClass B+Class C+ reference
ONT Rx: sensitivity to overload−27 to −8 dBm−30 to −8 dBm
ONT Tx: mean launch power+0.5 to +5 dBm+0.5 to +5 dBm
OLT Rx: sensitivity to overload−28 to −8 dBm−32 to −12 dBm
OLT Tx: mean launch power+1.5 to +5 dBm+3 to +7 dBm

The C+ sensitivity values assume the specified forward error correction (FEC). A C+ OLT label alone does not establish that a particular ONT can use the −30 dBm limit. Confirm the receiver specification and active configuration. See the ITU-T source, Annex A and Appendix V.

Use equipment-specific limits if they differ. Do not increase launch power or change optics during a support call to make a reading fit this table.

Good, marginal or bad: an explicit triage assumption

For this guide only, assume an ONT receiver with the limits above, a fresh correctly scaled reading, and the required FEC configuration. We reserve 3 dB above sensitivity and 2 dB below overload for the good band. Those margins are editorial support assumptions, not ITU pass/fail requirements or guaranteed engineering reserve. Measurement error can consume the margin; use a suitable calibrated power meter when readings are disputed.

The following bands apply to ONT Rx only, including the exact boundaries shown. Unknown class, missing data or stale data means unknown, never good.

Support bandB+ ONT RxC+ ONT Rx, with stated FEC assumptionNext action
Good by this rule−24 through −10 dBm, inclusive−27 through −10 dBm, inclusiveCompare with installation baseline; continue checking service symptoms.
Marginal, weak side−27 inclusive to below −24 dBm−30 inclusive to below −27 dBmRecord trend and alarms; ask the NOC to review path loss.
Marginal, strong sideAbove −10 through −8 dBm, inclusiveAbove −10 through −8 dBm, inclusiveCheck optical class and designed minimum loss with the NOC.
Bad, outside reference windowBelow −27 or above −8 dBmBelow −30 or above −8 dBmEscalate for measurement and plant/optics checks.

“Bad” means outside the assumed window; it does not identify a failed part. “Good” does not rule out intermittent loss, upstream faults, congestion, Wi-Fi issues or service configuration errors. Loss-of-signal (LOS) alarms and service interruptions still warrant investigation at any reported level.

Example: an ONT reporting −25 dBm Rx and +2 dBm Tx on a confirmed B+ link is marginal on the weak side under this rule. Its launch reading is within the reference range, but that does not prove the OLT receives the upstream signal correctly. Record both ends before suggesting a replacement.

There is no separate universal good/marginal/bad Tx ladder here. Compare Tx with the exact transceiver specification and any power-control state; an unexpected value needs verification, not an automatic “dirty fibre” diagnosis.

What the bands suggest checking

ObservationPossible causes to investigateUseful evidence
Good, stable Rx but poor serviceUpstream fault, Ethernet/Wi-Fi problem, provisioning or congestion; optics alone cannot decideWired-device symptoms, OLT per-ONT Rx, registration state and error counters
Marginal weak Rx or a downward trendDirty connector, macrobend from a tightly bent drop cable, splice damage, or more splitter loss than designedInstallation baseline, recent cabling work, affected neighbours and splitter route
Bad weak Rx or LOSDisconnected/damaged fibre, severe connector contamination, unexpected splitter cascade, wrong optical class or a transmitter problemFresh readings at both ends, alarm times and shared-PON impact
Marginal strong or bad strong RxToo little path loss, wrong optics/class, or a patch route that bypasses the intended splitter/attenuationOLT/ONT part numbers and the designed optical path

Splitter loss is normally part of the design. An extra or incorrectly patched splitter is a different finding. A bend or contaminated connector can cause loss, but one power number cannot locate it. Leave connector inspection, cleaning and optical testing to trained staff with the appropriate equipment.

A five-step phone check

  1. Identify the line and symptom. Confirm the subscriber and ONT serial/model in the operator record. Ask when the fault began, whether every device is affected, and whether the ONT has power, PON registration or an LOS indicator. Record the actual LED state; meanings vary by model. Check whether neighbours on the same PON are affected.
  2. Capture fresh readings before changing anything. Use an authorized operator view or ask the customer to read the optical status screen if your support procedure allows it. Record ONT Rx, ONT Tx, units, time and firmware. Request the OLT's per-ONT Rx and alarms from the NOC. Mark missing/stale values unknown; do not turn zero, blank or a sentinel value into a pass.
  3. Check the right limits. Confirm GPON and the matched optics/class with the NOC. Normalize units, compare ONT Rx against the actual receiver limits and installation baseline, then apply a documented support margin. If class or FEC is unknown, keep the verdict unknown and escalate that question.
  4. Ask about visible changes safely. Ask whether furniture moved, a cable was trapped, or the external drop was disturbed. The customer can describe visible routing without unplugging or handling the optical connector. Never ask them to look into a fibre end, open the optical module, clean a connector or reset the ONT. Follow your established power-check procedure only after preserving evidence.
  5. Choose and record the handoff. Send LOS, out-of-window levels, deteriorating readings or repeated drops to the NOC/field team with serial, timestamps, both directions, baseline and affected-neighbour scope. For stable in-band readings, continue wired Ethernet, Wi-Fi and service checks. Explain the next action to the caller; do not promise that a reboot or ONT replacement will fix a fibre fault.

Reading optical parameters through an ACS

Under Device.Optical.Interface.{i}., the TR-181 model defines OpticalSignalLevel for downstream receive power and TransmitOpticalLevel for mean launch power. Both use dBm/1000 (Dbm1000): divide the raw value by 1000 to obtain dBm. For example, raw −25000 represents −25.000 dBm; a UI may already have converted it. Check the parameter definition and the displayed units before converting, so you do not apply a second conversion. See the Broadband Forum Device:2 data model.

Availability depends on the CPE model and firmware. Huawei and ZTE devices may expose vendor-specific paths instead of, or alongside, Optical.Interface; path names, units and access permissions must be discovered and qualified for that CPE. Do not assume a path found on another model exists on this one. Capture the collection time and whether the value is valid.

Where ISPAgents fits

Available: ISPAgents supports TR-069/CWMP parameter reads and diagnostics. Optical values are usable only where the particular CPE exposes supported parameters; qualify the model and firmware first.

Planned: an ISPAgents optics verdict that classifies ONT readings. The manual bands and worked example in this guide do not show a shipped product verdict or promise automatic fault diagnosis.

Review the TR-069 ACS integration, check device compatibility, or discuss your support workflow with the ONT models you need to qualify.

Frequently asked questions

Is −25 dBm a good ONT receive level?

In this guide's B+ example it is marginal: only 2 dB above the assumed −27 dBm sensitivity. In the C+ example it is within the good band, but only if that receiver and its FEC configuration support the stated −30 dBm limit. Check the model, trend and alarms.

Does positive ONT Tx power mean the fibre is healthy?

No. Tx describes light leaving the ONT. Upstream light can still arrive too weakly at the OLT after path loss. Compare the OLT's per-ONT receive measurement and alarms.

Can every ONT report optical levels through TR-069?

No. Optical parameter availability, units and freshness depend on the CPE model and firmware. A missing value is unknown, not a healthy reading.

Does ISPAgents automatically classify optical readings?

An ISPAgents optics verdict is planned. TR-069 parameter reads are available, but optical parameter coverage must be verified on the particular CPE and firmware.

Next step

Discuss the scope for your network.