Wireless

Hi Community,

Any one can provide a document explaining deauthen reson and roming reson, please. I can't find it on the internet.

The CLI commands should be documented in the AOS or Instant CLI Reference guides available from the support site asp.arubanetworks.com

Those reason messages are in fact not documented in the latest document versions, but should be. it would be really helpful if you can file a support case, and point this out and TAC will  file a defect to these documented.

Dormant STA delete - The AP/MD system has entries for a client, but no frames have been heard within a given timeframe, so the client entries are deleted.

Sapcp Ageout - the Aruba AP/controller system processes are removing STA entries, could be the client roamed and no deauth frame was seen. Quite often because of client inactivity, and can be seen in cases where a client associates, but higher layers are failing (i.e. IPv4 or DHCP fails)

Wlan driver excessive tx fail quick kickout - specific to Qualcom chipset APs (ex. ap-3xx) the radio chip itself sees no frames from the client within X retries, declares the client gone, and informs the AP/MD to delete the client.

The CLI Reference guides cover commands that provide more detail: (AOS versions shown)

show ap clent trail (command depicted here)

show ap remote debug mgmt-frames * (consult CLI Reference guide for exact details)

show ap auth * (consult CLI Reference guide for exact details)

All of these seem to point to a client that associates, doesn't/can't communicate,  and the client moves.

One great tactic is an MD packet-capture, filtering on the client's MAC. 

Further interesting info:

https://blogs.arubanetworks.com/industries/802-11-reason-codes-and-status-codes/