topic eap request-timeout 60; Good or Bad ? in Wireless https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262291#M50359 <HTML><HEAD></HEAD><BODY><P>Thank's Steve. That is also what I have concluded so far. </P><P></P><P>One thing that bugs me is that the article you mention states that no more than 5 secunds makes sense. But the default on newer generation WLC software is 30 secunds?</P></BODY></HTML> Tue, 30 Apr 2013 19:32:43 GMT sin 2013-04-30T19:32:43Z eap request-timeout 60; Good or Bad ? https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262289#M50357 <P>I have a device manufacture there are requesting the following change on a customer's WLC 5508. </P><P></P><P style="margin: 0px 0px 10px; font-family: 'Lucida Grande', Geneva, Arial, Verdana, sans-serif; font-size: 13px; background-color: #ffffff;"><STRONG style="font-family: 'courier new', courier; ">config advanced eap identity-request-timeout 60</STRONG></P><P style="margin: 0px 0px 10px; font-family: 'Lucida Grande', Geneva, Arial, Verdana, sans-serif; font-size: 13px; background-color: #ffffff;"><STRONG style="font-family: 'courier new', courier; ">config advanced eap request-timeout 60</STRONG></P><P> I have studied many guides but I can't find out if there is a down-side to setting the timeout this high.</P><P></P><P>Could it result in slow roaming or reauthentication if there is a connection error? </P><P></P><P>The customer have large areas with high client density and some outdoor areas with low client density.</P> Sun, 04 Jul 2021 07:00:24 GMT https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262289#M50357 sin 2021-07-04T07:00:24Z eap request-timeout 60; Good or Bad ? https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262290#M50358 <HTML><HEAD></HEAD><BODY><P>The issue with setting the timeout that high is interruption of service if the client doesn't respond.</P><P></P><P>Take a look at this doc that goes over this.</P><P></P><P><A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-12110">https://supportforums.cisco.com/docs/DOC-12110</A></P><P></P><P></P><P></P><P>HTH, <BR />Steve <BR /> <BR />------------------------------------------------------------------------------------------------ <BR />Please remember to rate useful posts, and mark questions as answered</P></BODY></HTML> Tue, 30 Apr 2013 19:28:46 GMT https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262290#M50358 Stephen Rodriguez 2013-04-30T19:28:46Z eap request-timeout 60; Good or Bad ? https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262291#M50359 <HTML><HEAD></HEAD><BODY><P>Thank's Steve. That is also what I have concluded so far. </P><P></P><P>One thing that bugs me is that the article you mention states that no more than 5 secunds makes sense. But the default on newer generation WLC software is 30 secunds?</P></BODY></HTML> Tue, 30 Apr 2013 19:32:43 GMT https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262291#M50359 sin 2013-04-30T19:32:43Z eap request-timeout 60; Good or Bad ? https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262292#M50360 <HTML><HEAD></HEAD><BODY><P>yeah, when I wrote that it was designed more around voice deployments, and to fix the troubleshooting guide that showed the values all pushed to max.</P><P></P><P>Generally 5sec is a good maximum, as most things will reply within that time frame, but it's not so long as to cause an interruption if the device doesn't respond</P><P></P><P></P><P>HTH, <BR />Steve <BR /> <BR />------------------------------------------------------------------------------------------------ <BR />Please remember to rate useful posts, and mark questions as answered</P></BODY></HTML> Tue, 30 Apr 2013 19:37:06 GMT https://community.cisco.com/t5/wireless/eap-request-timeout-60-good-or-bad/m-p/2262292#M50360 Stephen Rodriguez 2013-04-30T19:37:06Z