Hello,
I want to pick up this discussion for further documentation, if you hit the issue that clients will not connect to an AP-505 at 8.6.x release.
Because this thread will be an google hit if you search for this issue...
Actually I was informed by an customer, that the connection to an SSID with WPA2 PSK authentication at one particular AP-505 fails (mobility conductor, md cluster environment).
The issue was reproducable, and shows up as follows:
- Older devices, like Galaxy S5 NEO, will try to connect but will not be successfully without any error message.
- If an older AP, AP-305 with an open ssid and captive portal for instance, is around, the device will connect there
- Newer devices supporting AX, for example IPhone 12, will throw an connection error
If you issue auth-tracebuf, you will see messages until wpa2-key4 but the user never will show up at the user table.
It's interesting, that in some cases the user will be shown on the user list at mobility conductor GUI and entrys for active and standby controller but without IP address.
But as wrote before, if you issue show user-table, the client will not show up at cli.
Of course the device will also get no IP address and will not shown at the ARP table at default GW.
In this chase, we got nearly 40 AP-505's purchased at quater 3 of 2020.
All AP's of that batch are working fine and are not affected.
A couple of months later, we added one AP-505.
Only this one AP-505 is effected by the issue.
I was able to fix the issue with disabeling high efficiency for that particular SSID.
This workaround was necessary at version 8.6.0.16.
The release notes of 8.7.1.1 (AOS controller based, I did not find it at instant release) does contain a driver update for AP-505.
The bug ID's AOS-207318, AOS-207996 were fixed by that release with the description: "Clients experienced poor performance with AP-505
access points running ArubaOS 8.7.0.0 or later
versions. Enhancements to the wireless driver
resolved this issue.".
Because of that, I decided to update the whole infrasructure (conductors, MD's, AP's) to 8.7.1.8.
And, yes, with 8.7.1.8 the issue is gone.
With enabled HE, the connection to that one AP was successfully again!
So may, a batch of AP-505's will have this issue, others not.
May some little differences in the hardware, or something else?
However, for this setup, the issue was only resolvable by updating to 8.7.1.8 (not tested with 8.7.1.1 - 8.7.1.7 or instant releases).
Unfortunately, 8.7.x is still not at conservative state....
------------------------------
Best regards, mom
------------------------------
Original Message:
Sent: Feb 02, 2021 10:36 PM
From: David Adino
Subject: Issue - Client connectivity loose ArubaOS 8.6.0.5 with AP-505
Hi mkk,
My customer is experiencing similar behaviour as yours, and its killing us lol.
Have you manage to resolve the issue?
For what we know so far, many people have suggested disabling High Efficiency (AX). However, using AX is part of the reason buying AP 505.
Support have verified there is performance issue bug and release note about enhancing AP 505 driver in 8.7.1.1.
I am waiting for the upgrade window and hopefully the issue gets resolved.
BR
David
------------------------------
David Adino
Original Message:
Sent: Sep 30, 2020 03:35 PM
From: Justin Rosenbrock
Subject: Issue - Client connectivity loose ArubaOS 8.6.0.5 with AP-505
Do you have DHCP logs from when the connection is failing?