Wireless Access

 View Only
last person joined: 2 days ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Client can't associate to WPA2/WPA3 ssid

This thread has been viewed 17 times
  • 1.  Client can't associate to WPA2/WPA3 ssid

    Posted 2 days ago
      |   view attached

    Hi everyone,

    I hope you're all doing well. I've encountered a strange issue after migrating my standalone controller to an MM hierarchy. Some devices can connect to open SSIDs but can't associate with WPA2/WPA3 SSIDs. The AP logs show "A constrained max client," even with only 2-3 clients connected to the AP. This issue affects all APs in my network, impacting devices like Samsung TVs and Nintendo Switches. I've attached a screenshot of the 802.11 management frame. Any help would be appreciated!

    Thanks!



  • 2.  RE: Client can't associate to WPA2/WPA3 ssid

    EMPLOYEE
    Posted 2 days ago

    Hi Joe,

    What version of AOS are you running? This may be fixed by upgrading perhaps.




  • 3.  RE: Client can't associate to WPA2/WPA3 ssid

    Posted 2 days ago

    8.10.0.13 , should be latest LSR version 




  • 4.  RE: Client can't associate to WPA2/WPA3 ssid

    EMPLOYEE
    Posted 2 days ago

    What is max associations set to in the SSID profile? 64?

    If yes, try increasing max associations from 64 to something like 128 or 256.




  • 5.  RE: Client can't associate to WPA2/WPA3 ssid

    Posted 19 hours ago

    I gave it a try today, but I'm still facing the same issue with any WPA2/WPA3 SSID

    It connects straightforwardly with open SSIDs




  • 6.  RE: Client can't associate to WPA2/WPA3 ssid

    Posted 19 hours ago

    Are your clients WPA3 capable? The logs mention SAE, which is the WPA3 Equivalent of WPA2-PSK. WPA3-SAE is not backward compatible with WPA2-PSK, and if you have not enabled transition mode (which in fact configures 2 different SSIDs, one for WPA2 the other for WPA3), clients not supporting SAE may not be able to connect.

    I would for now try with WPA2 and see if that fixes the issue... and explore the options from there.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------