Controller Based WLANs

Debugging Cellular Handoff Assist
Problem:

When cellular handoff assist is enabled, Client Match will attempt to unstick a sticky client even when there is no better (or other) Wifi radio available on the same band.

There might be cases when this customer will like to debug the reason for client disconnection & find cellular handoff assist to be one of the reasons.

So, this article will help in verifying if client movement was due to CHA.



Diagnostics:

In order to get detailed information regarding CHA moves, we need to enable the following debugging on the controller.

We can enable client-match related debugging to capture the CHA events.

•logging level debugging arm subcat client-match



Solution

 

1. Mgmt-frame output will show the De-auth reason to be CHA.

show ap remote debug mgmt-frames ap-name <name of ap> client-mac <mac-address of client>

 

2. Client Match summary will log the event as sticky client.

show ap arm client-match summary

3. ARM logging will list the Client Match event related to CHA.

show log arm all | include <mac-address of client>

 

4. AP client trail-info will record the De-auth reason as "Cellular handoff Assist"

show ap client trail-info <mac-address of client>

Version History
Revision #:
2 of 2
Last update:
‎04-03-2017 12:30 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.