Overview

In GPON and XGS-PON access networks, an ONT failing to save WAN configuration changes pushed by the OLT is a high-impact B2B support issue. It typically points to OMCI persistence failures, write-protected config partitions, mismatched MIB profiles, or a software image that cannot commit the received service model to non-volatile memory. This FAQ answers the most common pre-sales and post-sales questions network architects, integrators and telecom operators ask when diagnosing ONT WAN provisioning save failures and validating hardware readiness for carrier-grade multi-service access.

Frequently Asked Questions

Q1: Why does my ONT fail to save WAN configuration changes pushed by the OLT?

The primary reason an ONT fails to save OLT-pushed WAN configuration is that the OMCI MIB upload/commit sequence is rejected or rolled back before the configuration is written to non-volatile flash. Typical root causes include an OMCI MIB mismatch between OLT and ONT firmware versions, insufficient configuration partition space, a write-protected or corrupted config file, an unaccepted T-CONT or GEM port mapping, or the ONT rebooting before the commit timer expires. Verify OMCI alarm codes, compare software images on both ends, and confirm the ONT reports a successful MIB upload before re-pushing the WAN profile.

Q2: What is the maximum switching throughput and backplane capacity of carrier-grade ONT/OLT access platforms?

Enterprise and carrier access platforms typically deliver 1 Gbps to 10 Gbps per PON port with an aggregate backplane capacity of 100 Gbps to 1.6 Tbps depending on chassis class. Line-rate forwarding performance generally scales from 10 Mpps to over 400 Mpps, with XGS-PON ONTs supporting symmetrical 10 Gbps and NG-PON2 platforms scaling to 40 Gbps per wavelength. Always confirm the listed switching capacity, packet forwarding rate and buffer depth against the actual access topology before procurement.

Q3: Which optical modules and transceiver form factors are compatible with ONT and OLT uplink ports?

Compatibility depends on the uplink interface, but most carrier access platforms support SFP, SFP+, SFP28, QSFP+ and QSFP28 modules with BIDI, CWDM and DWDM options. For GPON/XGS-PON access, the ONT uses a fixed or pluggable PON transceiver in Class B+, C+ or C++ optical budget variants. Third-party transceivers are generally supported when they match the vendor's MSA, EEPROM coding and digital diagnostic monitoring requirements. Confirm wavelength, reach, optical budget and temperature range before deployment.

Q4: How do I perform basic CLI configuration and verify WAN provisioning on an ONT or OLT?

Basic CLI verification starts with connecting via console, SSH or Telnet, then entering privileged mode and running show commands to inspect the WAN, OMCI and interface status. Typical commands include show wan status, show omci mib, show interface gpon, and show running-config to confirm the pushed profile is present. If the WAN entry appears but does not persist, check show flash or show config-files to confirm the commit succeeded. Always save the running configuration to startup configuration after validation.

Q5: How does stacking or virtual chassis work on access and aggregation switches, and what causes stacking errors?

Stacking or virtual chassis technology logically merges multiple physical switches into one management domain, simplifying CLI configuration and improving high availability. Common stacking errors are caused by mismatched firmware versions, incorrect stacking cable topology, duplicate unit IDs, insufficient stack bandwidth, or a broken ring that forces a split-brain condition. Verify stack port status, unit numbering and priority settings, then confirm the stack master election before troubleshooting uplink or WAN-related symptoms.

Q6: How does redundant power supply failover work, and how do I troubleshoot a PSU that does not take over?

Redundant AC/DC power supplies provide hardware-level failover by sharing load and automatically switching to the secondary unit when the primary fails. If failover does not occur, check PSU seating, input voltage, fuse or breaker status, and whether the PSU is detected in the CLI or management GUI. Also verify that the power budget supports the full configuration, since an underrated PSU may cause the system to shut down rather than switch over cleanly. Confirm alarm logs for power supply fault events.

Q7: What are the main differences between this generation of access hardware and previous generations?

Current-generation access platforms typically improve upon previous generations with higher per-port bandwidth, deeper packet buffers, better thermal efficiency, and support for 10G/40G/100G uplinks. They also add advanced features such as network slicing, enhanced QoS, MACsec, and more granular OMCI handling. Migration is generally smoother when firmware, OMCI profiles, and management systems are aligned across both generations before cutover.

Q8: How can I recover an ONT that keeps rejecting OLT-pushed WAN configuration changes?

Recovery begins with factory-resetting the ONT, upgrading or downgrading the firmware to match the OLT, and re-registering the device on the PON. Then re-push a minimal WAN profile, verify MIB upload success, and only after that add VLAN, QoS and service mappings incrementally. If the failure persists, replace the ONT or move it to a different PON port to rule out optical or OLT-side profile corruption. Capture OMCI traces and vendor logs for escalation.