<?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 When using N+1 and in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/how-n-1-ha-works-over-wan/m-p/2945029#M165866</link>
    <description>&lt;P&gt;When using N+1 and controllers separated by L3, you need to define the bland and interfaces for that location. When a controller fails, users will disassociate and then re-associate and obtain a dhcp from the new location. This is how N+1 works over L3. &amp;nbsp;So look at it like a total different site as traffic now will egress that location when there is a failover.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Scott&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*** Please rate helpful posts ***&lt;/P&gt;</description>
    <pubDate>Sun, 16 Oct 2016 12:41:11 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2016-10-16T12:41:11Z</dc:date>
    <item>
      <title>How N+1 HA works over WAN?</title>
      <link>https://community.cisco.com/t5/wireless/how-n-1-ha-works-over-wan/m-p/2945028#M165865</link>
      <description>&lt;P&gt;I have read that the N+1 HA model provides redundancy for&amp;nbsp;geographically separated data centers.&lt;/P&gt;
&lt;P&gt;As of my implementation for the&amp;nbsp;&lt;SPAN&gt;the N+1 HA in one site, I understand that it works in Layer 2, as we&amp;nbsp;connect the WLC as a trunk, connect APs as an access and add the VLAN ID to every interface we add and then assign these&amp;nbsp;interfaces to SSIDs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;But over WAN we are in Layer 3, how does the backup controller work with VLANs that it don't know about?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 12:58:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-n-1-ha-works-over-wan/m-p/2945028#M165865</guid>
      <dc:creator>Ahmad El-Saka</dc:creator>
      <dc:date>2021-07-05T12:58:45Z</dc:date>
    </item>
    <item>
      <title>When using N+1 and</title>
      <link>https://community.cisco.com/t5/wireless/how-n-1-ha-works-over-wan/m-p/2945029#M165866</link>
      <description>&lt;P&gt;When using N+1 and controllers separated by L3, you need to define the bland and interfaces for that location. When a controller fails, users will disassociate and then re-associate and obtain a dhcp from the new location. This is how N+1 works over L3. &amp;nbsp;So look at it like a total different site as traffic now will egress that location when there is a failover.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Scott&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*** Please rate helpful posts ***&lt;/P&gt;</description>
      <pubDate>Sun, 16 Oct 2016 12:41:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-n-1-ha-works-over-wan/m-p/2945029#M165866</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2016-10-16T12:41:11Z</dc:date>
    </item>
  </channel>
</rss>

