EAP Timers Best Practice

[MuhammadHasan]

Hi Meraki Community,

I just want to ask about EAP timer settings and the best and most recommended Practice. Currently, we have below settings and Users are experiencing wireless issues as these timers are crossing values. Please suggest.

[Rasmus Hoffmann Birkelund]

I don't have the answer, as this is something I've been researching myself. But I've found this, which I've been leaning myself towards.

https://community.cisco.com/t5/wireless-mobility-knowledge-base/eap-timers-on-wireless-lan-controllers/ta-p/3122477

[aleabrahao]

In fact, there is no best practice, in some cases adjustments are necessary (very rarely), but in practice what is configured by default is always used.

[Philip D'Ath]

I might have to adjust these once in every 1000 installs. Your deployment is not likely to need these changed.

Is the RTT for your RADIUS server under 2s? If so - you don't need to touch anything.

"Currently, we have below settings and Users are experiencing wireless issues as these timers are crossing values"

What is the specific issue you are facing?

[Raphael_L]

Meraki defaults are just fine but the thing that I dislike is that the default doesn't match the timers from the "Aironet/Catalyst" world. I like to have things setup the same everywhere...

[Alejandro Flores]

The default EAP timers works fine generally speaking. It depends on your topology, where is your RADIUS connected, on premise or in the Cloud? If the answer is Cloud or across a VPN tunnel, it would be good to check the round trip time and increase the timeouts a lit bit.
Nevertheless your wireless health connection is Excellent, the clients having the connection problems might be not RADIUS timers related. A single client attempting to connect located far from any AP might cause the dashboard health timers to increase.