Wireless Access

Reply

Local probe threshold - Clients with SNR below threshold

I've set the local probe threshold on all our VAPs to 21.  I'm still seeing with an SNR below 21 connected.  My understanding was that the controller would not respond to client probe requests if the SNR of the client is below 21, which would effectively keep a client from associating to an AP if it's SNR is below 21.  So should I assume that the clients with an SNR below 21 were connected with an SNR above the threshold at first, and then an environmental change caused the SNR of the client to drop below the threshold?

=======================================
If a reply adequately addresses your issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users.

Re: Local probe threshold - Clients with SNR below threshold

I have spoke with a couple Aruba engineers and they've said that in order for this to properly work you have hide the SSID .

Look at this post :
http://community.arubanetworks.com/t5/ArubaOS-and-Mobility-Controllers/local-probe-response-threshold/td-p/67820
Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA

Re: Local probe threshold - Clients with SNR below threshold

Very interesting... This is a bit at odds with what another Aruba ACE engineer suggested.  Gotta love it!

 

I guess it goes back to the original intent of setting the local probe threshold.  I was trying to help clients make better association and roaming decisions.  Maybe I should try and attack the problem by modifying min/mx EIRP.

=======================================
If a reply adequately addresses your issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users.
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: