if the CPU is at 100% then there is obviously an issue and this can sometimes be due to the rpm cache and max-aid values.
I would do the following on the AP's to reduce some of the CPU load and tweak network performance:
then run this on each model of you AP:
then using the values above issue the following:
Note: As you can see the default unconnected cache on my AP is 640 per radio.
Essentially what I have done here is set the maximum association per radio to be 100 (connected client cache) and then applied the same value to the rpm (unconnected client cache).
By default the AP will dedicate resource to the unconnected client cache and the default value is 512 for each radio - so its wasting memory on clients that are not even connected 😞
By setting the rpm to be the same value as the max-aid what you get is a see-saw effect:
In a state where no clients are connected you get this:
connected cache = 0
unconnected cache = 100
and then when they connect you get this:
connected cache = 10
unconnected cache = 90
Essentially all you are doing here is allowing the AP to dedicate memory to the maximum of clients you want to per radio.
I would also issue the following:
If you have multiple SSID's then you need to apply the above commands to the relevant SSID's i.e. set ofdm-only to 2.4GHz SSID and the set bss-minrate & proxy-arp to both 2.4 and 5GHz SSID's.
If you are using an SCG you can accomplish this by using a ksp script in the following format:
You can upload the ksp file from the Administration>Diagnostics>AP CLI Scripts
This can also be accomplished in the Edit WLAN Config>Advanced section:
Outside of the above you could look at load balancing clients and band Balancing all capable clients to the 5GHz radio to reduce noise by using the following settings (if your running v3.0 or above):
The 17dB value means clients will be load balanced is they are at 17dB (you can get top bit rate at 17dB), and setting the value to 0% means that if they are 5GHz capable they will join the 5GH radio.
Also look at smart roam to prevent sticky client issues:
Note: This can also be applied via ksp script also using the above mentioned format.
Here is the link to help you understand:
https://support.ruckuswireless.com/answers/000002277
Note: Client Admission control is something that may help in the future, but I would not be touching it at this stage as its experimental and introduces CPU load to the AP if you don't configure it correctly
Try the above and see what you get form there 🙂
I would do the following on the AP's to reduce some of the CPU load and tweak network performance:
set max-aid wlan0 100
set max-aid wlan32 100
then run this on each model of you AP:
rkscli: get rpmkey wifi0/mq-config
wifi0/mq-config = 4096 1536 640 128 768 512 128
OK
rkscli: get rpmkey wifi1/mq-config
wifi1/mq-config = 4096 1536 640 128 768 512 128
OK
then using the values above issue the following:
set rpmkey wifi0/mq-config = 4096 1536 100 128 768 512 128
set rpmkey wifi1/mq-config = 4096 1536 100 128 768 512 128
Note: As you can see the default unconnected cache on my AP is 640 per radio.
Essentially what I have done here is set the maximum association per radio to be 100 (connected client cache) and then applied the same value to the rpm (unconnected client cache).
By default the AP will dedicate resource to the unconnected client cache and the default value is 512 for each radio - so its wasting memory on clients that are not even connected 😞
By setting the rpm to be the same value as the max-aid what you get is a see-saw effect:
In a state where no clients are connected you get this:
connected cache = 0
unconnected cache = 100
and then when they connect you get this:
connected cache = 10
unconnected cache = 90
Essentially all you are doing here is allowing the AP to dedicate memory to the maximum of clients you want to per radio.
I would also issue the following:
set ofdm-only wlan0 enable
set bss-minrate wlan0 24000
set bss-minrate wlan32 24000
set proxy-arp wlan0 enable
set proxy-arp wlan32 enable
If you have multiple SSID's then you need to apply the above commands to the relevant SSID's i.e. set ofdm-only to 2.4GHz SSID and the set bss-minrate & proxy-arp to both 2.4 and 5GHz SSID's.
If you are using an SCG you can accomplish this by using a ksp script in the following format:
fw_version=3.1.1.0.348Note: save the above in a file as filename.ksp
model=all
set ofdm-only wlan0 enable
set bss-minrate wlan0 24000
set bss-minrate wlan32 24000
set proxy-arp wlan0 enable
set proxy-arp wlan32 enable
You can upload the ksp file from the Administration>Diagnostics>AP CLI Scripts
This can also be accomplished in the Edit WLAN Config>Advanced section:
Outside of the above you could look at load balancing clients and band Balancing all capable clients to the 5GHz radio to reduce noise by using the following settings (if your running v3.0 or above):
The 17dB value means clients will be load balanced is they are at 17dB (you can get top bit rate at 17dB), and setting the value to 0% means that if they are 5GHz capable they will join the 5GH radio.
Also look at smart roam to prevent sticky client issues:
set roam_factor wlan0 3
set roam_factor wlan32 3
reboot now
quit
Note: This can also be applied via ksp script also using the above mentioned format.
Here is the link to help you understand:
https://support.ruckuswireless.com/answers/000002277
Note: Client Admission control is something that may help in the future, but I would not be touching it at this stage as its experimental and introduces CPU load to the AP if you don't configure it correctly
Try the above and see what you get form there 🙂
Thanks for your information
For the last AP log I give out it is a test case that we want to know if all user is under web browsing or downloading traffic how many user can be handle on single AP.
it has few SSID that original has set 100 client per ssid per radio limit but during one of the test case. End user suspect the AP can't handle the client (>200) may be due to this setting and then they request to change the value to 500 and redo the test and provide the last AP log.
Actually the end user want to know the performance for the AP so that it can plan the density for the next phase.
The test result is
5G Client is 19 (open)
5G Client is 44 (WPA2)
2.4G Client is 11 (WPA2)
Then no more client can join this AP and the AP cpu is 100%
( the end user is active user doing some file download and also web browsing)
Below is the value I got from that AP
wifi0/mq-config='4096 1536 640 128 768 512 128'
wifi1/mq-config='2048 768 384 64 384 256 64'
Also the client association is show below
For the last AP log I give out it is a test case that we want to know if all user is under web browsing or downloading traffic how many user can be handle on single AP.
it has few SSID that original has set 100 client per ssid per radio limit but during one of the test case. End user suspect the AP can't handle the client (>200) may be due to this setting and then they request to change the value to 500 and redo the test and provide the last AP log.
Actually the end user want to know the performance for the AP so that it can plan the density for the next phase.
The test result is
5G Client is 19 (open)
5G Client is 44 (WPA2)
2.4G Client is 11 (WPA2)
Then no more client can join this AP and the AP cpu is 100%
( the end user is active user doing some file download and also web browsing)
Below is the value I got from that AP
wifi0/mq-config='4096 1536 640 128 768 512 128'
wifi1/mq-config='2048 768 384 64 384 256 64'
Also the client association is show below
