<?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 APs not joining controller in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704782#M61071</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Someone resolved this issue? I have the same problems. Im using 6.0.196.0 and all works fine, but when i upgraded to 6.0.202.0 APs can't join wlc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Jan 2012 12:39:02 GMT</pubDate>
    <dc:creator>Anton Rybak</dc:creator>
    <dc:date>2012-01-16T12:39:02Z</dc:date>
    <item>
      <title>APs not joining controller</title>
      <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704778#M61067</link>
      <description>&lt;P&gt;I upgraded a controller yesterday 5508 it went from a low code version 6.x to 6.0.196.0 then to 7.0.116.0. However although all the access points joined code 6.0.196.0 they refused to join 7.0.116.0. The aps are all 1242s.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The country codes etc were all fine so I do not understand what was going on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discovery Request from 10.0.0.95:55080&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask0: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask0: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discovery Response sent to 10.0.0.95:55080&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Discovery Request from 10.0.0.95:55080&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Discovery Response sent to 10.0.0.95:55080&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discovery Request from 10.0.1.232:20023&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discovery Response sent to 10.0.1.232:20023&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask0: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Discovery Request from 10.0.1.232:20023&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Discovery Response sent to 10.0.1.232:20023&lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:46.516: 00:3a:99:db:fa:10 DTLS connection not found, creating new connection for 10:0:0:101 (55079) 10:0:1:45 (5246)&lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:101/55079)&lt;BR /&gt;*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 No entry exists for AP (10:0:0:101/55079)&lt;BR /&gt;*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 No entry exists in database&lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:47.759: 00:3a:99:db:fa:a0 Discovery Request from 10.0.0.184:55084&lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:47.759: 00:3a:99:db:fa:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask0: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask0: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Response sent to 10.0.0.184:55084&lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Request from 10.0.0.184:55084&lt;/P&gt;&lt;P&gt;*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Response sent to 10.0.0.184:55084&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discovery Request from 10.0.1.239:20032&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discovery Response sent to 10.0.1.239:20032&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask0: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Discovery Request from 10.0.1.239:20032&lt;/P&gt;&lt;P&gt;*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Discovery Response sent to 10.0.1.239:20032&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.222: 00:13:c3:e1:4d:80 Discovery Request from 10.0.1.230:20027&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.222: 00:13:c3:e1:4d:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discovery Response sent to 10.0.1.230:20027&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask0: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discovery Request from 10.0.1.230:20027&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask1: Jun 26 16:07:52.224: 00:13:c3:e1:4d:80 Discovery Response sent to 10.0.1.230:20027&lt;/P&gt;&lt;P&gt;*spamApTask5: Jun 26 16:07:52.267: 00:3a:99:da:c7:70 DTLS connection not found, creating new connection for 10:0:0:181 (34152) 10:0:1:45 (5246)&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discovery Request from 10.0.0.182:55099&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask0: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'&lt;BR /&gt;*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discovery Response sent to 10.0.0.182:55099&lt;/P&gt;&lt;P&gt;*spamApTask0: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discarding discovery request in LWAPP from AP supporting CAPWAP &lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Discovery Request from 10.0.0.182:55099&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0&lt;BR /&gt;*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Discovery Response sent to 10.0.0.182:55099&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.306: 00:3a:99:db:f2:40 DTLS connection not found, creating new connection for 10:0:0:100 (55069) 10:0:1:45 (5246)&lt;/P&gt;&lt;P&gt;*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:181/34152)&lt;BR /&gt;*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 No entry exists for AP (10:0:0:181/34152)&lt;BR /&gt;*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 No entry exists in database&lt;/P&gt;&lt;P&gt;*spamApTask1: Jun 26 16:07:52.501: 00:3a:99:db:f2:40 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:100/55069)&lt;BR /&gt;*spamApTask1: Jun 26 16:07:52.502: 00:3a:99:db:f2:40 No entry exists for AP (10:0:0:100/55069)&lt;BR /&gt;*spamApTask1: Jun 26 16:07:52.502: 00:3a:99:db:f2:40 No entry exists in database&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:29:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704778#M61067</guid>
      <dc:creator>Peter Nugent</dc:creator>
      <dc:date>2021-07-04T03:29:56Z</dc:date>
    </item>
    <item>
      <title>APs not joining controller</title>
      <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704779#M61068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any chance you could see what the console of an AP is saying?&lt;/P&gt;&lt;P&gt;Did you just downgrade, or do you at least have your APs functional on some other WLC on 6.x for the time being?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no bug that comes to mind regarding upgrading what would cause this.... so there must be something going on...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On a side note, I'm pretty sure yesterday was not June 26th....&amp;nbsp; Whats up with your date? Is the year at least correct on that WLC..?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Jul 2011 01:46:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704779#M61068</guid>
      <dc:creator>weterry</dc:creator>
      <dc:date>2011-07-30T01:46:17Z</dc:date>
    </item>
    <item>
      <title>APs not joining controller</title>
      <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704780#M61069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Unfortunately not I was pushed for time so downgraded to 6.0.196.0, checked everything could not see anything obvious. I guess its one of those mysteries if I ever get back to that client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was a little bit of a strange network, but weird why its perfect on v6.x but does not like v7.x&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Jul 2011 17:07:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704780#M61069</guid>
      <dc:creator>Peter Nugent</dc:creator>
      <dc:date>2011-07-30T17:07:09Z</dc:date>
    </item>
    <item>
      <title>APs not joining controller</title>
      <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704781#M61070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Something "weird" is on the newest 7.0.X.&amp;nbsp; Here's my situation: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; It doesn't happen to all new APs.&amp;nbsp; When I mean "new", I mean out from a box including APs from RMA.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; I've seen this in 1240, 1250, 1140.&amp;nbsp; Haven't seen it on a 3500. &lt;/P&gt;&lt;P&gt;3.&amp;nbsp; Here's how it goes ... When the AP, fresh from a box, connects to the networks, sees the WLC/WiSM and downloads the full IOS (OK so far).&amp;nbsp; After the reboot the AP in question loads the new IOS and shows up in the WLC/WiSM.&amp;nbsp; When I check CDP neighbors, NOTHING.&amp;nbsp; What the ... ?&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; Go to the switch and do command "sh cdp neighbor" and what do I get?&amp;nbsp; NOTHING. &lt;/P&gt;&lt;P&gt;5.&amp;nbsp; Check PoE and show that it's IEEE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For unknown reason, APs in this "trance" shuts off the CDP.&amp;nbsp; I currently have a Cisco TAC Case trying to iron out this "feature".&amp;nbsp; Doesn't appear on the 7.0.96.0 but happens to the newer one. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 05:56:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704781#M61070</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2011-08-01T05:56:58Z</dc:date>
    </item>
    <item>
      <title>APs not joining controller</title>
      <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704782#M61071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Someone resolved this issue? I have the same problems. Im using 6.0.196.0 and all works fine, but when i upgraded to 6.0.202.0 APs can't join wlc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2012 12:39:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704782#M61071</guid>
      <dc:creator>Anton Rybak</dc:creator>
      <dc:date>2012-01-16T12:39:02Z</dc:date>
    </item>
    <item>
      <title>APs not joining controller</title>
      <link>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704783#M61072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Every situation is different.... you need to consol into the ap and post the output so we can see what happens when the ap boots up all the wasy through the discovery process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2012 12:41:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-not-joining-controller/m-p/1704783#M61072</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2012-01-16T12:41:18Z</dc:date>
    </item>
  </channel>
</rss>

