<?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 LAPs joing the wrong controller in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074672#M148906</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so, WLC discovery doesn't work like that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you set option 43, DNS, L2 broadcast etc, the AP learns about all the WLC in the mobility group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The AP should then join the WLC with the greatest excess availability.&amp;nbsp; Once the AP has joined, you can then set the Primary/Secondary/Tertiary, and if AP fallback is enabled the AP will move to it's configured primary controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH, &lt;BR /&gt;Steve &lt;BR /&gt; &lt;BR /&gt;------------------------------------------------------------------------------------------------ &lt;BR /&gt;Please remember to rate useful posts, and mark questions as answered&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Nov 2012 14:17:33 GMT</pubDate>
    <dc:creator>Stephen Rodriguez</dc:creator>
    <dc:date>2012-11-07T14:17:33Z</dc:date>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074668#M148901</link>
      <description>&lt;P&gt;We have 3 5508 WLCs&amp;nbsp; (A, B, &amp;amp; C) and several LAPs (1140, 3500, 3600). The APs learn the controllers IP addresses through DHCP Option 43.&amp;nbsp; When we setup a new site we put the IP address of the controller we want the AP to join first.&amp;nbsp; Lately, I've noticed that regardless of which WLC IP I put first when I setup Option 43 the LAPs are always joining a particular controller. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Master Controller Mode is not set on any controller.&lt;/P&gt;&lt;P&gt;All controllers are running version 7.3.101.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else seen something like this?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074668#M148901</guid>
      <dc:creator>JASON SIMMONS</dc:creator>
      <dc:date>2021-07-04T05:59:33Z</dc:date>
    </item>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074669#M148902</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; This behavior started happening before I upgraded to version 7.3.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 00:15:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074669#M148902</guid>
      <dc:creator>JASON SIMMONS</dc:creator>
      <dc:date>2012-11-07T00:15:17Z</dc:date>
    </item>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074670#M148903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you enable Primary/Secondary/Tertiary Controller details?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 02:45:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074670#M148903</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2012-11-07T02:45:55Z</dc:date>
    </item>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074671#M148904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This happens before I can set a Primary.&amp;nbsp; This happens with brand new out of box LAPs&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 03:03:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074671#M148904</guid>
      <dc:creator>JASON SIMMONS</dc:creator>
      <dc:date>2012-11-07T03:03:43Z</dc:date>
    </item>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074672#M148906</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so, WLC discovery doesn't work like that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you set option 43, DNS, L2 broadcast etc, the AP learns about all the WLC in the mobility group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The AP should then join the WLC with the greatest excess availability.&amp;nbsp; Once the AP has joined, you can then set the Primary/Secondary/Tertiary, and if AP fallback is enabled the AP will move to it's configured primary controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH, &lt;BR /&gt;Steve &lt;BR /&gt; &lt;BR /&gt;------------------------------------------------------------------------------------------------ &lt;BR /&gt;Please remember to rate useful posts, and mark questions as answered&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 14:17:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074672#M148906</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2012-11-07T14:17:33Z</dc:date>
    </item>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074673#M148908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;The AP should then join the WLC with the &lt;SPAN style="text-decoration: underline;"&gt;greatest excess availability&lt;/SPAN&gt;.&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;Greatest excess availibility, meaning the controller with the most available licenses?&amp;nbsp; If that is true, it makes sense why the LAPs initially join that controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for clarifying this process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 15:01:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074673#M148908</guid>
      <dc:creator>JASON SIMMONS</dc:creator>
      <dc:date>2012-11-07T15:01:28Z</dc:date>
    </item>
    <item>
      <title>LAPs joing the wrong controller</title>
      <link>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074674#M148909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From what I have seen, the new AP always join the least busy controller (lowest number of APs) in the mobillity group first.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 19:53:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/laps-joing-the-wrong-controller/m-p/2074674#M148909</guid>
      <dc:creator>zhenningx</dc:creator>
      <dc:date>2012-11-07T19:53:37Z</dc:date>
    </item>
  </channel>
</rss>

