Wireless Access

This community is currently in a read-only state due to a maintenance window. For more info click here
Reply
Highlighted
Frequent Contributor I

local probe response threshold

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!

Highlighted
MVP Expert

Re: local probe response threshold

 

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> 

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Guru Elite

Re: local probe response threshold


@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.

 


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
MVP Expert

Re: local probe response threshold

 

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

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Frequent Contributor I

Re: local probe response threshold

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

 

Thx!

Highlighted
MVP Expert

Re: local probe response threshold

 

Harris,

 

Which one of the suggestions ?

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Frequent Contributor I

Re: local probe response threshold


@cjoseph wrote:



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

 


 

Highlighted
Guru Elite

Re: local probe response threshold

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?


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
Frequent Contributor I

Re: local probe response threshold

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.

 

 

Highlighted
Guru Elite

Re: local probe response threshold


@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.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: