Hi
I just wanted to share some experiences with high density ares and AP-220 series.
I large customer had much of the same issues explained in this tread, not only towards Intel.
They saw random disconnects, even failure to connect.
We could actually see that the client was unabel to get a lock on the AP when roaming, PHY state was suddenly g, not a-HT or a-VHT.
Often had to reboot computer or disable/enable the wireless device to get it running again.
The Aruba system was running with most of the settings default, VHT and CM enabled and all.
This happened only on AP-220, when moving to a buidling with the older AP-130 series, the issue was not seen.
After weeks with TAC, i was given some new RF settings to use with AP-220 in particular.
We ended up running AP groups for only AP-220 beacuse of this.
The problem was related to too agressive Client Match etc, hence the roaming did not work, so users was disconnected.
I use these settings whenever i install a system running AP-220's, this has proven to be very stable.
As i understand much has changed with new drivers, but these settings a worth a shoot.
This particular customer is running controller-based, but i guess this was aparent allready.
As these problems happend over a year ago, the controllers in question was running 6.3.1.x, and they have been upgraded across 6.4 without problems.
Settings we implemented are as follows:
rf arm-profile "default.armg.11ac"
cm-sticky-snr 15
cm-sticky-min-signal 65
cm-steer-timeout 3
cm-lb-thresh 30
cm-lb-client-thresh 30
cm-max-steer-fails 2
!
rf ht-radio-profile "default.htrpg.11ac"
!
rf dot11g-radio-profile "default-g.11ac"
arm-profile "default.armg.11ac"
ht-radio-profile "default.htrpg.11ac"
!
rf arm-profile "default.arma.11ac"
cm-sticky-snr 15
cm-sticky-min-signal 65
cm-steer-timeout 3
cm-lb-thresh 30
cm-lb-client-thresh 30
cm-max-steer-fails 2
!
rf ht-radio-profile "default.htrpa.11ac"
Hope this will help you
Roar Fossen