<?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 Re: 2504 as anchor controller HA setup in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3325597#M146986</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/WirelessNetwork_GuestAccessService.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/WirelessNetwork_GuestAccessService.html&lt;/A&gt;&lt;/P&gt;
&lt;H3 class="p_H_Head2"&gt;Anchor Controller Redundancy Priority&lt;/H3&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146753" target="_blank"&gt;&lt;/A&gt;The guest anchor priority feature provides a mechanism that gives "active/standby" load distribution amongst the anchor WLCs. This is achieved by assigning a fixed priority to each anchor WLC, by distributing the load to highest priority WLC and in round-robin fashion if they have the same priority value.&lt;/P&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146706" target="_blank"&gt;&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV align="left"&gt;
&lt;TABLE border="1" width="96%" cellspacing="0" cellpadding="3"&gt;
&lt;TBODY&gt;
&lt;TR align="left" valign="top"&gt;
&lt;TH scope="col"&gt;
&lt;DIV class="pCH1_CellHead1"&gt;&lt;A name="pgfId-1146772" target="_blank"&gt;&lt;/A&gt;Releases Prior to 8.1&lt;/DIV&gt;
&lt;/TH&gt;
&lt;TH scope="col"&gt;
&lt;DIV class="pCH1_CellHead1"&gt;&lt;A name="pgfId-1146774" target="_blank"&gt;&lt;/A&gt;With Release 8.1&lt;/DIV&gt;
&lt;/TH&gt;
&lt;/TR&gt;
&lt;TR align="left" valign="top"&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146776" target="_blank"&gt;&lt;/A&gt;All guest clients are load balanced in round robin fashion amongst anchor WLCs.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146778" target="_blank"&gt;&lt;/A&gt;All guest clients are sent to anchor controller with highest priority in relation to local internal WLC.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR align="left" valign="top"&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146780" target="_blank"&gt;&lt;/A&gt;If an anchor fails, guest clients will be load balanced amongst remaining anchor WLCs.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146782" target="_blank"&gt;&lt;/A&gt;If an anchor fails, guest clients will be sent to the next highest priority or round robin if remaining anchors have same priority value.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146877" target="_blank"&gt;&lt;/A&gt;You can configure a priority to the guest anchor when you configure a WLAN. Priority values range from 1 (high) to 3 (low) or primary, secondary or tertiary and defined priority is displayed with guest anchor. Only one priority value is allowed per anchor WLC. Selection of guest anchor is round-robin based on a single priority value. If a guest anchor is down, the fallback would be on guest anchors with equal priority. If all guest anchors with same priority value are down, the selection would be on a round-robin basis on next highest priority and so on. Default priority value is 3. If WLC is upgraded to Release 8.1, it will be marked with priority 3. Priority configurations are retained across reboots. The priority configuration would be synchronized on HA pair for seamless switchover. Same set of rules apply in determining the anchor WLC regardless of IPv4 and/or IPv6 addressing. That is, highest priority value is determinant and not addressing including dual stack case.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Feb 2018 20:55:15 GMT</pubDate>
    <dc:creator>Saravanan Lakshmanan</dc:creator>
    <dc:date>2018-02-05T20:55:15Z</dc:date>
    <item>
      <title>2504 as anchor controller HA setup</title>
      <link>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3323264#M146983</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The setup are 2 5520 in HA as foreign controller and 2 2504 as anchor controller.&amp;nbsp;The part nbr is 2504-HA-K9. I am confused how the 2504 will be setup as HA.?&amp;nbsp; There is no RP port like the 5520.&amp;nbsp; Do I just have to configure the 2 2504 with diffderent manament IP address?&amp;nbsp; &amp;nbsp;How ill it function as HA?&amp;nbsp; Also, the anchor controller will be used as internal DHCP server.&amp;nbsp; How will the IP addresses be leased?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Manuelito&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:11:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3323264#M146983</guid>
      <dc:creator>mcaoile</dc:creator>
      <dc:date>2021-07-05T15:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: 2504 as anchor controller HA setup</title>
      <link>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3323365#M146984</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/295273"&gt;@mcaoile&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; 2504 does not support HA SSO. You can configure only N + 1 HA.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2018 13:54:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3323365#M146984</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-02-01T13:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: 2504 as anchor controller HA setup</title>
      <link>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3324738#M146985</link>
      <description>&lt;P&gt;Hi Flavio,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thks for the reply.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How will the 2 anchor controllers work in providing Guest access?&amp;nbsp; Will the 2 balance the Guest useer access? What about the internal DHCP, do I have to divide into 2 the DHCP pool?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Sun, 04 Feb 2018 05:02:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3324738#M146985</guid>
      <dc:creator>mcaoile</dc:creator>
      <dc:date>2018-02-04T05:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: 2504 as anchor controller HA setup</title>
      <link>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3325597#M146986</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/WirelessNetwork_GuestAccessService.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide/WirelessNetwork_GuestAccessService.html&lt;/A&gt;&lt;/P&gt;
&lt;H3 class="p_H_Head2"&gt;Anchor Controller Redundancy Priority&lt;/H3&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146753" target="_blank"&gt;&lt;/A&gt;The guest anchor priority feature provides a mechanism that gives "active/standby" load distribution amongst the anchor WLCs. This is achieved by assigning a fixed priority to each anchor WLC, by distributing the load to highest priority WLC and in round-robin fashion if they have the same priority value.&lt;/P&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146706" target="_blank"&gt;&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV align="left"&gt;
&lt;TABLE border="1" width="96%" cellspacing="0" cellpadding="3"&gt;
&lt;TBODY&gt;
&lt;TR align="left" valign="top"&gt;
&lt;TH scope="col"&gt;
&lt;DIV class="pCH1_CellHead1"&gt;&lt;A name="pgfId-1146772" target="_blank"&gt;&lt;/A&gt;Releases Prior to 8.1&lt;/DIV&gt;
&lt;/TH&gt;
&lt;TH scope="col"&gt;
&lt;DIV class="pCH1_CellHead1"&gt;&lt;A name="pgfId-1146774" target="_blank"&gt;&lt;/A&gt;With Release 8.1&lt;/DIV&gt;
&lt;/TH&gt;
&lt;/TR&gt;
&lt;TR align="left" valign="top"&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146776" target="_blank"&gt;&lt;/A&gt;All guest clients are load balanced in round robin fashion amongst anchor WLCs.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146778" target="_blank"&gt;&lt;/A&gt;All guest clients are sent to anchor controller with highest priority in relation to local internal WLC.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR align="left" valign="top"&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146780" target="_blank"&gt;&lt;/A&gt;If an anchor fails, guest clients will be load balanced amongst remaining anchor WLCs.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146782" target="_blank"&gt;&lt;/A&gt;If an anchor fails, guest clients will be sent to the next highest priority or round robin if remaining anchors have same priority value.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;P class="pB1_Body1"&gt;&lt;A name="pgfId-1146877" target="_blank"&gt;&lt;/A&gt;You can configure a priority to the guest anchor when you configure a WLAN. Priority values range from 1 (high) to 3 (low) or primary, secondary or tertiary and defined priority is displayed with guest anchor. Only one priority value is allowed per anchor WLC. Selection of guest anchor is round-robin based on a single priority value. If a guest anchor is down, the fallback would be on guest anchors with equal priority. If all guest anchors with same priority value are down, the selection would be on a round-robin basis on next highest priority and so on. Default priority value is 3. If WLC is upgraded to Release 8.1, it will be marked with priority 3. Priority configurations are retained across reboots. The priority configuration would be synchronized on HA pair for seamless switchover. Same set of rules apply in determining the anchor WLC regardless of IPv4 and/or IPv6 addressing. That is, highest priority value is determinant and not addressing including dual stack case.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Feb 2018 20:55:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2504-as-anchor-controller-ha-setup/m-p/3325597#M146986</guid>
      <dc:creator>Saravanan Lakshmanan</dc:creator>
      <dc:date>2018-02-05T20:55:15Z</dc:date>
    </item>
  </channel>
</rss>

