Controller Based WLANs

 View Only
last person joined: one year ago 

APs, Controllers, VIA
Back to Library

Why is Captive Portal Wait Logon wait page displayed even when the controller CPU usage is low? 

Jul 04, 2014 01:48 PM

Question:  Why is Captive Portal Wait Logon wait page displayed even when the controller CPU usage is low?

 

Product and Software: This article applies to all Aruba controllers and any ArubaOS 3.3.1 code older than 3.3.1.28 or any ArubaOS 3.3.2 code older than 3.3.2.14.

When a controller has been running for a long time, you may see that all of the captive portal clients always get CP logon wait page even when the controller CPU usage is much lower than the configured "logon wait CPU utilization threshold" under the CP authentication profile.

#show aaa authentication captive-portal default

Captive Portal Authentication Profile "default"
-----------------------------------------------
Parameter                                    Value
---------                                    -----
Default Role                                 guest
Server Group                                 default
Redirect Pause                               10 sec
..................
Logon wait minimum wait                      5 sec
Logon wait maximum wait                      10 sec
logon wait CPU utilization threshold         60 %
Max Authentication failures                  0
Show FQDN                                    Disabled
..........................

This problem is caused by a bug that is triggered when the CPU idle counter is overflowed. You may see this problem when the controller has been running for a long time.

This bug has been fixed in ArubaOS 3.3.1.28 and 3.3.2.14. The best solution is to upgrade to the latest 3.3.1 or 3.3.2 patch.

 

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.