Wireless Access

Reply
Occasional Contributor II

Logging client match reasons

I'm parsing my aruba logs and I see many client match events like:

 

Deauth to sta: 14:dd:a9:a8:8d:e1: Ageout AP 192.168.244-24:de:c6:13:64:80-EWFMA-Atrium Client Match

 

Is there a way to increase the logging verbosity of client match so that it will also log the *reason* for the client match event?

 

As far as I know there are three reasons a client can be moved:

 

band-steering

sticky client

load-balancing the AP

 

 

It would be really helpful to be able to syslog the reasons for an event so I can then coalate them and get a better idea of what is happening in various physical locations.

 

Thanks. 

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: