Overview

Enabling MTU manual override on an ONT WAN interface requires CLI access to the service personality profile to set a custom byte value, followed by a personality update and OLT-side frame length alignment to prevent packet fragmentation. This technical FAQ addresses the most common pre-sales and post-sales inquiries from network architects deploying business ONTs in high-throughput backhaul and enterprise access scenarios.

Frequently Asked Questions

\n

Q1: How do I enable MTU manual override on an ONT WAN interface via the CLI?

\n

The primary method to enable MTU manual override is to enter the ONT service configuration mode via CLI and issue the set personality mtu command followed by the required byte value, then commit the change with personality update. For example, on compatible platforms, the command sequence is: access the specific ONT MAC context, enter the service view, set the MTU to your target value (typically within a 64–1900 byte range for subscriber terminals), run personality update to make the setting persistent across reboots, and finally verify with personality show to confirm the active MTU value. It is critical to note that modifying MTU on the ONT alone is insufficient; you must also ensure the OLT uplink chip and intermediate switches are configured to forward the larger frame size, otherwise large packets will be discarded.

\n

Q2: What is the maximum supported MTU/Jumbo Frame size on current-generation ONT WAN interfaces?

\n

Maximum supported MTU varies by PON technology and ONT operating mode: GPON OMCI-bridge mode typically supports up to 1950 bytes, while XGS-PON OMCI-bridge mode can support up to 9000 bytes for Jumbo Frame end-to-end delivery. In residential gateway (RG) mode, the WAN MTU is often restricted to 1500 bytes by default but can be extended via ACS to approximately 2000 bytes depending on the model. For B2B deployments requiring 9000-byte Jumbo Frames (such as storage backup or dedicated backhaul), XGS-PON ONTs in bridge mode are the recommended choice, provided the entire path—including the OLT NNI uplink, aggregation switches, and CPE—supports the same frame size.

\n

Q3: Which optical transceiver modules are compatible with the ONT WAN uplink interface for 10G/25G deployments?

\n

ONT WAN uplink optical interfaces generally require standard-compliant SFP+ or SFP28 modules with digital diagnostics monitoring (DDM) and proper temperature hardening for carrier-grade environments. For 10G backhaul, SFP+ 10GBASE-LR (1310nm, 10km) and 10GBASE-ER (1550nm, 40km) modules are the most common choices, while 25G deployments require SFP28 modules matching the specific ONT port capability. Compatibility caveats include: verify that the ONT firmware recognizes the module vendor code (some carrier-locked ONTs restrict third-party optics), confirm the optical budget matches your fiber plant loss, and ensure the module's operating temperature range meets your outdoor cabinet or unconditioned space requirements. Always validate with a show interface transceiver command to confirm Rx power levels fall within the ONT's specified sensitivity range.

\n

Q4: What is the maximum line-rate throughput and backplane capacity of a typical B2B ONT?

\n

The maximum line-rate throughput for an XGS-PON ONT is 9.953 Gbps downstream and 9.953 Gbps upstream symmetrically, with the backplane and internal switching fabric designed to sustain non-blocking forwarding at this rate. For GPON models, the asymmetric rates are 2.488 Gbps downstream and 1.244 Gbps upstream. In practical B2B deployments, the achievable throughput depends on the service configuration: bridge-mode pass-through achieves near-line-rate, while route-mode with NAT/firewall enabled may introduce throughput degradation depending on the CPU and offload capabilities. When specifying for high-capacity backhaul, confirm that the ONT's LAN interfaces (2.5GBASE-T or 10GBASE-X SFP+) do not become the bottleneck for the PON uplink rate.

\n

Q5: How does this generation of ONT differ from previous generations in terms of WAN interface flexibility and stacking support?

\n

The current generation of B2B ONTs introduces significantly enhanced WAN interface flexibility compared to prior GPON-only models: dual-mode GPON/XGS-PON auto-sensing optics, support for 2.5GBASE-T copper and 10GBASE-X SFP+ LAN ports, and expanded MTU ranges in bridge mode (up to 9000 bytes on XGS-PON). Regarding stacking, ONT devices typically do not support traditional virtual chassis stacking like data center switches; instead, high availability is achieved through dual-homing to redundant OLT ports or PON protection switching. For stacking-like behavior at the customer premises, multiple ONTs can be managed logically through the OLT's OMCI or via an ACS/EMS platform, but this is management aggregation rather than a unified control plane stack.

\n

Q6: How do I troubleshoot redundant power failover issues on a rack-mounted B2B ONT?

\n

Redundant power failover troubleshooting should begin by verifying that both PSU slots are populated with modules of identical wattage and that the ONT's alarm LEDs indicate dual-feed health. Common failure modes include: one PSU feeding from a de-energized circuit, mismatched PSU firmware if the modules are intelligent, or a failed PSU that has not triggered an audible/visual alarm due to alarm suppression settings. Use the CLI command show power-supply (or equivalent platform-specific syntax) to inspect input voltage, output current, and fault status for each PSU. If the ONT unexpectedly reboots during a power event, check whether the hold-up time is sufficient for your backup generator start sequence; carrier-grade ONTs typically provide 10–20ms hold-up, which may not cover generator ramp-up.

\n

Q7: What CLI commands verify that the MTU override has been applied and is passing traffic correctly?

\n

After applying the MTU override, verify the configuration with personality show (or the platform-equivalent display command) to confirm the stored MTU value matches your intended setting. For functional verification, issue a ping with the Don't Fragment (DF) bit set and a payload size calculated from your target MTU: for a 9000-byte MTU, use ping -s 8972 -M do (8972 payload + 28 bytes IP/ICMP headers = 9000 bytes). A successful response confirms end-to-end MTU path support; a failure with "packet too big" or "fragmentation needed" indicates a downstream device is still at a lower MTU and must be adjusted. On the OLT side, verify the uplink NNI interface MTU and the per-ONT service profile MTU are aligned.

\n