PON optical alarm triage
When ONTs report loss-of-signal or unstable optical power, triage the physical ODN before changing service profiles. Confirm patching, connector cleanliness, splitter labels and measured receive levels.
Key facts
- Symptom-first: LOS / low power / intermittent drop
- Do not invent vendor alarm codes here
- Measure before re-provisioning
Audience
NOC and field engineers.
Prerequisites
- Access to ODN records
- Optical power meter
Workflow
- Scope: single ONT vs splitter subtree vs OLT port
- Inspect recent patching changes
- Clean/reseat connectors on the affected path
- Measure Rx at ONT and compare to design window
- Escalate to fiber repair if plant loss is out of budget
Decision table
| Scope | First checks |
|---|---|
| One ONT | Drop fiber, ONT power, local connectors |
| Many ONTs on one splitter | Distribution fiber / that splitter stage |
| Entire OLT PON port | OLT optic/port, feeder, first splitter |
Verification
Stable Rx and cleared symptom for a soak period appropriate to the change window.
Rollback
Restore prior patching if a change introduced the fault; re-measure.
Related guides
- Optical power budget checklist — Task checklist for calculating and validating end-to-end optical budgets.
- XGS-PON design basics — Foundational XGS-PON design inputs, verification, and rollback considerations.
- FTTH access reference architecture — OLT–ODN–ONT access architecture and coexistence considerations.
Owner: Novatelia Engineering / AEO Program. Reviewed: 2026-07-22. Doc version: 2026.07. Change log: Phase 6 technical authority pilot.
No datasheet copies, fabricated benchmarks, or unverified vendor authorizations appear in this document.