Controller Based WLANs

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

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.

 

Version History
Revision #:
1 of 1
Last update:
‎07-04-2014 10:48 AM
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.