Question: What changes can cause clients to be deauthorized from an Aruba AP with the "deauth due to configuration change" message?
Product and Software: This article applies to all Aruba controllers that run ArubaOS 3.4.x.
These changes can cause clients to be deauthorized with the "deauth due to configuration change" message:
· WEP key change
· PSK change for WPA/WPA2
· time range change
· counter measure configuration change
· preauthorization configuration change
· DMO configuration change
· deny broadcast configuration change
· battery boost configuration change
· ESSID name change
· channel change
· WMM configuration change
In general, anything that changes the traffic behavior in the tunnel or in the air causes all stations to be kicked off.
If you are using ArubaOS 5.x, this message is not logged, although the behavior is basically the same.