NWA130BE latest firmware, anyone getting crazy amount of disconnects for Reason 34?

Options
jj38100
jj38100 Posts: 19 image  Freshman Member
First Comment Friend Collector Fourth Anniversary
edited March 3 in Wireless

Running NWA130BE with latest firmware to get proper MLO support for Smart Mesh.

It's happening across bands, but for 5ghz I'm running 40mhz and DCS (avoid dfs) enabled. Signal could be above -70dbm and it still happens

All Replies

  • jj38100
    jj38100 Posts: 19 image  Freshman Member
    First Comment Friend Collector Fourth Anniversary
    edited March 3

    So I've done some testing, I removed 5ghz from SmartMesh by bumping the radio down to 802.11ax, so I can lock down to using the 6ghz band as the backhaul. Reason 34 on the 2.4ghz and 5ghz bands has stopped, it only continues on the 6ghz band. This is pointing to some instability with SmartMesh and MLO. What's interesting is 2.4ghz was never even selected as an uplink band for SmartMesh MLO

  • Zyxel_Melen
    Zyxel_Melen Posts: 4,616 image  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
    edited March 4

    Hi @jj38100

    Please help to collect the diagnostic file when the issue happens so we can better investigate this issue.

    Standalone mode:

    https://community.zyxel.com/en/discussion/22983/how-to-collect-the-ap-diaginfo-on-the-standalone-mode

    Nebula mode:

    https://community.zyxel.com/en/discussion/31580/how-to-collect-the-nebula-ap-diagnostic-info-by-gui

    About the 2.4ghz was never even selected as an uplink band for SmartMesh MLO, it is because 2.4ghz band default radio mode is 802.11ax. Please help to change it to 802.11be before setup SmartMesh MLO.

    Zyxel Melen


  • jj38100
    jj38100 Posts: 19 image  Freshman Member
    First Comment Friend Collector Fourth Anniversary

    The SmartMesh was working, I am had the 2.4ghz radio forced to 802.11ax anyway, are you saying it should be set up as 802.11be even if it's not an eligible uplink band for MLO?

    How far back does the diagnostic files go? I can try setting it back to MLO.

  • Zyxel_Melen
    Zyxel_Melen Posts: 4,616 image  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @jj38100

    Thanks for the diagnostic file. The diagnostic file keeps how many previous logs depends on how many logs been generated before, therefore, I can't guarantee how far back does it go. And that's the reason I mentioned to collect it when the issue happens.

    We checked and noticed the reason 34 log could be an issue on the client's WiFi connection, not SmartMesh issue. And we have a date code firmware that we think it can fix the reason 34 issue. I have sent it to you via the private message.

    For the 2.4ghz MLO problem, I think I might have misunderstanding. Could you share more details about "What's interesting is 2.4ghz was never even selected as an uplink band for SmartMesh MLO"? Do you mean the AP's smartmesh setting with MLO? Or?

    Zyxel Melen


  • jj38100
    jj38100 Posts: 19 image  Freshman Member
    First Comment Friend Collector Fourth Anniversary
    https://community.zyxel.com/en/discussion/comment/83895#Comment_83895

    Thanks! Yeah I'll try the updated firmware.

    I think I just meant that 2.4ghz band was never part of MLO operations for SSIDs or for SmartMesh.

  • ScottE
    ScottE Posts: 3 image  Freshman Member
    First Comment First Anniversary

    I'm using an Ethernet backhaul on 3x NWA130BEs and seeing "reason 23" very frequently across all bands. Like the OP, my Pixel 10 and Pixel 10 Pro seem to rarely have all the bands connected in MLO.

    Same issue, or different issue and warrants a different post?

Categories

Wireless Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）