Troubleshoot an ONU from Evidence, Not One Signal Number
A field workflow for separating optical loss, registration, Ethernet, power and service-policy faults before dispatching a technician.
A field workflow for separating optical loss, registration, Ethernet, power and service-policy faults before dispatching a technician.
First locate the failing layer
“ONU offline” describes an outcome, not a cause. The fault may be absent power, broken fiber, failed registration, a disabled PON object, an Ethernet problem or a subscriber service policy. A useful workflow eliminates layers in order and records evidence before changing configuration.
| Layer | Evidence | Typical next check |
|---|---|---|
| Power | LED state, adapter output, reboot history | Outlet, adapter rating, UPS and connector fit |
| Optical | OLT/ONU receive level, LOS history | Patch lead, connector, splitter path and bend |
| Registration | Serial/LOID state and last-down reason | Provisioning identity and PON authorization |
| Ethernet | UNI link, errors, negotiated rate | Cable, customer router WAN and port profile |
| Service | VLAN, PPPoE/DHCP and RADIUS evidence | End-to-end forwarding and entitlement |
Read optical values as a path
One receive-power value cannot explain the path. Compare the ONU’s downstream receive level with the OLT’s upstream receive level, the design budget and the device class. Directional differences can point to a dirty connector, failing transmitter or measurement variation.
Trend the value. A subscriber at a stable lower level may be less urgent than one that moved several decibels after construction work. Store measurement time, OLT, PON, ONU identity and firmware so comparisons remain meaningful.
Use the last-down reason carefully
Loss of signal, dying gasp, deactivation and ranging failure imply different paths, but vendor labels are not perfectly consistent. Dying gasp usually indicates loss of ONU power; it does not prove the fiber is healthy. LOS indicates optical reception failure; it does not identify which connector or span failed.
- Confirm identity. Match serial/LOID, customer and physical splitter path.
- Check correlated alarms. Determine whether one ONU, a branch or the full PON is affected.
- Compare both optical directions. Record current and previous known-good values.
- Check registration and service objects. Avoid cleaning fiber for a disabled configuration.
- Dispatch with a hypothesis. Give the technician path, evidence and required tools.
Correlate the fault radius
Several ONUs failing together provide topology information. All ONUs on a PON suggest OLT port, feeder or upstream power. A subset sharing one splitter suggests distribution fiber or splitter failure. One ONU suggests drop fiber, connector, power or device.
Single endpoint
Compare power history, drop route, adapter and UNI state.
Shared branch
Group affected ONUs by splitter and distribution segment.
Whole PON
Check port state, uplink impact, feeder and OLT alarms.
Intermittent set
Look for temperature, movement, contamination or marginal budget.
Inspect and clean without causing new damage
Follow fiber safety and inspection procedures. Never look into a connector. Inspect before cleaning, use approved tools for the connector type, and inspect again. Avoid repeated unplugging across live customers without documenting the path and expected interruption.
An optical power meter confirms loss at a point; an OTDR can help locate reflective or loss events when used by trained staff with correct launch/receive setup. Neither replaces accurate splice and splitter records.
Verify customer service after optical recovery
Registration is not the final test. Confirm the correct ONU profile, VLAN translation, UNI state and subscriber authentication. Then test DNS and representative traffic. Close the incident with before/after optical values, repair location, materials and the technician’s identity.
- Signal recovered within the engineered budget.
- ONU identity matches the intended customer.
- UNI negotiates the expected speed without rising errors.
- Subscriber receives the correct service policy.
- Branch topology and repair records are updated.
Research basis: GPON concepts from the ITU-T G.984 family, EPON concepts from IEEE 802.3ah, and vendor-specific optical class/alarm documentation. Always use approved laser-safety and fiber-inspection procedures.