Overview

Deploying a high-performance Wi-Fi Mesh network in a B2B environment requires the seamless integration of an OEM Optical Network Terminal (ONT) with secondary wireless extenders. This expert guide addresses critical pre-sales technical specifications and post-sales configuration challenges, ensuring your enterprise infrastructure meets stringent throughput, redundancy, and security requirements.

Frequently Asked Questions

Q1: What is the maximum throughput (Gbps) supported when connecting an OEM ONT to Wi-Fi Mesh extenders via the Ethernet WAN port?

The maximum throughput is defined by the ONT's Ethernet WAN port speed and the extender's backhaul capability, typically ranging from 1 Gbps to 10 Gbps. For multi-gigabit deployments, ensure the ONT features a 2.5G/5G/10G-Base-T port and the extenders support a corresponding wired backhaul link to avoid bottlenecking the total wireless aggregate capacity.

Q2: Does the OEM ONT support the 802.11k/v/r protocols necessary for seamless roaming between the primary ONT Wi-Fi and secondary extenders?

Yes, modern OEM ONTs often support 802.11k/v/r standards within their embedded Wi-Fi chipset when configured as the mesh controller. However, if the ONT acts solely as a modem (bridge mode), you must deploy a separate mesh controller or ensure your secondary extenders can operate in an autonomous mesh topology utilizing these fast-roaming protocols.

Q3: What are the CLI command prerequisites for configuring VLAN trunking between the ONT and a managed extender to separate guest and corporate traffic?

The primary CLI prerequisite is to define the VLAN interface on both the ONT and the extender using the 'interface vlan' command, assigning the appropriate subnet and DHCP scope. You must set the Ethernet uplink port connecting the extender to the ONT as a trunk port using 'switchport mode trunk' and explicitly allow the specific VLAN IDs (e.g., 'switchport trunk allowed vlan 10,20') to preserve the tag across the physical link.

Q4: How do I troubleshoot a situation where the secondary extender fails to obtain an IP address from the ONT's DHCP server after a power cycle?

First, verify the physical link status by checking the Ethernet LED on the ONT and extender; a solid link confirms Layer 1 connectivity. Subsequently, access the ONT's CLI and execute 'show dhcp lease' to confirm the extender's MAC address is not excluded and that the IP scope has not been exhausted; if the lease is absent, reboot the DHCP service using 'clear ip dhcp binding *' and restart the extender.

Q5: How do I configure an OEM ONT's built-in Wi-Fi to broadcast a unique SSID while still allowing the secondary extenders to extend that same network with different BSSIDs?

Configure the primary SSID and security settings within the ONT's Wi-Fi management interface (via CLI or Web GUI). For the extenders, configure them in 'repeater' or 'mesh' mode, utilizing the same SSID and passphrase but selecting 'Bridge' or 'Router' mode for IP assignment; the extenders will inherently broadcast a unique BSSID, but the ONT's controller (if available) should manage handoff via 802.11r.

Q6: What is the maximum recommended distance between the OEM ONT and the first secondary extender for optimal 5GHz backhaul signal integrity?

The maximum recommended distance is 10 to 15 meters (30-50 feet) in an indoor environment with minimal physical obstruction. For distances exceeding this, the 5GHz backhaul signal may degrade by more than 20%, significantly impacting the maximum throughput and increasing latency; consider relocating the extender or utilizing a wired Ethernet backhaul for superior performance.

Q7: What is the procedure for performing a factory reset on the OEM ONT and re-synchronizing the extender mesh network after a firmware mismatch error?

To resolve a firmware mismatch, physically power cycle the ONT and press the reset pinhole for 10 seconds until the status LED flashes rapidly. Next, upload the correct unified firmware image via TFTP from a management server and wait for the reboot to complete. Finally, power off all extenders, power them back on sequentially, and ensure the 'auto-join' feature or the specific MAC filtering list on the controller re-establishes the mesh links.