<?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: WLC Redundancy has failed. Looking to restore. in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269616#M281491</link>
    <description>&lt;P&gt;So, I believe I see the issue I just checked &amp;amp; I as mistaken &amp;amp; one of the RP ports isn't passing traffic. If I replace the possibly bad SFP &amp;amp; the interface comes back up, would there be downtime for the WLC's to enter back into an HA state or would downtime be required?&lt;/P&gt;</description>
    <pubDate>Mon, 10 Mar 2025 17:38:51 GMT</pubDate>
    <dc:creator>Mogwai</dc:creator>
    <dc:date>2025-03-10T17:38:51Z</dc:date>
    <item>
      <title>WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269564#M281483</link>
      <description>&lt;P&gt;Hello, over the weekend it seems that our Cisco 5520's that are in an HA, went down &amp;amp; came in in a non-HA state.&amp;nbsp;&lt;/P&gt;&lt;P&gt;(CEN-5520) &amp;gt;show redundancy summary&lt;BR /&gt;Redundancy Mode = SSO ENABLED&lt;BR /&gt;Local State = ACTIVE&lt;BR /&gt;Peer State = UNKNOWN - Communication Down&lt;BR /&gt;Unit = Primary&lt;BR /&gt;Unit ID = 00:A2:EE:9C:69:AD&lt;BR /&gt;Redundancy State = Non Redundant&lt;BR /&gt;Mobility MAC = 00:A2:EE:9C:69:AD&lt;BR /&gt;Redundancy Port = UP&lt;BR /&gt;BulkSync Status = Pending&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 15:25:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269564#M281483</guid>
      <dc:creator>Mogwai</dc:creator>
      <dc:date>2025-03-10T15:25:21Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269589#M281488</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Check if all network connections are solid on the controller, especially RP to RP ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 16:28:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269589#M281488</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-03-10T16:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269603#M281489</link>
      <description>&lt;P&gt;Yes, all RP's are connected &amp;amp; passing traffic. One the Secondary unit, I do see the following error.&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;(Secondary) &amp;gt;show redundancy summary
            Redundancy Mode = SSO ENABLED 
                Local State = MAINTENANCE 
                 Peer State = UNKNOWN - Communication Down 
                       Unit = Secondary
                    Unit ID = 00:B7:71:8B:04:2F
           Redundancy State = Non Redundant
               Mobility MAC = 00:A2:EE:9C:69:AD
               Redundancy Port  = UP
               Link Encryption = ENABLED
Maintenance Mode = Enabled
Maintenance cause= Peer RP is not reachable or Hardware model/Software version mismatch&lt;/LI-CODE&gt;&lt;P&gt;I've checked the versioning of both the primary &amp;amp; secondary and both match. Although, the Bootloader &amp;amp; Emergency versions are different between the Primary &amp;amp; Secondary. Do those need to match as well?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 17:02:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269603#M281489</guid>
      <dc:creator>Mogwai</dc:creator>
      <dc:date>2025-03-10T17:02:34Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269616#M281491</link>
      <description>&lt;P&gt;So, I believe I see the issue I just checked &amp;amp; I as mistaken &amp;amp; one of the RP ports isn't passing traffic. If I replace the possibly bad SFP &amp;amp; the interface comes back up, would there be downtime for the WLC's to enter back into an HA state or would downtime be required?&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 17:38:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269616#M281491</guid>
      <dc:creator>Mogwai</dc:creator>
      <dc:date>2025-03-10T17:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269617#M281492</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp; &amp;nbsp;Both&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;Bootloader &amp;amp; Emergency versions&amp;nbsp; need to match!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 17:41:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269617#M281492</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-03-10T17:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269625#M281493</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Depends , start by issuing the command &lt;STRONG&gt;show redundancy summary&lt;/STRONG&gt; again, when you replace the bad SFP ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 18:12:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269625#M281493</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-03-10T18:12:30Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269626#M281494</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Here you have a number of other commands which can provide insights :&lt;BR /&gt;&lt;STRONG&gt;show redundancy summary&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy infra statistics&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy transport statistics&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy keepalive statistics&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy gw-reachability statistics&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy config-sync statistics&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy ap-sync statistics&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;show redundancy client-sync statistics&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 18:14:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269626#M281494</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-03-10T18:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Redundancy has failed. Looking to restore.</title>
      <link>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269678#M281496</link>
      <description>&lt;P&gt;Power down the secondary WLC and replace the faulty SFP.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Power on.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 21:31:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-redundancy-has-failed-looking-to-restore/m-p/5269678#M281496</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-03-10T21:31:27Z</dc:date>
    </item>
  </channel>
</rss>

