ā04-16-2018 02:50 PM
Solved! Go to Solution.
ā04-16-2018 06:35 PM
The AP230 is able to support that amount of clients. In our testing the 6.5 series firmware is the most efficient and stable. We have had great performance improvements using by disabling the QoS engine in the CLI of the AP. The command is "no qos enable no-prompt". Command to see state is "show qos".
With the QOS engine disabled we have had nearly 200 clients (100 per radio) on older AP330s and the APs not even breaking a sweat. Enable QoS engine, CPU spikes to 100% - to the point were AP is unresponsive.
Doing "no qos enable no-prompt" from the CLI is equivalent in HM Classic to "Turbo Mode" - available in the Monitor pane when you select one AP capable of 802.11ac. However doing it that way - doesn't scale, and it won't save to memory. We created a CLI Supplicant and applied it that way to our 17,000 access points.
Note even though "Turbo Mode" states that it operates on APs capable of 802.11ac - we have seen performance improvements across the board, on all AP products including those that do not support 802.11ac (AP330s).
Note that in our testing, it did not matter what QoS policies you actually used, merely having the engine on reduced performance.
We did our analysis by enabling SNMP on the AP and using third party tools to monitor and graph CPU, client account, and memory on select APs - and comparing with and without the QoS engine disabled.
ā04-16-2018 06:35 PM
The AP230 is able to support that amount of clients. In our testing the 6.5 series firmware is the most efficient and stable. We have had great performance improvements using by disabling the QoS engine in the CLI of the AP. The command is "no qos enable no-prompt". Command to see state is "show qos".
With the QOS engine disabled we have had nearly 200 clients (100 per radio) on older AP330s and the APs not even breaking a sweat. Enable QoS engine, CPU spikes to 100% - to the point were AP is unresponsive.
Doing "no qos enable no-prompt" from the CLI is equivalent in HM Classic to "Turbo Mode" - available in the Monitor pane when you select one AP capable of 802.11ac. However doing it that way - doesn't scale, and it won't save to memory. We created a CLI Supplicant and applied it that way to our 17,000 access points.
Note even though "Turbo Mode" states that it operates on APs capable of 802.11ac - we have seen performance improvements across the board, on all AP products including those that do not support 802.11ac (AP330s).
Note that in our testing, it did not matter what QoS policies you actually used, merely having the engine on reduced performance.
We did our analysis by enabling SNMP on the AP and using third party tools to monitor and graph CPU, client account, and memory on select APs - and comparing with and without the QoS engine disabled.