Higher Education

Hello

 

What is the recommended settnigs for the RF Optimization profile. Reading about it: the station handoff assist allows the controller to force a client off an AP when the RSSI drops below a defined minimum. By default is disable.

 

Would enabling this help my users to find APs where they will have better RSSI. If a client connect to a AP with a RSSI of -80 and i set the threshold at 75, then the AP will send a death message to the client forcing the client to associate possible to a better AP with RSSI better than 75. Am I correct? If so, this feature will be helpful for builidng that i have high density deployments.

 

Thank you

NIls.

What version of AOS are you using ?

 

If you have AOS 6.3 you can take advantage of ClientMatch that will help with this

If you're on AOS 6.3, it is probably best to use Client Match instead to take care of this stuff.

SHA, should be used in combination with Local Probe threshold as well.

SHA Allows the controller to force a client off an AP when the RSSI drops below a defined minimum threshold. (as per AOS user guide)

Jinx @victorfabian!

:)

Client-match will over-ride this feature of hand-off assist/load-balancing the clients to better AP. I wouldnt recommend this to enable if you have already enabled client-match feature.

 

Thank you.

Thank you i think is better to use Client Match than mess with these features!

 

Enlighten me please gentlemen. I just recently upgraded to 6.3, where do I find Client match to enable it?

 

Thanks :-)

It should be under ARM profile. find below,

 

 

(M3) # show rf arm-profile default

Adaptive Radio Management (ARM) profile "default"
-------------------------------------------------
Parameter Value
--------- -----
Assignment single-band
Allowed bands for 40MHz channels a-only
80MHz support Enabled
Client Aware Enabled
Max Tx EIRP 127 dBm
Min Tx EIRP 9 dBm
Rogue AP Aware Disabled
Scan Interval 10 sec
Aggressive scanning true
Active Scan Disabled
ARM Over the Air Updates Enabled
Scanning Enabled
Multi Band Scan Enabled
VoIP Aware Scan Enabled
Power Save Aware Scan Disabled
Video Aware Scan Enabled
Ideal Coverage Index 10
Acceptable Coverage Index 4
Free Channel Index 25
Backoff Time 240 sec
Error Rate Threshold 50 %
Error Rate Wait Time 30 sec
Channel Quality Aware Arm Disabled
Channel Quality Threshold 70 %
Channel Quality Wait Time 120 sec
Minimum Scan Time 8
Load aware Scan Threshold 1250000 Bps
Mode Aware Arm Disabled
Scan Mode all-reg-domain
Cellular handoff assist Disabled
Client Match Enabled=================THIS CONFIG OPTION NEEDS TO BE ENABLED FOR CLIENT-MATCH FEATURE TO TURN ON.
Client Match report interval (sec) 30
Allows Client Match to automatically clear unsteerable clients after ageout Enabled
Client Match Unsteerable Client Ageout Interval 2 Days 0 Hours
Client Match Band Steer A Band Min Signal (-dBm) 75
Client Match Sticky Client Check Interval (sec) 3
Client Match Sticky client check SNR (dB) 25
Client Match SNR threshold(dB) 10
Client Match Sticky Min Signal 70

It's enabled by default , under ARM settings

Thanks gang, looks like it was enabled by default from the upgrade.

What version of 6.3 are you running?

Nils - if you mean me, I am now running 6.3.1.5, been happy with it so far...

Thank you Scott

 

What wireless controllers are you running your production? I have some M3, 3400, and 7000 series controllers and had some issues running 6.3 on the M3 cards.

 

Have you heard anything regarding version 6.3.1.7?

Nils,

 

We are a smaller outfit wireless wise. I am currently running a 3600US, a 3400US and a 3200XM as locals and have a 3200XM as a dedicated master - all on 6.3.1.5. I had a small hiccup with some other issues later and during the TAC support call they did recommend bumping up to the 6.3.1.7, but then again TAC usually recommends bumping up to the latest revs :-)

---

@nilslau03 wrote:

Thank you Scott

 

What wireless controllers are you running your production? I have some M3, 3400, and 7000 series controllers and had some issues running 6.3 on the M3 cards.

 

Have you heard anything regarding version 6.3.1.7?

---

What issues have you noticed on M3 cards?

 

I am getting ready to upgrade from 6.1.3.9 to 6.3.1.7 and I am upgrading a pair of 3600 master controllers with 2x3600 DMZ controllers and 2x6000 chassis with 3xM3 cards in each acting as locals to the pair of Master 3600s. 

 

Customer wants the configuration to remain the same, no changes, that means no client match (for now) and I have to disable airgroup upon upgrade.

 

Scott they recommended me to upgrade to 6.1.3.7 as well, according to TAC this version fix several bugs found on previous versions.

 

Pasquale,

 

I have a mix of AP 70, 105, 125, and 135. In my case AP 125 were dropping connections in high density areas such as classrooms. Same AP in the hallway were working fine. I experience this accross campus and two M3 cards have memory utlization spikes that were causing the STM module to not respond. They told me to upgrade to the latest code. I am planning an ugrade in two weeks.

 

Nils.

 

Thanks for the quick response nilslau03.
My deployments has 105s everywhere. I don't expect issues but you never know.

Thanks for providing insight