<?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: How disruptive is 'redundancy force-switchover'? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391628#M228617</link>
    <description>&lt;P&gt;If the failover state is healthy (and assuming you haven't changed anything in the networking setup on the switch side since setup and testing) then there is no interruption at all when switching over at least for data transfers. Never tested if voice calls have a jitter when doing it.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Apr 2021 15:26:06 GMT</pubDate>
    <dc:creator>patoberli</dc:creator>
    <dc:date>2021-04-22T15:26:06Z</dc:date>
    <item>
      <title>How disruptive is 'redundancy force-switchover'?</title>
      <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391574#M228609</link>
      <description>&lt;P&gt;We have a pair of WLC 5520s in an active/standby configuration. Both are up, but it looks like there was a failover to the secondary at some point. If I do a 'redundancy force-switchover' on the secondary, how disruptive will this be to our wireless users? We have around 1260 APs.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 20:11:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391574#M228609</guid>
      <dc:creator>spfister336</dc:creator>
      <dc:date>2021-07-05T20:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: How disruptive is 'redundancy force-switchover'?</title>
      <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391575#M228610</link>
      <description>&lt;P&gt;HA Switch over not distruptive&amp;nbsp; as long it configured correctly.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:24:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391575#M228610</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2021-04-22T14:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: How disruptive is 'redundancy force-switchover'?</title>
      <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391578#M228611</link>
      <description>&lt;P&gt;Anything I should check for before doing it? I'll probably do it after business hours.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:25:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391578#M228611</guid>
      <dc:creator>spfister336</dc:creator>
      <dc:date>2021-04-22T14:25:58Z</dc:date>
    </item>
    <item>
      <title>Re: How disruptive is 'redundancy force-switchover'?</title>
      <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391608#M228615</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- If there was&lt;FONT color="#993366"&gt; a failover&lt;/FONT&gt; to the secondary then the reason should probably be &lt;STRONG&gt;known&lt;/STRONG&gt; and or the the &lt;STRONG&gt;health-state&lt;/STRONG&gt; of the (previous) primary should &lt;EM&gt;&lt;U&gt;be inspected&lt;/U&gt;&lt;/EM&gt; , look for crash-logs (e.g.). But in normal circumstances there is &lt;FONT color="#008000"&gt;&lt;STRONG&gt;no&lt;/STRONG&gt; impact&lt;/FONT&gt; and it is even safe to do in business hours.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:57:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391608#M228615</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2021-04-22T14:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: How disruptive is 'redundancy force-switchover'?</title>
      <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391618#M228616</link>
      <description>&lt;P&gt;Make sure HA is Health before failover - no obnormal logs and fail over.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes it is always advise to do in maintenance window for safe and good approach to cover yourself.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 15:14:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391618#M228616</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2021-04-22T15:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: How disruptive is 'redundancy force-switchover'?</title>
      <link>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391628#M228617</link>
      <description>&lt;P&gt;If the failover state is healthy (and assuming you haven't changed anything in the networking setup on the switch side since setup and testing) then there is no interruption at all when switching over at least for data transfers. Never tested if voice calls have a jitter when doing it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 15:26:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-disruptive-is-redundancy-force-switchover/m-p/4391628#M228617</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2021-04-22T15:26:06Z</dc:date>
    </item>
  </channel>
</rss>

