Masquerade as the Nokia XS-250X-A with the WAS-110 or X-ONU-SFPP¶

Purchase a WAS-110 or X-ONU-SFPP¶

The WAS-110 and X-ONU-SFPP are available from select resellers worldwide. To streamline the process, some resellers are pre-flashing the 8311 community firmware and highly recommended for the X-ONU-SFPP. Purchase at your discretion; we take no responsibility or liability for the listed resellers.

WAS-110 Value-Added Resellers

X-ONU-SFPP Value-Added Resellers

Install the 8311 community firmware¶

As a prerequisite to masquerading as the XS-250X-A, the 8311 community firmware is recommended and required for the remainder of this guide. If you purchased a pre-flashed WAS-110 or X-ONU-SFPP, skip past to the masquerade setup.

Masquerade setup¶

Additionally, mandatory identifiers are available on the back label of the XS-250X-A, such as ONT P/N, ICS, and CLEI if present.

from the web UI recommended¶

1. Within a web browser, navigate to https://192.168.11.1/cgi-bin/luci/admin/8311/config and, if asked, input your root password.

2. From the 8311 Configuration page, on the PON tab, fill in the configuration with the following values:

   All attributes below are mandatory to achieve O5 operation state

   Replace the PON Serial Number, IP Host MAC address, Registration ID, and Software Version A/B with the provisioned values.

   Attribute	Value	Remarks
   PON Serial Number (ONT ID)	ALCL…	Serial number
   Equipment ID	BVMGJ10BRAXS250XA	CLEI + Mnemonic
   Hardware Version	3FE48114ABBD01	ONT P/N. + ICS
   Sync Circuit Pack Version
   Software Version A	3FE47493HJKI15	Active software version
   Software Version B	3FE47493HJKI15	Standby software version
   Firmware Version Match	(3FE[0-9A-Z]{11})$
   Override active firmware bank	A	OLT inits a reboot if on bank B
   Override committed firmware bank	A	OLT inits a reboot if on bank B
   MIB File	/etc/mibs/prx300_1U.ini	PPTP i.e. default value (Telus customers use prx300_1U_telus.mib)
   PON Slot	10

3. From the 8311 Configuration page, on the ISP Fixes tab, disable Fix VLANs from the drop-down.

   Identify VLANs

   Once configuration is complete and the fiber is connected, wait for successful authentication (O5 state). You can then use the VLAN Table Analyser to identify service VLANs by copying the table from the VLANs page (https://192.168.11.1/cgi-bin/luci/admin/8311/vlans) and pasting it into the tool.

4. Save changes and reboot from the System menu.

from the shell¶

1. Login over secure shell (SSH).

   ssh root@192.168.11.1
   

2. Configure the 8311 U-Boot environment.

   All attributes below are mandatory to achieve O5 operation state

   Replace the 8311_gpon_sn, 8311_iphost_mac, and 8311_sw_verA/B with the provisioned values.

   fwenv_set -8 gpon_sn ALCL... # (1)!
   fwenv_set -8 equipment_id BVMGJ10BRAXS250XA # (2)!
   fwenv_set -8 hw_ver 3FE48114ABBD01 # (3)!
   fwenv_set -8 cp_hw_ver_sync 1
   fwenv_set -8 sw_verA 3FE47493HJKI15
   fwenv_set -8 sw_verB 3FE47493HJKI15
   fwenv_set -8 -b fw_match '(3FE[0-9A-Z]{11})$'
   fwenv_set -8 override_active A
   fwenv_set -8 override_commit A
   fwenv_set -8 pon_slot 10
   fwenv_set -8 fix_vlans 0
   

   1. Serial number or S/N
   2. CLEI + Mnemonic
   3. ONT P/N + ICS

   Additional details and variables are described at the original repository ¹

   /usr/sbin/fwenv_set is a helper script that executes /usr/sbin/fw_setenv twice consecutively.

   The WAS-110 functions as an A/B system, requiring the U-Boot environment variables to be set twice, once for each environment.

   The -8 option prefixes the U-Boot environment variable with 8311_.

3. Verify the 8311 U-boot environment and reboot.

   fw_printenv | grep ^8311
   reboot
   

After rebooting the WAS-110, safely remove the SC/APC cable from the XS-250X-A and connect it to the WAS-110. If all previous steps were followed correctly, the WAS-110 should operate with O5.1 PLOAM status. For troubleshooting, please read the Troubleshoot connectivity issues with the WAS-110 guide before seeking help on the 8311 Discord community server.

Software versions¶

The following are the last known supported software versions. If the Firmware Version Match attribute is configured with the correct regular expression, the Software Version A/B attribute(s) will attempt to auto-update to match the firmware version transferred by the OLT, although this isn't foolproof. Most OLT provisioning systems will attempt to update the firmware via OMCI upon detecting a mismatch. Note that this transfer can take several minutes due to the size of the firmware image. These images are stored at /tmp/upgrade/firmware.img and can be dumped for analysis.

Please help us by contributing new versions via the 8311 Discord community server or submitting a Pull Request on GitHub.