cancel
Showing results for 
Search instead for 
Did you mean: 

Best practices timeout dot1x

stefano_costant
New Contributor II

Hello everybody, we are looking for bet practices about dot1x timeouts. quiet-period, supplicant, tx-period, max-reauth-req. We'd like to avoid fail of auth, and even not to have too long timers 🙂 Suggestion?

4 REPLIES 4

Mayank
RUCKUS Team Member

Chandini
RUCKUS Team Member

Hi Stefano_Costant,

Thank you for reaching us

Also, feel free to refer to the article and link below.

Thank you 

stefano_costant
New Contributor II

Thanks guys, i've already studied all the docs, i just need some advice on best practices. Any suggestion? Tks

Chandini
RUCKUS Team Member

Hi Stefano_Costant,

Thank you for reaching us

To configure 802.1X authentication and optimize timeout parameters—minimizing authentication failures and avoiding excessive delays—consider the following best practices. Please note that these recommendations may vary depending on your specific network environment and deployment requirements.

Quiet Period: Defines the time the device waits before reattempting authentication after a failed attempt.

  • device(config-authen)# dot1x timeout quiet-period 30

A value of 30 seconds is a good starting point. Adjust based on your network’s retry strategy.

TX Period: Specifies the interval between retransmissions of EAP-Request/Identity frames to the client.

  • device(config-authen)# dot1x timeout tx-period 30

30 seconds is recommended to ensure timely retries without unnecessary delays. Adjust based on your network.

Supplicant Timeout: Controls how long the device waits before retransmitting RADIUS EAP-Request/Challenge frames.

  • device(config-authen)# dot1x timeout supplicant 30

Setting this to 30 seconds balances responsiveness with avoiding premature timeouts. Adjust based on your network.

Max Reauth Requests: This parameter sets the maximum number of times EAP-Request/Identity frames are sent for reauthentication after the first authentication attempt.

  • device(config-authen)# dot1x max-reauth-req 4

A value of 4 is typically sufficient to ensure multiple attempts for reauthentication without causing excessive retries. Adjust based on your network.

Max Requests: Defines how many times EAP-Request/Challenge frames are retransmitted when no EAP Response/Identity is received.

  • device(config-authen)# dot1x max-req 3

Setting this to 3 ensures the device makes reasonable attempts before marking authentication as failed. Adjust based on your network.

By tuning these parameters, you can enhance the reliability and efficiency of the 802.1X authentication process. Be sure to adjust values based on your specific network environment and performance requirements.

Thank you