<?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 Great, thanks for the answer in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816229#M114867</link>
    <description>&lt;P&gt;Great, thanks for the answer&lt;/P&gt;</description>
    <pubDate>Wed, 10 Feb 2016 15:16:26 GMT</pubDate>
    <dc:creator>Alexmpj376</dc:creator>
    <dc:date>2016-02-10T15:16:26Z</dc:date>
    <item>
      <title>WLC Active/Active vs Active/Standby</title>
      <link>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816225#M114863</link>
      <description>&lt;P&gt;&lt;SPAN&gt;What are all&amp;nbsp;advantages of&amp;nbsp;using Redundancy mode for WLC's vs using Active/Active mode&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:33:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816225#M114863</guid>
      <dc:creator>Alexmpj376</dc:creator>
      <dc:date>2021-07-05T11:33:51Z</dc:date>
    </item>
    <item>
      <title>1:1 where one WLC will be</title>
      <link>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816226#M114864</link>
      <description>&lt;DIV data-canvas-width="475.41736000000003" style="left: 484.301px; top: 713.897px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04095);"&gt;1:1 where one WLC will be&lt;/DIV&gt;
&lt;DIV data-canvas-width="719.7660399999996" style="left: 240px; top: 733.896px; font-size: 16.6px; font-family: serif; transform: scaleX(1.02633);"&gt;in an Active state and the second WLC will be in a Hot Standby state continuously monitoring the health&lt;/DIV&gt;
&lt;DIV data-canvas-width="357.1207799999999" style="left: 240px; top: 753.896px; font-size: 16.6px; font-family: serif; transform: scaleX(1.0482);"&gt;of the Active WLC via a Redundant Port. Both the&lt;/DIV&gt;
&lt;DIV data-canvas-width="336.05039999999997" style="left: 597.601px; top: 753.896px; font-size: 16.6px; font-family: serif; transform: scaleX(1.05016);"&gt;WLCs will share the same set of configurations&lt;/DIV&gt;
&lt;DIV data-canvas-width="716.9357399999999" style="left: 240px; top: 773.896px; font-size: 16.6px; font-family: serif; transform: scaleX(1.05141);"&gt;including the IP address of the Management interface. The WLC in the Standby state does not need to&lt;/DIV&gt;
&lt;DIV data-canvas-width="667.0560600000003" style="left: 240px; top: 793.895px; font-size: 16.6px; font-family: serif; transform: scaleX(1.05067);"&gt;be configured independently as the entire configuration (Bulk Configuration while boot up and&lt;/DIV&gt;
&lt;DIV data-canvas-width="719.6000400000001" style="left: 240px; top: 813.895px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04822);"&gt;Incremental Configuration in runtime) will be synced from the Active WLC to the Standby WLC via a&lt;/DIV&gt;
&lt;DIV data-canvas-width="397.49198" style="left: 240px; top: 833.895px; font-size: 16.6px; font-family: serif; transform: scaleX(1.02196);"&gt;Redundant Port. The AP's CAPWAP State (only APs whic&lt;/DIV&gt;
&lt;DIV data-canvas-width="321.80262000000005" style="left: 637.801px; top: 833.895px; font-size: 16.6px; font-family: serif; transform: scaleX(1.01005);"&gt;h are in a run state) is also synced, and a mirror&lt;/DIV&gt;
&lt;DIV data-canvas-width="719.7959200000001" style="left: 240px; top: 853.894px; font-size: 16.6px; font-family: serif; transform: scaleX(1.03182);"&gt;copy of the AP database is maintained on the Standby WLC. The APs do not go into the Discovery state&lt;/DIV&gt;
&lt;DIV data-canvas-width="619.3626" style="left: 240px; top: 873.894px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04516);"&gt;when the Active WLC fails and the Standby WLC takes over the network's Active WLC.&lt;/DIV&gt;
&lt;DIV data-canvas-width="375.12348000000003" style="left: 240px; top: 902.194px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04491);"&gt;There is no preempt functionality. When the previous&lt;/DIV&gt;
&lt;DIV data-canvas-width="344.34874" style="left: 615.401px; top: 902.194px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04174);"&gt;Active WLC comes back, it will not take the role&lt;/DIV&gt;
&lt;DIV data-canvas-width="719.7228800000005" style="left: 240px; top: 922.193px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04066);"&gt;of the Active WLC, but will negotiate its state with the current Active WLC and transition to a Standby&lt;/DIV&gt;
&lt;DIV data-canvas-width="337.48464000000007" style="left: 240px; top: 942.193px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04269);"&gt;state. The Active and Standby decision is not an&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="382.0224400000001" style="left: 577.7px; top: 942.193px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04235);"&gt;automated election process. The &lt;SPAN class="highlight selected"&gt;Active/Standby&lt;/SPAN&gt; WLC&lt;/DIV&gt;
&lt;DIV data-canvas-width="364.5874599999999" style="left: 240px; top: 962.193px; font-size: 16.6px; font-family: serif; transform: scaleX(1.03107);"&gt;is decided based on HA SKU (Manufacturing Ordere&lt;/DIV&gt;
&lt;DIV data-canvas-width="354.6158400000001" style="left: 604.9px; top: 962.193px; font-size: 16.6px; font-family: serif; transform: scaleX(1.02288);"&gt;d UDI) from release 7.3 onwards. A WLC with HA&lt;/DIV&gt;
&lt;DIV data-canvas-width="705.9963400000001" style="left: 240px; top: 982.192px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04947);"&gt;SKU UDI will always be the Standby WLC for the first time when it boots and pairs up with a WLC&lt;/DIV&gt;
&lt;DIV data-canvas-width="337.22402000000005" style="left: 240px; top: 1002.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.05081);"&gt;running a permanent count license. For existing&lt;/DIV&gt;
&lt;DIV data-canvas-width="317.1180999999999" style="left: 577.5px; top: 1002.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04861);"&gt;WLCs having a permanent count license, the&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="485.5416999999999" style="left: 240px; top: 1022.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04793);"&gt;Active/Standby decision can be made based on manual configuration&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="485.5416999999999" style="left: 240px; top: 1022.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04793);"&gt;&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="485.5416999999999" style="left: 240px; top: 1022.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04793);"&gt;For more information about the redundancy you can look into the HA availability guide below.&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="485.5416999999999" style="left: 240px; top: 1022.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04793);"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="485.5416999999999" style="left: 240px; top: 1022.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04793);"&gt;&lt;/DIV&gt;
&lt;DIV class="" data-canvas-width="485.5416999999999" style="left: 240px; top: 1022.19px; font-size: 16.6px; font-family: serif; transform: scaleX(1.04793);"&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 01 Feb 2016 10:53:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816226#M114864</guid>
      <dc:creator>Prakash Parvathala</dc:creator>
      <dc:date>2016-02-01T10:53:39Z</dc:date>
    </item>
    <item>
      <title>Alex, </title>
      <link>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816227#M114865</link>
      <description>&lt;P&gt;Alex,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are no real advantages between Redundancy mode vs Active / Active it all depends on your topology and failover scenarios and downtime you can sustain.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lets step through all the possible options.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1: &lt;STRONG&gt;Single controller&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;/STRONG&gt;All your&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;AP's will register to the single controller and if this controller fails you will have no wireless service until that controller has been restored.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2:&amp;nbsp;&lt;STRONG&gt;2 x Controllers in Active / Standby&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;With this&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;setup you will have two controllers running in an Active / Standby configuration. They will share the same IP and configuration. They can be located in the same location or at two geographically separate locations (if you can provide L2 connectivity between both controllers)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;All AP's register to a single IP address and if the primary controller fails the APs will not experience any downtime as they will instantly move to the standby controller.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;3:&amp;nbsp;&lt;STRONG&gt;Redundant Controllers&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;In this&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;setup you have a primary controller in one location and a second controller in another location. APs will register to the primary controller and also be configured to have the second controller as a backup. In the event of a failure of the primary controller the AP's will have to re-associate to the secondary controller which could be up to 120 seconds and will result in downtime for clients.&lt;/P&gt;
&lt;P&gt;As for advantages of either setup you need to assess your budget and downtime requirements.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then based on your requirements you choose the best solution.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that helps&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2016 22:50:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816227#M114865</guid>
      <dc:creator>roger perkin</dc:creator>
      <dc:date>2016-02-01T22:50:43Z</dc:date>
    </item>
    <item>
      <title>Simply in HA, if your primary</title>
      <link>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816228#M114866</link>
      <description>&lt;P&gt;Simply in HA, if your primary controller went down, the AP's will go directly to the secondary without any interruption (APSSO), and your clients will not disconnect (Client SSO if it is supported). both controllers will share the same configuration including the management IP address.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;In active-active clients will disconnect and the AP will disconnect if the one controller went down, because the AP will go with the joining process with the second active controller.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Mohammad Setan&lt;/P&gt;</description>
      <pubDate>Tue, 09 Feb 2016 14:08:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816228#M114866</guid>
      <dc:creator>Mohammad Setan</dc:creator>
      <dc:date>2016-02-09T14:08:09Z</dc:date>
    </item>
    <item>
      <title>Great, thanks for the answer</title>
      <link>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816229#M114867</link>
      <description>&lt;P&gt;Great, thanks for the answer&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2016 15:16:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-active-active-vs-active-standby/m-p/2816229#M114867</guid>
      <dc:creator>Alexmpj376</dc:creator>
      <dc:date>2016-02-10T15:16:26Z</dc:date>
    </item>
  </channel>
</rss>

