Wireless Access

Hi Everyone,

I have Handheld 802.1 a/b/g/n how to config roamming like ClientMatch?

When connected on IAP1 then i walk nearby IAP2 hendheld don't connnect to IAP2.

Best Regards,

BABABA

It is the clients decision which AP it will roam too, not the AP. You can use ClientMatch however to influence the devices decision to roam.

Are you able to identify the received signal strength from each AP where the client is located? It might be high enough that the client does not roam.

During the mean time, more info on Client Match can be found here.

http://www.arubanetworks.com/techdocs/Instant_40_Mobile/Advanced/Content/UG_files/ARM/ARM_Features.htm#Spectrum

Hi Zalion0,

The CliantMatch doesn't supported a/b/g right?

I show you table below.

---

wrote:

Hi Everyone,

 

I have Handheld 802.1 a/b/g/n how to config roamming like ClientMatch?

 

When connected on IAP1 then i walk nearby IAP2 hendheld don't connnect to IAP2.

 

Best Regards,

BABABA

---

Clients make the decision to roam themselves.  On the infrastructure side, you can encourage them however by:

- Lowering the transmit power of the access points

- Removing the lower transmit rates on the SSID profile.  An example of how to remove lower rates is here:  http://community.arubanetworks.com/t5/Controller-Based-WLANs/Why-do-I-need-to-disable-lower-data-rates-on-802-11g-band/ta-p/174978

Client Match is not a roaming mechanism because it does not trigger often enough to help a moving client.  It should not be relied on for roaming, because it is not intended for that.

Hi cjoseph,

Thank you.

I'll try to do like that.