<?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 WLAN controller redundancy over IP VPN in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlan-controller-redundancy-over-ip-vpn/m-p/2565366#M75640</link>
    <description>&lt;P&gt;Customer currently has a Cisco 5500 WLAN controller at one of our datacenters. They want to add a WLAN controller as redundancy at their local site which shall be used as a secondary failover controller. This site is reachable over VPN. Which redundancy options do I have here? As i understand with HA functions the controllers has to be within the same L2 network and have low latency. Is my only option here to manually configure a new controller, buy double the AP licenses and copy the config from the old one? And if the first fail the APs would need to reboot and reassociate with the secondary controller?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would be really greatful if someone could point me in the right direction &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 09:01:57 GMT</pubDate>
    <dc:creator>Andre Liverod</dc:creator>
    <dc:date>2021-07-05T09:01:57Z</dc:date>
    <item>
      <title>WLAN controller redundancy over IP VPN</title>
      <link>https://community.cisco.com/t5/wireless/wlan-controller-redundancy-over-ip-vpn/m-p/2565366#M75640</link>
      <description>&lt;P&gt;Customer currently has a Cisco 5500 WLAN controller at one of our datacenters. They want to add a WLAN controller as redundancy at their local site which shall be used as a secondary failover controller. This site is reachable over VPN. Which redundancy options do I have here? As i understand with HA functions the controllers has to be within the same L2 network and have low latency. Is my only option here to manually configure a new controller, buy double the AP licenses and copy the config from the old one? And if the first fail the APs would need to reboot and reassociate with the secondary controller?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would be really greatful if someone could point me in the right direction &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 09:01:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlan-controller-redundancy-over-ip-vpn/m-p/2565366#M75640</guid>
      <dc:creator>Andre Liverod</dc:creator>
      <dc:date>2021-07-05T09:01:57Z</dc:date>
    </item>
    <item>
      <title>You have a few options ..  1.</title>
      <link>https://community.cisco.com/t5/wireless/wlan-controller-redundancy-over-ip-vpn/m-p/2565367#M75641</link>
      <description>&lt;P&gt;You have a few options ..&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Buy two fully licensed controllers. One primary one secondary and configure as such.&lt;/P&gt;&lt;P&gt;2. HA N+1 where you buy one fully licensed controller and one HA controller or a controller with a minimum of 50 licenses. Put the secondary controller into ha mode and it will go to max licenses.&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide/Licensing.html&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. APSSO AND CLIENT SSO this is where you need layer 2. There is a data base that syncs between the&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2014 13:59:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlan-controller-redundancy-over-ip-vpn/m-p/2565367#M75641</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2014-11-28T13:59:30Z</dc:date>
    </item>
  </channel>
</rss>

