<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic We have a similar setup with in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656789#M164400</link>
    <description>&lt;P&gt;We have a similar setup with a 5508 WLC and around 50 3502 access points on 8.0.120&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jul 2016 17:01:38 GMT</pubDate>
    <dc:creator>mattlewis1</dc:creator>
    <dc:date>2016-07-26T17:01:38Z</dc:date>
    <item>
      <title>Client Association Failure Reason:Unknown ReasonCode: 102</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656784#M164395</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;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&amp;nbsp;[WPA + WPA2][Auth(802.1X + CCKM)] an a guest SSID with zero authentication. Both WLANs are using FlexConnect Local Switching.&amp;nbsp;We have an association problem that is logged as :&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;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&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;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 &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; I'm really stuck in this situation and can't find any thing more to try. This affects our wireless service quality too bad.&amp;nbsp;&amp;nbsp;Please, I need help immediately!&lt;/P&gt;&lt;P&gt;WLAN configs are attached.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 10:02:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656784#M164395</guid>
      <dc:creator>M. Said Temelli</dc:creator>
      <dc:date>2021-07-05T10:02:52Z</dc:date>
    </item>
    <item>
      <title>I would test this without</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656785#M164396</link>
      <description>&lt;P&gt;I would test this without CCKM, that is Auth (802.1X) &amp;nbsp;&amp;amp; see if this is CCKM related.&lt;/P&gt;&lt;P&gt;Is that possible to test ?&lt;/P&gt;&lt;P&gt;Rasika&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2015 05:40:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656785#M164396</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2015-04-27T05:40:38Z</dc:date>
    </item>
    <item>
      <title>Now, there are 6K clients</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656786#M164397</link>
      <description>&lt;P&gt;Now, there are 6K clients connected so I cannot try anything. But I will try it evening.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2015 08:34:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656786#M164397</guid>
      <dc:creator>M. Said Temelli</dc:creator>
      <dc:date>2015-04-27T08:34:24Z</dc:date>
    </item>
    <item>
      <title>It is still the same. Nothing</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656787#M164398</link>
      <description>&lt;P&gt;It is still the same. Nothing has changed &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; Anything else?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2015 11:09:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656787#M164398</guid>
      <dc:creator>M. Said Temelli</dc:creator>
      <dc:date>2015-04-28T11:09:07Z</dc:date>
    </item>
    <item>
      <title>Cisco released http://www</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656788#M164399</link>
      <description>&lt;P&gt;Cisco released &lt;A href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn80mr1dot5.html"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn80mr1dot5.html&lt;/A&gt; 8.0.115.0. Can you check if the issue is resolved in that release?&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2015 14:53:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656788#M164399</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2015-06-08T14:53:46Z</dc:date>
    </item>
    <item>
      <title>We have a similar setup with</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656789#M164400</link>
      <description>&lt;P&gt;We have a similar setup with a 5508 WLC and around 50 3502 access points on 8.0.120&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2016 17:01:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656789#M164400</guid>
      <dc:creator>mattlewis1</dc:creator>
      <dc:date>2016-07-26T17:01:38Z</dc:date>
    </item>
    <item>
      <title>Besides doing a software</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656790#M164401</link>
      <description>&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Please rate useful posts... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Jul 2016 21:42:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656790#M164401</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2016-07-30T21:42:42Z</dc:date>
    </item>
    <item>
      <title>Thank you for your answer.</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656791#M164402</link>
      <description>&lt;P&gt;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 &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2016 13:10:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failure-reason-unknown-reasoncode-102/m-p/2656791#M164402</guid>
      <dc:creator>M. Said Temelli</dc:creator>
      <dc:date>2016-08-05T13:10:07Z</dc:date>
    </item>
  </channel>
</rss>

