Why Your ONT Loses WAN Settings After a Power Outage

An ONT reverting its WAN configuration to factory defaults after a power outage is typically caused by failed non-volatile storage (NVRAM/flash), a corrupted firmware save routine, unstable power delivery, or a defective backup battery in carrier-grade units. This technical FAQ addresses both pre-sales questions—such as optical module compatibility, maximum throughput, and backplane capacity—and post-sales troubleshooting for basic CLI configuration, stacking interfaces, and redundant power failover. Each answer is structured for quick reference by network architects and field engineers.

Frequently Asked Questions

Q1: Why does my ONT reset its WAN settings back to default after a power outage?

The most common cause is that the ONT's configuration was never committed to non-volatile memory, so the power loss wipes the running config held in volatile RAM. Secondary causes include flash/NVRAM wear-out from excessive write cycles, a firmware bug that skips the save-on-shutdown routine, brownout conditions triggering an incomplete write, and a depleted supercapacitor or battery that fails to hold the config through the outage. Fix: issue an explicit save command, verify write protection, and replace hardware if flash sectors are bad.

Q2: Which optical transceivers and SFP modules are compatible with the ONT's WAN uplink port?

Compatibility depends on the port's MSA compliance—standard SFP/SFP+ slots accept 1000BASE-LX/EX and 10GBASE-LR/ER modules that conform to IEEE 802.3 and SFF-8472 DDM specifications. Always verify the ONT's published wavelength, reach, and connector type (typically SC/LC), and confirm whether the port is locked to vendor-coded EEPROMs; many carrier-grade ONTs accept third-party modules if the firmware allows uncoded optics.

Q3: What is the maximum WAN throughput in Gbps that the ONT can forward?

Typical enterprise ONTs support 1 Gbps to 10 Gbps line-rate WAN forwarding, with higher-end models reaching 10/25 Gbps on the uplink. Confirm the model's datasheet for bidirectional throughput and whether it is symmetric, since asymmetric PON profiles and CPU-bound NAT can bottleneck below the advertised line rate.

Q4: What backplane and switching capacity should I budget for a multi-service ONT deployment?

Size the backplane above the sum of all uplink and subscriber-facing ports to guarantee non-blocking forwarding—for example, a 10 Gbps WAN uplink with 8×1 Gbps LAN ports requires at least 18 Gbps of switching capacity. Add 30–50% headroom for multicast, QoS queuing, and future service growth.

Q5: How does this ONT generation differ from the previous generation in WAN configuration persistence?

Newer generations add dual-image firmware banks, atomic config commits, and supercapacitor-backed config retention, which prevent the post-outage default reset seen on older units. They also support remote zero-touch provisioning to restore WAN profiles automatically after power recovery.

Q6: What basic CLI commands should I use to verify and persist WAN settings on the ONT?

Use the equivalent of show running-config versus show startup-config to compare active and saved WAN profiles, then issue write memory or copy running-config startup-config to persist. Always confirm the save succeeded with a checksum or reload test before declaring the fix complete.

Q7: How do I troubleshoot stacking interfaces and redundant power failover on the ONT or its aggregation switch?

Check stack port link status and cabling first, then verify the stack priority and firmware match across members; for power failover, confirm both PSUs report healthy, test each feed independently, and review logs for brownout events that correlate with config loss. Replace any PSU that fails under load or shows unstable output voltage.

Q8: How can I prevent WAN configuration loss after future power outages?

Deploy a UPS or line conditioner, enable automatic config backup to a remote server, schedule periodic startup-config verification, and upgrade to firmware with atomic save support. For carrier deployments, enable ZTP so the WAN profile is re-provisioned automatically on boot.