<?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 Changing Wireless Controllers in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902007#M78092</link>
    <description>&lt;P&gt;I have a single WLC 5508 on my network at this time.&amp;nbsp; I have 108 access points all CAPWAP associated to it.&amp;nbsp; I am in the process of configuring two new 5508 controllers in a HA configuration.&amp;nbsp; The IP address of the primary will be the same as the IP of the current controller.&amp;nbsp; I use option 43 for the access points to find the controller IP in my DHCP server.&amp;nbsp; I want to make sure that I can get the access points to associate to the new controller correctly and to get them their configuration (flexconnect).&amp;nbsp; Is there a way to create a seed file with the names, IPs and AP type that I can load into the controller before putting it in production?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 11:44:57 GMT</pubDate>
    <dc:creator>tndmcclain</dc:creator>
    <dc:date>2021-07-05T11:44:57Z</dc:date>
    <item>
      <title>Changing Wireless Controllers</title>
      <link>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902007#M78092</link>
      <description>&lt;P&gt;I have a single WLC 5508 on my network at this time.&amp;nbsp; I have 108 access points all CAPWAP associated to it.&amp;nbsp; I am in the process of configuring two new 5508 controllers in a HA configuration.&amp;nbsp; The IP address of the primary will be the same as the IP of the current controller.&amp;nbsp; I use option 43 for the access points to find the controller IP in my DHCP server.&amp;nbsp; I want to make sure that I can get the access points to associate to the new controller correctly and to get them their configuration (flexconnect).&amp;nbsp; Is there a way to create a seed file with the names, IPs and AP type that I can load into the controller before putting it in production?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:44:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902007#M78092</guid>
      <dc:creator>tndmcclain</dc:creator>
      <dc:date>2021-07-05T11:44:57Z</dc:date>
    </item>
    <item>
      <title>Access-point related</title>
      <link>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902008#M78093</link>
      <description>&lt;P&gt;Access-point related configuration is being saved on this access-point itself. These are things like the last joined controller, primary/secondary controller settings, hostname, access-point mode and AP group. The big exception you need to be aware of is the that the FlexConnect group relation is not being saved on the access-point itself. So if you are currently using FlexConnect groups you need to export the lists with MAC address and import / prime the new controller. &lt;BR /&gt;&lt;BR /&gt;Before you pair-up the two new controllers in a HA-SSO setup make sure that at least release 8.0.121.0 and FUS 1.9 is installed on both. Upgrading the FUS image takes at least 35min, so don't freak out :-). The management interface needs to be configured as a "tagged" interface, use a unrouted VLAN for connected the RP ports if there are switches in between.&lt;BR /&gt;&lt;BR /&gt;Be aware when you are going to "rip &amp;amp; replace" the current controller with new units while using the same IPv4 addresses, in some cases ARP tables might need to be cleared on the upstream router (default-gateway).&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>Mon, 04 Apr 2016 20:43:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902008#M78093</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2016-04-04T20:43:19Z</dc:date>
    </item>
    <item>
      <title>Refer link : http://www.cisco</title>
      <link>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902009#M78094</link>
      <description>&lt;P&gt;Refer link : &lt;A href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01110100.html#concept_6C8DB7891E764C869E5FC11349120C20"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01110100.html#concept_6C8DB7891E764C869E5FC11349120C20&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 02:07:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/changing-wireless-controllers/m-p/2902009#M78094</guid>
      <dc:creator>mohanak</dc:creator>
      <dc:date>2016-04-06T02:07:13Z</dc:date>
    </item>
  </channel>
</rss>

