<?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 This depends on the software in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059751#M77895</link>
    <description>&lt;P&gt;This depends on the software version you are running. With &amp;gt;7.5 you can run&amp;nbsp;the redundancy port&amp;nbsp;over a switched/routed network and latency isn't anymore that important.&lt;/P&gt;
&lt;P&gt;See here for the exact details: http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/HA_SSO_DG/High_Availability_DG.html&lt;/P&gt;
&lt;P&gt;The chapter named "High Availability in Release 7.5" is probably the one you're looking at.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 05 May 2017 10:59:51 GMT</pubDate>
    <dc:creator>patoberli</dc:creator>
    <dc:date>2017-05-05T10:59:51Z</dc:date>
    <item>
      <title>Configure redundancy between 2 active Cisco Wireless Controllers (5508)</title>
      <link>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059747#M77891</link>
      <description>&lt;P&gt;We have two (2) WLC 5508 currently in production, each with associated Access Points and Wireless devices. Now we would like to configure the redundancy between the two wireless controllers. I have not done configuring two devices in production with associated APs and Wireless devices so I'd like to&amp;nbsp;get the opinion from the group. Shall I move/copy all APs and wireless devices to the primary WLC before configuring the redundancy?&amp;nbsp;What else should we consider to successfully implement a redundancy between the 2 controllers and without affecting the existing users? Thanks in advance!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;WLC #1 --- 12 APs and 170 wireless devices (roaming users between WLC#1 and WLC#2)&lt;/P&gt;
&lt;P&gt;WLC #2 --- 8 APs and 170 wireless devices&amp;nbsp;(roaming users between WLC#1 and WLC#2)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 13:47:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059747#M77891</guid>
      <dc:creator>Harold Bueno</dc:creator>
      <dc:date>2021-07-05T13:47:02Z</dc:date>
    </item>
    <item>
      <title>roaming users between WLC#1</title>
      <link>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059748#M77892</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;roaming users between WLC#1 and WLC#2&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;Inter-controller roaming is not recommended. &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If redunancy is key, then put all the APs in one controller and enable HA SSO.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2017 05:39:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059748#M77892</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2017-04-03T05:39:18Z</dc:date>
    </item>
    <item>
      <title>Hi Leo, thank you very much</title>
      <link>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059749#M77893</link>
      <description>&lt;P&gt;Hi Leo, thank you very much for&amp;nbsp;the quick note and suggestion. It is really appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2017 07:36:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059749#M77893</guid>
      <dc:creator>Harold Bueno</dc:creator>
      <dc:date>2017-04-03T07:36:34Z</dc:date>
    </item>
    <item>
      <title>Hi again,</title>
      <link>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059750#M77894</link>
      <description>&lt;P&gt;Hi again,&lt;/P&gt;
&lt;P&gt;What is the maximum cable length allowed for redundancy? Our WLCs are located on different sites with about 1 kilometer apart but a fiber optic cable is available - just waiting for media converter and fiber patch cables to complete the connection.&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2017 11:01:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059750#M77894</guid>
      <dc:creator>Harold Bueno</dc:creator>
      <dc:date>2017-05-02T11:01:20Z</dc:date>
    </item>
    <item>
      <title>This depends on the software</title>
      <link>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059751#M77895</link>
      <description>&lt;P&gt;This depends on the software version you are running. With &amp;gt;7.5 you can run&amp;nbsp;the redundancy port&amp;nbsp;over a switched/routed network and latency isn't anymore that important.&lt;/P&gt;
&lt;P&gt;See here for the exact details: http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/HA_SSO_DG/High_Availability_DG.html&lt;/P&gt;
&lt;P&gt;The chapter named "High Availability in Release 7.5" is probably the one you're looking at.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 May 2017 10:59:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configure-redundancy-between-2-active-cisco-wireless-controllers/m-p/3059751#M77895</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2017-05-05T10:59:51Z</dc:date>
    </item>
  </channel>
</rss>

