Probe Suppression/Force Disassociation

Thanks. We are already running 10.01.03.0007 on our controllers. We use a min rate of 12 on radio1 and 6 on radio2. I will look into increasing the min rate on radio2 in order to decrease the cell size. Is that considered a more reliable way to "force" roaming than probe suppression?

Thanks again for the input. I don't see the fast transition option in the privacy tab of my vns. I looked in the controller manual, and while it is listed as an option under the fields and buttons section, the privacy tab snapshot on page 232 does not show the option. I'm assuming that there is a prerequisite that we are not meeting.

I'm also not sure that 8011.r will address our issue. It is supposed to make roaming faster, but the client is still in charge. Our issue is not that the clients are roaming too slowly, but rather they are not roaming at all when there are better signal options available. Decreasing the cell size seems like the most viable option at the moment, unless the the probe suppression worked as intended

FYI 802.11r is only an option if your wlan is using WPA (not WPA -PSK).

If your testing probe suppression, make sure you are are verifying roam activity by looking in Netsight>Wireless>clients. We were originally looking at the Clients By AP reports on the controllers and after working with GTAC, it seems that is not a reliable to determine the active clients. See GTAC's note below:

"After discussion with some of my colleagues as well as the wireless developers, we determined that the client reports are not actually a list of currently connected clients. These are actually showing the currently authenticated clients, regardless of whether the client is actually connected to an AP.

Because of this, once a client is disconnected by force disassociation, it will stay in the report for 30 minutes, assuming the session timers are set to defaults."

We are not using fast roaming (802.11r) in our environment. Fast roaming was designed to speed up the key exchange for mobile users when roaming. Since we are using WPA-PSK, there is no key exchange when roaming.

For us, the question became how to verify the force disassociation threshold was working. You can verify client association by looking in the Wireless>Clients view in Netsight, or by using 3rd party software on the client itself, such as Acrylic or even Ekahau.

One caveat that is not stated in the manual, found in https://gtacknowledge.extremenetworks.com/articles/Solution/Issues-with-clients-staying-with-an-Acce... , is that the client will be disassociated 5dBm below the disassociation threshold. So if you set the threshold to -70, the system will disassociate clients at -75. Hope this helps.

Hi FES

I have Probe supression enabled with RSS: -65 , min rate of 6 mbps and disabled b clients (only using g/n) is it fine ?

I was on the phone with GTAC last week troubleshooting something unrelated to probe suppression. One of the things they wanted me to verify was that probe suppression was not enabled, as there is apparently a current known bug. we are running firmware 10.11.02.0032 on our controllers. I didn't ask any further questions since we are not currently using it, however maybe someone from extreme can confirm in this post.