This sounds like a "zombie client" issue where the controller flushes the user entry while the client still thinks the session is active. Since this started with the 8.13.2.0 update, here are the quickest things to check:
1. Check User Idle Timeout
The controller might be aging out the client too fast. Go to your AAA Profile > User Idle Timeout. Increase the value (default is 300s). If the client goes into power save and stops sending traffic, the controller drops it.
2. WPA3 / MFP Compatibility
WPA3 mandates Management Frame Protection (802.11w). If you are running a Transition Mode SSID (WPA2+WPA3), some older drivers fail to handle the MFP requirements.
Test: Create a test SSID with only WPA2-AES (MFP disabled/optional) and see if the drops persist.
3. Disable 802.11ax (HE) Features
There have been reported regressions in some 8.x builds involving High Efficiency (Wi-Fi 6) advertisements. Try disabling HE (High Efficiency) in the Radio Profile temporarily to rule out a chipset-specific incompatibility.
4. DHCP Enforcement
If DHCP Enforcement is enabled in the User Role, the controller will kill the session if it doesn't see a successful DHCP exchange. Try disabling it to see if the client remains in the User Table.
5. Debug via CLI
To see exactly why the controller is dropping the client, run:
logging level debugging user-debug <client_mac>
show log user-debug 50
Look for keywords like "Age out" or "Deauth".
6. Open a TAC Case
If these steps don't resolve the issue, I highly recommend opening a case with HPE Aruba TAC. This behavior is typical of a firmware bug in the 8.13.2.0 LSR branch. Provide them with the tech-support logs and the user-debug output to speed up the process.
Note: Check the "Known Issues" section of the release notes for "User Table Age-out" or "UAC/AAC heartbeat" issues.
---------------------------------
Francisco Pinto
francisco.pinto@novatec-corp.com---------------------------------