Security

last person joined: 23 hours ago 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

Effects of changing the User Idle Timeout

This thread has been viewed 5 times

  • 1.  Effects of changing the User Idle Timeout

    Posted Jun 22, 2015 07:21 PM

    There is a mutiny brewing.  We are using the default idle timeout (5 minutes). Devices that are going to sleep are having to go back through the Captive Portal.  We are having the users enter an email address and they are getting tired of this.

    What performance impact would there be if I increased the idle timeout?

    During the day we have anywhere from 1000 to 1250 devices connected to a 3600 controller.

     



  • 2.  RE: Effects of changing the User Idle Timeout

    EMPLOYEE
    Posted Jun 22, 2015 07:57 PM
    There is a user idle timeout in the captive portal authentication profile. Use that instead...


  • 3.  RE: Effects of changing the User Idle Timeout

    EMPLOYEE
    Posted Jun 23, 2015 02:18 AM

    make sure the idle timeout is less than your dhcp lease time.



  • 4.  RE: Effects of changing the User Idle Timeout
    Best Answer

    EMPLOYEE
    Posted Jun 23, 2015 08:18 AM
    stephencm@cos.edu wrote:

    There is a mutiny brewing.  We are using the default idle timeout (5 minutes). Devices that are going to sleep are having to go back through the Captive Portal.  We are having the users enter an email address and they are getting tired of this.

    What performance impact would there be if I increased the idle timeout?

    During the day we have anywhere from 1000 to 1250 devices connected to a 3600 controller.

     

    No significant performance impact, but your user table will be inflated with devices that have been gone for hours, so you will never get a real idea of how many users are really connected.  Use the user-idle-timeout parameter in the captive portal profile (http://www.arubanetworks.com/techdocs/ArubaOS_64x_WebHelp/Web_Help_Index.htm#ArubaFrameStyles/1CommandList/aaa_authentication_captive.htm?Highlight=user-idle-timeout) , instead of the global user idle-timeout so that the "inflation" only happens on your Captive Portal SSID.

     



  • 5.  RE: Effects of changing the User Idle Timeout

    Posted Jun 23, 2015 07:18 PM

    Thanks for the information!