Wireless Access

Reply
New Contributor
Posts: 1
Registered: ‎06-02-2016

Client match doesnt work if the APs are configured as AP specific --But they are in same ARM profile

Hi

I have configured APs in the AP specific group.

eg: ap-name "B3-RR3-R2-W078"
regulatory-domain-profile "NO_DFS"

ap-name "B3-RR3-R3-W338"
regulatory-domain-profile "NO_DFS"

 

There is no difference in the arm profile for the 2 APs.

Both the above mentioned Aps belong to the AP-group mentioned below:

ap-group "Ward_Tower(RH)_L2"
virtual-ap "civetcat_dot1x"
virtual-ap "woodpecker_wpa2-psk"
virtual-ap "parrot_wpa2-psk"
virtual-ap "penguin_wpa2-psk"
virtual-ap "TMEP_wpa2-psk"
virtual-ap "wireless@sg_cp"
virtual-ap "wireless@sgx_dot1x"
virtual-ap "vocera_vap"

 

They both belong to the same arm profile. Client match is enabled.

But the user doesnt roam to another AP.

 

Guru Elite
Posts: 21,587
Registered: ‎03-29-2007

Re: Client match doesnt work if the APs are configured as AP specific --But they are in same ARM pro

The client decides when it will roam to another AP.   Client Match is not a roaming mechanism; it will help if it believes a client is "sticky".  What is your ARM Maximum Transmit Power for those APs?  You could have the power too high.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

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