Overview

When a third-party ONU drops connection every time the OLT reboots, the root cause is almost always an authentication, registration, or configuration-persistence mismatch between the ONU and the OLT. This FAQ answers the highest-intent pre-sales and post-sales questions that network architects, integrators, and procurement teams ask about third-party ONU interoperability, optical module compatibility, CLI configuration, stacking, redundant power failover, and L3 protocol behavior. Each answer is written in a direct, featured-snippet-ready format so you can quickly diagnose and resolve OLT-reboot-related link drops in carrier, datacenter, and enterprise edge deployments.

Frequently Asked Questions

Q1: Why does my third-party ONU drop connection every time the OLT reboots?

The most common reason is that the third-party ONU is not properly re-authenticated or re-registered after the OLT restarts, because the OLT does not persist the ONU's serial number, password, or logical link ID across reboots. In GPON and XGS-PON environments, the OLT must retain ONU registration data in non-volatile storage or an external AAA/RADIUS server; if it does not, every reboot triggers a full discovery cycle and the third-party ONU is left in an unregistered state. Secondary causes include mismatched OMCI firmware versions, missing VLAN or service profile bindings, and the ONU defaulting to a different management VLAN after power loss.

Q2: What optical module compatibility rules must a third-party ONU follow to survive an OLT reboot?

A third-party ONU must use an optical module that matches the OLT's PON type, wavelength plan, and transmit power budget exactly, or it will fail re-ranging after the OLT reboots. For GPON, the ONU must support 1310 nm upstream and 1490 nm downstream with a minimum 28 dB budget; for XGS-PON, 1270 nm upstream and 1577 nm downstream with 29 dB budget. The module must also support the OLT's DDM/DOM thresholds, burst-mode transmission, and the correct OMCI or TR-069 management channel. If the optical module is not on the OLT vendor's approved list, the OLT may reject it during the post-reboot ranging window even if it worked before.

Q3: What is the maximum throughput and backplane capacity I should expect from a third-party ONU?

A compliant third-party ONU should deliver line-rate 2.5 Gbps downstream and 1.25 Gbps upstream for GPON, or 10 Gbps symmetric for XGS-PON, with a backplane capacity of at least 20 Gbps to avoid internal bottlenecks. The backplane capacity must exceed the PON line rate plus management and multicast overhead; otherwise, buffering delays can cause the ONU to miss the OLT's registration window after a reboot. Confirm the ONU datasheet lists non-blocking forwarding, jumbo frame support up to 9216 bytes, and a packet buffer of at least 1 MB for stable re-registration under load.

Q4: How do I configure basic CLI settings on a third-party ONU to prevent reboot drops?

You must configure persistent registration and save the running configuration to non-volatile memory before the OLT reboots. Use the CLI to set the ONU serial number, registration ID, and management VLAN, then issue the write memory or copy running-config startup-config command. For OMCI-managed ONUs, enable omci auto-reconnect and set the OLT discovery timeout to at least 30 seconds. For TR-069 ONUs, configure the ACS URL and periodic inform interval so the ONU re-establishes management after the OLT restarts. Always verify with show ont registration and show ont optical-info after a simulated reboot.

Q5: What stacking interfaces and virtual chassis options help maintain uptime when the OLT reboots?

Stacking interfaces such as 10G SFP+ or 25G SFP28 ports can keep the ONU management path alive if one OLT member reboots, provided the stack uses a ring or dual-homed topology. In a virtual chassis, the ONU should be dual-homed to two stack members with LACP or MC-LAG so that a single OLT reboot does not isolate the ONU. Configure stacking priority and stacking failover so the surviving member retains the ONU's MAC and OMCI session. Avoid daisy-chain stacking for ONU uplinks because a single rebooted member can break the entire chain and force a full re-registration.

Q6: How does redundant power failover affect third-party ONU reconnection after an OLT reboot?

Redundant AC/DC power supplies on the OLT prevent the reboot from happening in the first place, but if a reboot still occurs, the ONU must have its own dual-power or hold-up capacitor to survive the OLT's power cycle. A third-party ONU with only a single power feed will lose its OMCI session and may take 60-180 seconds to re-range, during which traffic drops. For carrier-grade uptime, use an ONU with dual DC inputs, a minimum 10 ms hold-up time, and a power failover circuit that keeps the PON MAC alive. Verify the OLT's power failover threshold and the ONU's brownout detection are aligned to avoid false resets.

Q7: Which L3 protocols and multicast handling features reduce ONU drops during OLT reboot?

OSPF, BGP, and VRRP help the ONU maintain L3 reachability if the OLT reboots, but only if the ONU supports graceful restart and bidirectional forwarding detection (BFD). Enable ospf graceful-restart and bfd echo so the ONU does not tear down routes when the OLT control plane restarts. For multicast, enable IGMP snooping with immediate leave and a querier timeout longer than the OLT reboot window. VRRP with a preempt delay of at least 120 seconds prevents the ONU from becoming master prematurely and flapping the uplink. Confirm the ONU supports at least 4K multicast groups and 1K ARP entries for stable post-reboot convergence.

Q8: How do I migrate from a legacy ONU to a third-party ONU without reboot-induced downtime?

To migrate without downtime, pre-stage the third-party ONU on a maintenance VLAN, copy the legacy ONU's serial number and service profiles to the OLT's persistent database, and then cut over during a scheduled window. Use the OLT's ont replace or ont migrate command so the new ONU inherits the old registration ID and OMCI configuration. Verify the third-party ONU's optical module is on the approved list and that its firmware version matches the OLT's OMCI baseline. After cutover, simulate an OLT reboot and confirm the ONU re-registers within 30 seconds; if it does not, check the OLT's persistent storage and AAA server logs for authentication mismatches.