Wireless Access

if I make a "local probe response threshold" setting change, how quickly does it take effect? Is it immediate, or does it require power cycle or scan cycle?

Additionally, is there a way to see those interactions (when an ap ignores a probe below threshold) so I can see if we've gone too far?

We're at 20 now, considering changing to 25 or 30 to address far roaming and sticky client issues.

Thanks!

It should take effect right away , but I think it would only impact new clients already associated clients will need to reassociate.

But you can check the SNR that the clients that are connected to a certain AP

show  ap  debug client-table ap-name <ap-name> 

---

@r_harris@culinary.edu wrote:

if I make a "local probe response threshold" setting change, how quickly does it take effect? Is it immediate, or does it require power cycle or scan cycle?

 

Additionally, is there a way to see those interactions (when an ap ignores a probe below threshold) so I can see if we've gone too far?

 

We're at 20 now, considering changing to 25 or 30 to address far roaming and sticky client issues.

 

Thanks!

---

Try enabling "hide ssid" in the Advanced Properties of the SSID profile.

Can you elaborate on why that would be a benefit (not a challenge, just looking to understand).

Thx!

Harris,

Which one of the suggestions ?

---

@cjoseph wrote:

---

---

Try enabling "hide ssid" in the Advanced Properties of the SSID profile.

 

---

Some clients still want to associate when they see the SSID in the beacon even with the threshold set.  Enabling Hide SSID works out more favorably for those clients.

Is your problem with roaming?

problem is that clients see too many APs and won't always connect to the nearest AP.

Just tried the "hide ssid" option, and no one could see the SSID at all.

---

@r_harris wrote:

problem is that clients see too many APs and won't always connect to the nearest AP.

 

Just tried the "hide ssid" option, and no one could see the SSID at all.

 

 

---

If your clients can see to many access points, you need to reduce the number of access points in the area, or decrease the power of all access points.

 Local-Probe-Threshold-Response will not do anything for you.  That feature is to attempt to keep a device from attaching to a very, very weak access point on the other side of the room, usually in an environment that is not dense.

Client roaming decisions, no matter how much we try to influence them, are ultimately made by clients. All we can do is encourage them.   Local-Probe-Thresh-Response is the wrong feature for you.

You should probably try 25 (Best practices) 30 might be a little bit to aggressive for certain clients