Wireless Access

 View Only
last person joined: 4 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

Changed AP315 for AP655 and now MPSK clients re-auth successfully but lose connectivity

This thread has been viewed 9 times
  • 1.  Changed AP315 for AP655 and now MPSK clients re-auth successfully but lose connectivity

    Posted Aug 28, 2024 05:06 PM

    All clients were working fine on wireless AP315, i swapped some AP's to test some AP655's in our environment  and we now have an issue with any Raspberry PI connected to only the 655 AP's - anything connected to an AP315 works fine and as expected.

    Raspberry PI clients are running yodeck - connect using MSPK and clearpass guest accounts. every 24hours they re-auth and its hit or miss if they continue have access to the network (each time in the clearpass logs they show as authing fine and get assigned the correct role)

    The client is visible in the Aruba Wireless GUI and is connected and assigned a role as well.

    removing the user will force it to re-auth and it will connect without any issues or reboots.

    Has anyone else seen something similar? It feels like its holding onto auth on the AP somehow and not re-authing the client correctly. 

    TAC have found this "Disassociated; Auth frame from STA that was already associated  STA has roamed to another AP" and we have tried to change the channel bandwidth's (5GHz from Max 80mhz down to 40mhz, which reduced speeds by about 10x) and also disabled high throughput both having negative impacts on other clients 

    we are running 8.10.0.12 LSR

    Any help appreciated!



  • 2.  RE: Changed AP315 for AP655 and now MPSK clients re-auth successfully but lose connectivity

    Posted Aug 29, 2024 03:36 AM

    It may be something with 802.11ax, which the raspberry pi does not like (but you disabled HT, which is strange as the AP315 supports HT as well). Similar problems tend to need packet captures or at least deeper debugging; and one thing you can try 'for free' is upgrading to 8.10.0.13 LSR.

    If you have not done yet, escalate this issue with TAC as after you disabled some features it doesn't sound like something that would be resolved at first-line.



    ------------------------------
    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.
    ------------------------------