<?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 WLC WAN Backup in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440131#M47200</link>
    <description>&lt;P&gt;WLC WAN Backup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My customer would like to have a Backup-WLC-Controller at their main site. &lt;BR /&gt;On the remote site he has a 5508 with actually 6 accesspoints.&lt;BR /&gt;On the mainsite he has also a 5508 which acts as backup only. They have a 2Mbit WAN between this two sites.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I configured in "Wireless - Global Configuration" the IP of the Backup-controller and a heartbeat.&lt;BR /&gt;When pulling the plug of the Remote-WLC, all accesspoint are moving to the backup-controller of the main site. This works perfect.&lt;BR /&gt;When I plug in again the controller of the remote site, the accesspoints to not jump back.&lt;BR /&gt;They only jump back when I configure on each AP under "High Avalability" the Primary Controller. Ok, the customer only has 6 APs, but what if they had more the 100 or so. Do I have to put in the IP of the primary controller on each AP or is there another way???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next question: The client on the remote site is logged in to the WLAN and has an DHCP-IP and Gateway of the local site.&lt;BR /&gt;In case of WLC-failure the client gets a new IP via the DHCP of the Backup-Controller-site. That works fine.&lt;BR /&gt;But when the controller comes back and all APs are also jumping back, the client fails.&lt;BR /&gt;I have to shutdown its network card and activate it again. After that the client finds the WLAN-SSID and gets a DHCP address again. &lt;BR /&gt;How can I solve this problem without always reloading the network card of the client? Is this a windows problem. Tried with XP and 7.&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 02:03:36 GMT</pubDate>
    <dc:creator>Mike Farnschlaeder</dc:creator>
    <dc:date>2021-07-04T02:03:36Z</dc:date>
    <item>
      <title>WLC WAN Backup</title>
      <link>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440131#M47200</link>
      <description>&lt;P&gt;WLC WAN Backup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My customer would like to have a Backup-WLC-Controller at their main site. &lt;BR /&gt;On the remote site he has a 5508 with actually 6 accesspoints.&lt;BR /&gt;On the mainsite he has also a 5508 which acts as backup only. They have a 2Mbit WAN between this two sites.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I configured in "Wireless - Global Configuration" the IP of the Backup-controller and a heartbeat.&lt;BR /&gt;When pulling the plug of the Remote-WLC, all accesspoint are moving to the backup-controller of the main site. This works perfect.&lt;BR /&gt;When I plug in again the controller of the remote site, the accesspoints to not jump back.&lt;BR /&gt;They only jump back when I configure on each AP under "High Avalability" the Primary Controller. Ok, the customer only has 6 APs, but what if they had more the 100 or so. Do I have to put in the IP of the primary controller on each AP or is there another way???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next question: The client on the remote site is logged in to the WLAN and has an DHCP-IP and Gateway of the local site.&lt;BR /&gt;In case of WLC-failure the client gets a new IP via the DHCP of the Backup-Controller-site. That works fine.&lt;BR /&gt;But when the controller comes back and all APs are also jumping back, the client fails.&lt;BR /&gt;I have to shutdown its network card and activate it again. After that the client finds the WLAN-SSID and gets a DHCP address again. &lt;BR /&gt;How can I solve this problem without always reloading the network card of the client? Is this a windows problem. Tried with XP and 7.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 02:03:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440131#M47200</guid>
      <dc:creator>Mike Farnschlaeder</dc:creator>
      <dc:date>2021-07-04T02:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: WLC WAN Backup</title>
      <link>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440132#M47201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mike,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Great job on running through the AP failover and fallback capabilities on the WLCs.&amp;nbsp; &lt;SPAN class="content"&gt;It is important to note that the AP only performs AP fallback from an &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unconfigured controller to a configured controller &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (Primary/Secondary/Tertiary).&amp;nbsp; So, if an AP without a primary WLC specified joins WLC-A, and fails over to WLC-B, the AP will not fall back.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you mentioned, if the Primary WLC is set, and the AP fails over to another unconfigured WLC, the AP will fallback automatically (once the primary is back online).&amp;nbsp; This can pose a problem as you noted when clients are currently connected.&amp;nbsp; To avoid such network inturruption you have a few options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Disable AP Fallback on WLC&lt;/P&gt;&lt;P&gt;2) Add both WLCs to the High Availablility settings to prevent fallback.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow for you to move APs back to the primary during a maintence window to migitate client inturruption.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In larger deployments the High Availablility settings are typically pushed down via a Lighteight AP Template within WCS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's a great doc that explains AP failover and fallback on the WLC:&lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/tech/tk722/tk721/technologies_tech_note09186a00807a85b8.shtml#ap-fall"&gt;http://www.cisco.com/en/US/tech/tk722/tk721/technologies_tech_note09186a00807a85b8.shtml#ap-fall&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;&lt;P&gt;Drew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Aug 2010 19:57:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440132#M47201</guid>
      <dc:creator>Andrew Betz</dc:creator>
      <dc:date>2010-08-13T19:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: WLC WAN Backup</title>
      <link>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440133#M47202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try H-REAP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Aug 2010 00:10:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-wan-backup/m-p/1440133#M47202</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2010-08-16T00:10:26Z</dc:date>
    </item>
  </channel>
</rss>

