cancel
Showing results for 
Search instead for 
Did you mean: 

Wireless Health - Failed Connections (Failure reason)

Just browsing

Wireless Health - Failed Connections (Failure reason)

We have configured 802.1X authentication for a corporate SSID. Wireless health shows that there are some Authentication failures. 

 

If shows that the authentication has failed along with some attributes and values. Is anyone have idea on this attributes?

 

(I need to know the highlighted fields)

type='802.1X auth fail'

num_eap='0'

associated='true'

radio='1'

vap='0'

 

Auth.PNG

 

 

5 REPLIES 5
Kind of a big deal

Re: Wireless Health - Failed Connections (Failure reason)

It usually means a device is failing to authenticate ...

 

This is common if it is for smart phones and the user changes their AD password and have not updated the password on their phone yet.

Head in the Cloud

Re: Wireless Health - Failed Connections (Failure reason)

Hi @Shawqy,

 

Do you have "WPA1 and WPA2" enabled on your SSID WPA encryption mode? If so, I would maybe try "WPA2 Only" and change the minimum bitrate to 24 Mbps (unless you have a need for lower).

 

Obviously the tale of caution applies; need to pre-check/pro-check any specific hardware after for connectivity.

 

Thank you,
Peter James

Getting noticed

Re: Wireless Health - Failed Connections (Failure reason)

"vap" is the virtual AP number. Look at your Wireless SSIDs Configuration overview and show all SSIDs. Reading from left to right they are vap=0, 1, 2, 3, etc

Just browsing

Re: Wireless Health - Failed Connections (Failure reason)

Thanks Peter. There is a requirement for Lower devices
Just browsing

Re: Wireless Health - Failed Connections (Failure reason)

Thanks for your response. Is there any idea of num_eap= value?
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.