Also, on Windows, many WLAN drivers allow you to configure the Roaming Aggressiveness or Roaming Sensitivity:

There are also some things you can do from the WLAN side, as mentioned in the RF Design section of the Validated Solution Guides (VSG). By tweaking things like the beacon rate, probe response threshold, removing lower data rates, reducing/tuning the AP radio power, you can improve client roaming behavior as well; but it can break your network if you are not careful and know what you are doing. There are some guidelines in the VSG for different types of environments.
If the client has a strong enough signal, but is not connected to the closest AP, that may not be a big issue, but there are ways to improve that on the client side and/or network side. Unfortunately every client is different, so it may take some tries to find the right settings.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Feb 21, 2025 10:06 AM
From: tonstar
Subject: How to check Client Match settings?
Hi, thanks for the detailed response! I really appreciate the insight, especially the explanation about client roaming behavior and the command for checking signal strength on Windows. I'll definitely give that a try
Original Message:
Sent: Feb 21, 2025 04:11 AM
From: dvdwulp1970
Subject: How to check Client Match settings?
Hi Tonstar,
As Carson already stated, the client decides to roam. The client will do this as soon as the signal strength is less then -70db, a little depending on the device and/or OS. I am quite sure at 10m, the signal is still better than -70db. you can check the signal strength on a windows laptop using the following command in the CMD: netsh wlan show networks mode=BSSID. If 802.11k is enabled, you can even see the amount of clients connected and the utilisation in the air. If you are NOT connected to any SSID, you can see all available SSID's and all the BSSID's available for that SSID with their own signal strength. Having 10m between the two AP's is great if you rely on a good 2nd signal strength. And Aruba doesn't mind you buying more AP's. I am using 100-150m2 cell size for each AP when building a network according to the Very High Density Validated Design guide by Aruba. But if this is not needed, cell sizes can be twice a large.
Take a walk with your laptop and check the signal strength. I never play with minimal RSSI signal unless I really have to but not because I can ;-) Aruba does a great job the clients match at default.
Original Message:
Sent: Sep 30, 2024 08:42 PM
From: tonstar
Subject: How to check Client Match settings?
Hi everyone, I have a Mobility Controller 7010 with a few AP-518s installed in an office and Client Match enabled in ArubaOS 8.7.1.3. My goal is for clients to automatically switch APs as they move around. Testing shows that clients do switch APs, but not always at the same physical point, and I'm trying to understand why.
For example, I have two APs 10m apart. I expect a client to switch to the second AP when passing the midpoint (<5m away), but sometimes the client stays connected to the first AP even when directly beneath the second.
I've read that Client Match uses parameters like "Sticky Client Check SNR (dB)" and "Sticky Min Signal." Where can I find these settings in ArubaOS, and how do I check their current values? I couldn't locate them in the webUI."
TL;DR: Confused by seemingly random physical locations that clients switch APs consistently. Where can I find the Client Match parameters like "Sticky Client Check SNR" and "Sticky Min Signal" in ArubaOS?