Client Association Failure Reason:Unknown ReasonCode: 102

[M. Said Temelli]

Hi,

We are using WLC 8510 with 8.0.110.0 code, 1131,1040, 1600, 1700, 2700, 3700 indoor APs, ISE 1.3.0.876. We have an eduroam SSID with [WPA + WPA2][Auth(802.1X + CCKM)] an a guest SSID with zero authentication. Both WLANs are using FlexConnect Local Switching. We have an association problem that is logged as :

Client Association Failure: MACAddress:80:1f:02:**:**:** Base Radio MAC:f4:4e:05:**:**:** Slot: 0 User Name:UNKNOWN IP Addr: unknown Reason:Unknown ReasonCode: 102

We take this log thousands of times in a day. It occurs in both SSID's and every models of APs we use. I searched the log at internet for months long and I could not find even one person who troubles with this problem. It is interesting that any of Cisco documents doesn't even mention about this case. I don't know maybe our WLC creates this log for itself only I'm really stuck in this situation and can't find any thing more to try. This affects our wireless service quality too bad.  Please, I need help immediately!

WLAN configs are attached.

Thank you.

[Rasika Nayanajith]

I would test this without CCKM, that is Auth (802.1X)  & see if this is CCKM related.

Is that possible to test ?

Rasika

[M. Said Temelli]

Now, there are 6K clients connected so I cannot try anything. But I will try it evening.

Thank you.

[patoberli]

Cisco released http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn80mr1dot5.html 8.0.115.0. Can you check if the issue is resolved in that release?

I also had the issue with 8.0.110.0 and had to downgrade to 7.6.130.0 to get eduroam working again. Same with a second university.

[M. Said Temelli]

It is still the same. Nothing has changed :( Anything else?

[mattlewis1]

We have a similar setup with a 5508 WLC and around 50 3502 access points on 8.0.120

The issue occurred only at one location (I have other locations with similar configurations) when I turned off Guest Wireless WLAN. This caused the WPA + WPA2 based SSID to no longer authenticate correctly. Doing the research like yourself, I only found one other post from Jonathan Mumm's blog, which just said to "Reboot" it. Which we did, and all users were able to authenticate again without any issues. Re-enabling the guest wireless WLAN did not fix the issue and I did notice that some devices were still connecting successfully, just not on certain Access Points. We didn't have time to investigate further due to production restraints, but I wanted to pass this along.

[Freerk Terpstra]

Besides doing a software upgrade of the WLC I would also investigate if it is possible to disable WPA support at all. Having WPA and WPA2 enabled on the same network can really confuse certain clients causing weird issues.

Please rate useful posts... :-)

[M. Said Temelli]

Thank you for your answer. Actually we were having this trouble about a year ago. Since we couldn't find a solid solution for this error, we completely abandoned the Flexconnect architecture. Now we use local mode and everything is just simple and fine. I recommend everyone I see not to use Flexconnect as long as it is really required :)