<?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 Re: Force AP to register with another controller in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/4471970#M233596</link>
    <description>&lt;P&gt;The solution provided by Scott Fella worked for me as well. Setting the WLC as Master Controller helped to move the APs.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Sep 2021 11:44:25 GMT</pubDate>
    <dc:creator>Comm Team</dc:creator>
    <dc:date>2021-09-23T11:44:25Z</dc:date>
    <item>
      <title>Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701520#M61073</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;I have 2 WLCs. One with newer IOS version than the other. All of APs are currently register with older IOS version WLC and of course have the older IOS version. My goal is to force all the APs re-download and re-register with newer IOS WLC. If I don't free up the WLC before IOS upgrade; wireless network will be interrupt and of course I would like to avoid as much as possible. I tried these:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On each AP and under High Availabilty tab; I changed the Primary Controller to the newer IOS WLC ip address; then reset or clear all the configuration; but after came up; APs still register to the older IOS controller.&lt;/P&gt;&lt;P&gt;On DHCP scope option 43; I only have the newer IOS WLC ip address and then reset the AP; it does not work as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess APs refer the controller that has same version of IOS; regardless of the High Availability setting or the ip address of the controller in the DHCP scope.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thought?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:29:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701520#M61073</guid>
      <dc:creator>xuanhuymai</dc:creator>
      <dc:date>2021-07-04T03:29:50Z</dc:date>
    </item>
    <item>
      <title>Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701521#M61074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; If you clear the config from the AP, it wont have the high availability config anymore (but then Option 43 should be helping it out).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyhow, the best approach is set the primary name and IP of the WLC you want, and either turn on AP fallback, or reboot the AP. If that AP is not joining the Primary WLC, then you have some kind of problem....&amp;nbsp; Because that is as easy as the procedure goes...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps you could console into an AP and record what output happens when you do this?&lt;/P&gt;&lt;P&gt;And better yet, if I were supporting this, I'd be looking to see "debug ip udp" from the console of the AP to see exactly what packets are sent and recieved (a packet capture from the AP switchport would work just as well).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2011 22:10:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701521#M61074</guid>
      <dc:creator>weterry</dc:creator>
      <dc:date>2011-07-28T22:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701522#M61075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is pretty simple. A couple other things is to make sure you don't have master controller enabled on the WLC  with the old code.  Verify that your mobility between the two WLC is up, AP fallback on both WLC is enabled. If everything is setup as mentioned, change the primary WLC on the AP to the  WLC with the new code and either wait a couple minutes or just reboot the AP. You do not need option 43 or dns for this. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 31 Jul 2011 18:09:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701522#M61075</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2011-07-31T18:09:05Z</dc:date>
    </item>
    <item>
      <title>Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701523#M61076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;On each AP and under High Availabilty tab; I changed the Primary Controller to the newer IOS WLC ip address&lt;/PRE&gt;&lt;/P&gt;&lt;P&gt;Only the IP address?&amp;nbsp; Hmmm ... Are you, by any chance, running 4.X firmware? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 05:17:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701523#M61076</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2011-08-01T05:17:15Z</dc:date>
    </item>
    <item>
      <title>Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701524#M61077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Leolaohoo,&lt;/P&gt;&lt;P&gt;I changed the ip address and Primary controller name under High Availability; but it did not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, with Scott Fella's method, it works just fine. I just need to set the newer code controller as master, then reset APs in other controllers. No downtime needed. Thank Scott.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 13:52:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701524#M61077</guid>
      <dc:creator>xuanhuymai</dc:creator>
      <dc:date>2011-08-01T13:52:49Z</dc:date>
    </item>
    <item>
      <title>Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701525#M61078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One thing to note if the AP's didn't join unless you set the WLC as master WLC, is to make sure the Primary Controller name is correct.&amp;nbsp; This entry is case sensitive.&amp;nbsp; Glad you got it working.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 13:56:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/1701525#M61078</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2011-08-01T13:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: Force AP to register with another controller</title>
      <link>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/4471970#M233596</link>
      <description>&lt;P&gt;The solution provided by Scott Fella worked for me as well. Setting the WLC as Master Controller helped to move the APs.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Sep 2021 11:44:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/force-ap-to-register-with-another-controller/m-p/4471970#M233596</guid>
      <dc:creator>Comm Team</dc:creator>
      <dc:date>2021-09-23T11:44:25Z</dc:date>
    </item>
  </channel>
</rss>

