Rogue ONT and an OTDR trace taken through a live splitter
A 1:32 GPON port serves 32 ONTs in a new subdivision. After three weeks, 31 ONTs deregister every 30–45 seconds and recover; the OLT logs a rogue ONT alarm and upstream BIP errors on the port. One ONT, at a home where the customer installed a homemade media converter, shows no alarm. The contractor connects an OTDR at 1550 nm at the OLT through the live 1:32 splitter and reports a 3.0 dB event at 2.1 km and no events beyond the splitter. The contractor wants to cut and re-splice the feeder at 2.1 km. The operator cannot take the whole PON down for more than a 30-minute maintenance window, and 31 customers are angry.
1. Interpret the OTDR result. Should the contractor cut the feeder at 2.1 km?
Read the worked answer
No. The trace was taken through a live 1:32 splitter. The splitter presents an approximately 17 dB event, and the OTDR cannot reliably see beyond it because of splitter directivity, multiple reflections, and reduced dynamic range. A 3.0 dB event on the feeder would also affect all 32 ONTs consistently, including the one with the homemade converter, rather than producing the observed pattern of 31 ONTs dropping and recovering while one stays up.
The event at 2.1 km may be a real splice, a ghost reflection, or a splitter artifact. Cutting the feeder based on this trace would interrupt all 32 customers and might not fix the fault. The symptom - upstream BIP errors and a rogue ONT alarm - points to an ONT transmitting outside its assigned burst window, not to a 3 dB feeder loss. Use an out-of-band PON OTDR at 1650 nm from the FDT, or test individual drops from the ONT end with a launch fiber. Do not cut.
2. Describe a plan to isolate the rogue ONT within a 30-minute maintenance window.
Read the worked answer
Use management first, not fiber cuts. From the OLT, disable ONTs in binary groups - 16, then 8, then 4 - and watch whether the rogue alarm clears. This narrows the suspect quickly without disturbing every customer. The ONT at the home with the homemade media converter is the prime suspect, but do not assume it is the only one; a failing laser can also transmit continuously.
If management cannot disable individual ONTs, use a PON power meter or upstream power monitoring at the OLT to identify a continuously transmitting source. At the FAT, disconnect the suspect drop and observe the alarm. Replace the suspect ONT and remove the unauthorized media converter. During the window, keep the rest of the port in service as much as possible, and notify affected customers. After the change, confirm that all 32 ONTs register and that the rogue alarm does not return.
3. What acceptance checks would you require after the rogue ONT is removed?
Read the worked answer
Verify that all 32 ONTs are registered and that each receive level at 1490 nm is within the design range. Check upstream RSSI at the OLT for each ONT and confirm that no ONT is transmitting outside its burst. Clear the error counters, then monitor the port for at least 24 hours for BIP errors, deregistrations, and rogue alarms.
Run an OLTS loss measurement on the repaired drop against the design value, and inspect the connector endfaces and bend radius at the customer premises. Remove the unauthorized media converter and document the configuration. Record the suspect ONT serial number, the action taken, and the 24-hour error results. Acceptance should be based on stable service and clean counters, not merely on the ONT coming back online.