This Article Applies to:

Software controller, OC200, OC300, EAPs

 

Issue Description/Phenomenon:

 

In scenarios where multiple EAPs are managed with controllers, you may see error messages in the log such as [Failed] XXX failed to connected to EAP with SSID "XXX" on channel XX because WPA Authentication times out/failed.

Or just like the below image:

 

 

 

Troubleshooting:

 

The WPA Authentication Timeout/Failed may be prompted on the Omada SDN Controller in two situations:

• There is a packet loss in the wireless associated handshake process, which causes the handshake process to timeout
• The wireless password is input wrong when connecting to the SSID on the wireless client.

 

In brief, it is simply the client taking too long or not fully completing authentication at one stage, likely due to the signal strength. For example, you will get it when your phone cannot join the WIFI, when you are out of WIFI range. As a rule, these error messages do not affect actual use.

 

 

Suggestions:

 

1. Please ensure your wireless clients can get a strong signal strength from the SSID, and the wireless password is input correctly first.

 

 

 

  

 

 

 

2. If the signal strength is strong enough and the password is input correctly, please check and optimise the wireless environment of your current device, you can adjust the placement of the EAP to test it.

You can download WiFi Analyzer on your mobile phone to check the wireless environment.

 

 

3. Normally, 2.4G channels are very congested compared to 5G, and if the client keeps trying to connect to the 2.4G SSID, it may also cause frequent WPA Authentication Timeouts.

It is recommended to turn off 2.4G and only turn on 5G band for testing optimization.

 

 

4. You can also change the channel and the channel width of this EAP to have a try.

For Example:

• For the 2.4G, the channel is 1, the channel width is 20 Mhz.
• For the 5G, the channel is 36, channel width is 20Mhz.

   Here is the related FAQ for the reference:  How to optimize wireless performance of EAP products

 

 

5. Sometimes, due to problems with the client mechanism and the wide range of signals broadcast by the EAP, the client may choose to connect to the SSID of an EAP that is far away, but often this time the client can get access to the network but it is unstable, which will cause the client to authenticate with the EAP frequently.

 

It is recommended that the Tx Power of the EAP be adjusted appropriately. In the case of multiple EAPs in an area, the Tx Power can be set to Medium or adjusted to the Low.

 

 

      

 

 

 

6. Please make sure your Omada Controller and EAPs are all up to date.

 

 

 Related Post:

Device failing to connect to EAP 610: WPA Authentication times out/failed