<?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: 4402 Fail-Over  in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675785#M213980</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;This is very possible. You could also go with 3 (4402-25's) WLC's in a N+1 configuration that would support all 25 of the AP's if A or B failed. Have a look;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WLAN Controller Failover for Lightweight Access Points Configuration Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;Rob &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Jan 2007 22:13:07 GMT</pubDate>
    <dc:creator>Rob Huffman</dc:creator>
    <dc:date>2007-01-23T22:13:07Z</dc:date>
    <item>
      <title>4402 Fail-Over</title>
      <link>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675784#M213979</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Does anybody know if you can split 50 lwap's between two 4402 WLC's?  Maybe take every other and put them on WLC A, and the others on WLC B?  So that if I lose WLC B or A, only half of the LWAP's go out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 20:31:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675784#M213979</guid>
      <dc:creator>mike</dc:creator>
      <dc:date>2021-07-03T20:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: 4402 Fail-Over</title>
      <link>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675785#M213980</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;This is very possible. You could also go with 3 (4402-25's) WLC's in a N+1 configuration that would support all 25 of the AP's if A or B failed. Have a look;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WLAN Controller Failover for Lightweight Access Points Configuration Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;Rob &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jan 2007 22:13:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675785#M213980</guid>
      <dc:creator>Rob Huffman</dc:creator>
      <dc:date>2007-01-23T22:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: 4402 Fail-Over</title>
      <link>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675786#M213981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First configure a mobility group between the controllers and use the Primary and Secondary fields under each access point to manually balance the load.  Set the controller name not the IP that you want to connect to.  I'd suggest architecting your primary and secondary so that a particular floor or area of access points is terminated to the same controller.  That way roams do not cause inter-controller events or traffic.  I have successfully tuned the AP Heart Beat Timeout from 30 seconds down to 10 seconds, thus speeding up AP failover when a controller dies (config advanced timers ap-heartBeat-timeout x) and (show advanced timers).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also look at the "AP Fallback" setting to determine if you want the AP's to stay on the secondary controller or return to the primary, after the failed primary recovers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jan 2007 22:13:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675786#M213981</guid>
      <dc:creator>Darren Ramsey</dc:creator>
      <dc:date>2007-01-23T22:13:39Z</dc:date>
    </item>
    <item>
      <title>Re: 4402 Fail-Over</title>
      <link>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675787#M213982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the excellent replies...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2007 16:05:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/4402-fail-over/m-p/675787#M213982</guid>
      <dc:creator>mike</dc:creator>
      <dc:date>2007-01-24T16:05:27Z</dc:date>
    </item>
  </channel>
</rss>

