Troubleshoot connectivity issues with the WAS-110 or X-ONU-SFPP¶

The MaxLinear SDK includes an extensive suite of debugging tools that come pre-bundled with the WAS-110 firmware(s). These tools can be run either from the shell console or have been tied into the web UI.

PON troubleshooting¶

Digital Diagnostic Monitor Interface¶

The WAS-110 supports the Digital Diagnostic Monitor Interface (DDMI)¹ to provide pseudo-real-time access to its operating parameters via a host interface. Although simplistic, this interface is suitable for monitoring power and temperature behaviours, which are the first tells of troubles.

For more details on accessing this interface, please search your hosts' documentation for Digital Diagnostic Monitoring (DDM) or Digital Optical Monitoring (DOM).

Host access¶

Linux / UniFi OS¶

ethtool -m <interface>

MikroTik RouterOS¶

/interface ethernet monitor sfpX #(1)!

1. Replace sfpX with the port name/number.

Optical power¶

Optical specifications¶

Industry standard signal ranges¶

Optical status¶

To determine if the WAS-110 optics are operating within specification, execute one of the following procedures:

pontop -b -g 'Optical Interface Status'

i2c_cmd show optical

And as with a Linux host, the DDMI¹ is available from the WAS-110 shell, where both Laser output power and Receiver signal average optical power can be evaluated.

ethtool -m pon0

OLT authentication¶

Activation states¶

• O1 Initial state
• O2 Stand-by state
• O3 Serial number state
• O4 Ranging state
• O5 Operation state
• O6 POPUP state
• O7 Emergancy stop state

Fake O5¶

A common term tossed around is fake O5, which is a misnomer that occurs when PLOAM message activation succeeds, including Serial Number and/or Registration ID authentication. However, the failure is further along in the registration chain, such as OMCI. It pertains to invalid managed entity attributes with common associations to device integrity, such as hardware and/or software versioning.

PLOAM status¶

To view the current PLOAM status (activation state), execute one of the following procedures:

pontop -b -g s

pontop -b -g 'PLOAM Downstream Counters'
pontop -b -g 'PLOAM Upstream Counters'

pontop -b -g s

pontop -b -g 'PLOAM Downstream Counters'
pontop -b -g 'PLOAM Upstream Counters'

OMCI clarification¶

To identify fake O5, execute the following command procedures. If the output is empty, the operational state is "fake" because the OLT failed to return the expected configuration. An output that only contains default rules can also be deceiving, even though it is technically valid.

8311-extvlan-decode.sh -t

omci_pipe.sh md | grep -E '^\|\s+(84|171)\s\|'

Additionally, it is possible to identify the connected OLT by executing the following command:

omci_pipe.sh meg 131 0

Typically, OLT operators enforce versioning compliance when software management is not handled over CWMP².

Alarms¶

Alarms are critical for diagnosing hardware failures, authentication errors, and physical layer issues. Use these indicators to pinpoint whether a fault originates with the OLT, the ODN, or your ONT.

Common alarms¶

To view real-time faults and begin remediation, execute one of the following procedures:

Page: Active alarms
Alarm type       Alarm                     Description
LEVEL            PON_ALARM_STATIC_LOS      Loss of signal
LEVEL            PON_ALARM_STATIC_LODS     Loss of downstream synchronization
LEVEL            PON_ALARM_STATIC_ERR_LOSS Same signal as LOS just configured as level sensitive

pontop -b -g w

pontop -b -g w

LAN troubleshooting¶

Link Speed¶

The WAS-110 will attempt to auto-negotiate with the host controller and, more often than not, fallback to 1 Gbps. To prevent this behaviour, forcefully set the speed of the host interface to 10 Gbps.

Furthermore, to force the link speed on the WAS-110 itself, execute the following ethtool³ procedures.

ethtool -s eth0_0 speed <speed> #(1)!

ethtool -s eth0_0 speed <speed> #(1)!

Tx fault¶

The SFP tx fault pin⁴ (2) is multiplexed with UART tx. If the serial UART is enabled, tx fault may be asserted by the host hardware and cause the link state to flap continuously.

Serial console¶

fwenv_set -8 console_en

env delete 8311_console_en
env save
env save

uci -c /ptconf set usrconfig_conf.InternetGatewayDevice__X_PT_CONSOLE_CFG__=interface
uci -c /ptconf set usrconfig_conf.InternetGatewayDevice__X_PT_CONSOLE_CFG__.Enable=0
uci -c /ptconf commit usrconfig_conf

Boot console & early printk¶

UART tx can be further controlled by two (2) U-Boot environment variables: uart_select and uart_select_preboot.

from the Linux shell

fwenv_set uart_select off

from the U-Boot shell

setenv uart_select off
env save
env save

Host Solutions¶

Linux (SFP subsystem)¶

SFP+ network drivers built on the Linux SFP subsystem use SFF-8472¹ DDMI to manage modules. This causes issues for non-compliant GPON and XGS-PON sticks. To work around this, maintainers add hardcoded quirks. However, each new hardware or vendor variant requires a new kernel build. As of kernel 6.17, a quirk for the Yunvo SFP+ONU-XGSPON (X-ONU-SFPP) module has been included to address this.

If you see the following output in your kernel log, you are either running an older kernel version, or your WAS-110 or X-ONU-SFPP module's vendor information does not match an existing quirk.

sfp sfp1: module transmit fault indicated
sfp sfp1: module persistently indicates fault, disabling

To resolve this issue, you can take one of two approaches:

1. Add a new quirk for your module and recompile your kernel.
2. Modify the vendor information on the module itself to match an existing quirk.

To achieve the latter, SSH into the module and read the current EEPROM value as base64, then paste it into the form below.

base64 /sys/class/pon_mbox/pon_mbox0/device/eeprom50

WAS-110 X-ONU-SFPP

Generate

Rx loss¶

The SFP rx loss pin⁵ (8) is asserted when the SC/APC fiber cable isn't plugged in and/or inactive. Depending on the host controller and implementation, the interface may enter a power saving state, making the WAS-110 inaccessible.

fwenv_set -8 rx_los

env delete 8311_rx_los
env save
env save

Host solutions¶

MikroTik RouterOS¶

/interface ethernet set sfpX sfp-ignore-rx-los=yes #(1)!

1. Replace spfX with the port name/number.

Common issues & workarounds¶

Nokia OLT (ALCL)¶

omci_pipe.sh meadg 131 0 1 | awk '/41 4C 43 4C/ {print "Nokia OLT"; id=1} /20 20 20 20/ {print "Fake O5"; id=1} END {if (!id) print "Other OLT"}'

GEM port encryption misconfiguration (key errors)¶

1. Check GEM port for Key Errors and make note of the GEM ID(s).

   pontop -b -g 'GEM/XGEM Port Counters'
   

2. If key errors are present (greater than 0), check GEM port Encryption Key Ring attribute value.

   omci_pipe.sh meadg 268 <GEM ID> 10 | awk -F'attr_data=' '{print $2}' # (1)!
   

   1. Replace <GEM ID> with the one found in the output for GEM/XGEM Port Counters page.

3. If the Encryption Key Ring value is 0 or 1, change it to 3 (downstream encryption only).

   omci_pipe.sh meads 268 <GEM ID> 10 3 # (1)!
   

   1. Replace <GEM ID> with the one found in the output for GEM/XGEM Port Counters page.

...
if ((*(int *)((int)local_38 + 0x13c) == 6) && (*(int *)((int)local_38 + 0x148) != 2)) {
    local_38 = (char *)0x7eb;
    omci_log_msg(8,4,"%s() [%d]Don\'t enable us aes for ALCL\n","ca_omci_saturn_gemflow_add",0x7eb);
    omci_log_print(1,8,"%s() [%d]Don\'t enable us aes for ALCL\r\n","ca_omci_saturn_gemflow_add",
                   local_38);
    if (param_1[0x16] == 1) {
      local_3c = 3;
    }
    else {
      local_3c = (undefined1)param_1[0x16];
    }
    iVar5 = param_1[3];
}
...