<?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: Wireless C9800 update Redundancy settings in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289369#M283179</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp;Nothing special seen ,as stated also check the&lt;EM&gt; interface counters&lt;/EM&gt; on the switch ports where the RP ports are connected to ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
    <pubDate>Fri, 09 May 2025 09:33:44 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2025-05-09T09:33:44Z</dc:date>
    <item>
      <title>Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280133#M282343</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;
&lt;P&gt;we have installed c9800 HA pair 2 months ago, running&amp;nbsp;17.12.4 version.&lt;/P&gt;
&lt;P&gt;We are facing now random reloads of standby WLC every few hours with this info:&lt;/P&gt;
&lt;P&gt;Reload History:&lt;/P&gt;
&lt;P&gt;Reload Code: Reload&lt;BR /&gt;Reload Description: Reload Command - RIF: Bulk Sync, system report at bootflash:core/XXXXX&lt;BR /&gt;Reload Severity: Normal Reboot&lt;BR /&gt;Reload Time: 05:21:52 CEST Wed Apr 9 2025&lt;/P&gt;
&lt;P&gt;As active WLC could see keep alive missing packets in logs, we got recommendation to increase keep alive timer in GUI (Administration -&amp;gt; Device -&amp;gt; Redundancy -&amp;gt; Keep alive timer) to 10 (currently set to 1).&lt;/P&gt;
&lt;P&gt;My question: would this update of running HA pair cause some downtime for active WLC / HA pair / associated clients?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, is there a way how to test RP cable (direct connection between A/S WLCs) to prove cable issues or we should just exchange cable?&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 12:35:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280133#M282343</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-04-10T12:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280143#M282344</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;The keepalive timer is only used for communication between the active and standby WLCs, and updating this timer just adjusts how long the active waits before declaring the standby "down".&amp;nbsp;&lt;BR /&gt;It should not affect the active WLC or connected clients, and for best practice i think you should do it during low usage and montor closely.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Regarding cable test, are you thinking about something like "test cable diagnostics tdr" on a switch? Dont think there is any support on WLC regarding that. &lt;BR /&gt;&lt;BR /&gt;Have you seen any unnusual outputs from:&lt;BR /&gt;show redundancy history&lt;BR /&gt;show redundancy summary&lt;BR /&gt;Any interface errors on show logging? &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 13:05:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280143#M282344</guid>
      <dc:creator>sveseg</dc:creator>
      <dc:date>2025-04-10T13:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280158#M282345</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- I can't see a correlation with the upgrade ; you can run CLI :&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp;test wireless redundancy rping&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;And keep it running for a while. Also check counters on both RP ports on the switches.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Always validate the configuration of the primary controller with the CLI command :&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;FONT color="#008000"&gt;&lt;STRONG&gt;show tech&lt;U&gt; wireless&amp;nbsp;&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Feed the output from that into&amp;nbsp;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank" rel="noopener"&gt;https://cway.cisco.com/wireless-config-analyzer/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;M.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 14:57:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280158#M282345</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-04-10T14:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280161#M282346</link>
      <description>&lt;P&gt;If your environment is experiencing no issues, then you are in a good spot.&amp;nbsp; You should probably open a TAC case also just in case.&amp;nbsp; If you know that your secondary is an issue, or at least you see if restarting.&amp;nbsp; Have you tried to failover to see if the issue persists with the new primary or does it happen with the same unit which would be the primary after you did a failover.&amp;nbsp; This would be a good check to validate that your wireless is either still working well after a failover or not.&amp;nbsp; If you happen to still see issues with that one unit that is your current secondary, I personally would remove it from the cluster, factory reset it and put on the basic configs so that you can enable SSO again.&amp;nbsp; Like what the others also mentioned, you should check all your cabling and see if you see any interface errors, if not, then a factory reset of that unit would probably be the way to help determine if maybe your secondary needs to be RMA's, but that would be where TAC can help.&amp;nbsp; TAC can look at the crash files.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 14:07:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280161#M282346</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2025-04-10T14:07:03Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280186#M282355</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;U&gt;- Adding a number of useful commands when troubleshooting HA SSO&lt;BR /&gt;&lt;BR /&gt;&lt;/U&gt;&lt;EM&gt;&amp;nbsp;show redundancy | i ptime|Location|Current Software state|Switchovers&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show chassis &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show chassis detail&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;show chassis ha-status local&lt;/STRONG&gt; &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show chassis ha-status active &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show chassis ha-status standby &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;show chassis rmi&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show redundancy &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show redundancy history &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;show redundancy switchover history&lt;/STRONG&gt; &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show tech wireless redundancy&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show redundancy states &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;show platform hardware slot R0 ha_port interface stats&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;show platform hardware slot R0 ha_port sfp idprom&amp;nbsp; &amp;nbsp; &amp;nbsp;(when using fiber)&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 15:01:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280186#M282355</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-04-10T15:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280248#M282367</link>
      <description>&lt;P&gt;Changing KA timers does not need a downtime. It can be done anytime. Based on the logs it looks like during every reload a system report is getting generated.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 17:27:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280248#M282367</guid>
      <dc:creator>Saikat Nandy</dc:creator>
      <dc:date>2025-04-10T17:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280423#M282389</link>
      <description>&lt;P&gt;Thanks for all inputs,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I edited timer and retries to maximum - 10. Im gonna monitor the HA pair now, but I noticed yesterday some drops for keepalive counter:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;WC-01#show platform software stack-mgr chassis active R0 sdp-counters&lt;BR /&gt;Stack Discovery Protocol (SDP) Counters&lt;/P&gt;
&lt;P&gt;---------------------------------------&lt;/P&gt;
&lt;P&gt;Message Tx Success Tx Fail Rx Success Rx Fail &lt;BR /&gt;------------------------------------------------------------------------------&lt;BR /&gt;Discovery 6374&amp;nbsp; 2&amp;nbsp; 177&amp;nbsp; 0 &lt;BR /&gt;Neighbor 17951390&amp;nbsp; 2&amp;nbsp; 8975605&amp;nbsp; 0 &lt;BR /&gt;Keepalive 2830439&amp;nbsp;&amp;nbsp;&lt;STRONG&gt;17169&lt;/STRONG&gt;&amp;nbsp; 2820659&amp;nbsp; 0 &lt;BR /&gt;SEPPUKU 0 0 0 0 &lt;BR /&gt;Standby Elect Req 11 0 0 0 &lt;BR /&gt;Standby Elect Ack 0 0 11 0 &lt;BR /&gt;Standby IOS State 0 0 22 0 &lt;BR /&gt;Reload Req 0 0 0 0 &lt;BR /&gt;Reload Ack 0 0 0 0 &lt;BR /&gt;SESA Mesg 0 0 0 0 &lt;BR /&gt;RTU Msg 0 0 0 0 &lt;BR /&gt;Disc Timer Stop 1 0 11 0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it showing faulty RP cable?&lt;/P&gt;
&lt;P&gt;If so, what are steps for replacement on running and operational HA pair? Just exchange cable and repatch it to WLCs? I assume, that some downtime is needed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 05:53:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280423#M282389</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-04-11T05:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280436#M282395</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp;&amp;gt;..&lt;EM&gt;.If so, what are steps for replacement on running and operational HA pair?&amp;nbsp;&lt;/EM&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Simply power down the standby only and replace the cable , then power it on again&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt;This will have no impact&lt;/FONT&gt;, use my bunch of diagnostic&amp;nbsp; commands send earlier&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; to verify statuses,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 06:26:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5280436#M282395</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-04-11T06:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289318#M283168</link>
      <description>&lt;P&gt;So, we exchange the RP cable for new one, issue still persists.&lt;/P&gt;
&lt;P&gt;WLC pairs are in different floors, we are using Cat6 cable with length more than 60m to connect them and not even directly but via patch panels: WLC1 -&amp;gt; patch cable -&amp;gt; Cat6 RP cable between floors -&amp;gt; patch cable -&amp;gt; WLC2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could be issue with losing RP communication related to this physical connection?&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 05:38:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289318#M283168</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-05-09T05:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289329#M283169</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp; &amp;nbsp;Check the output of the command&amp;nbsp;&lt;STRONG&gt; show redundancy config-sync failures prc&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 06:48:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289329#M283169</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-05-09T06:48:33Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289333#M283170</link>
      <description>&lt;P&gt;WC-01#show redundancy config-sync failures prc &lt;BR /&gt;PRC Failed Command List&lt;BR /&gt;-----------------------&lt;/P&gt;
&lt;P&gt;The list is Empty&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 06:54:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289333#M283170</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-05-09T06:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289337#M283171</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp; &amp;nbsp;That's OK, if you suspect problems with the physical connection then look at the &lt;STRONG&gt;port counters&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;of the RP port(s) on the switches.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;And look at the output of the command :&amp;nbsp;&lt;STRONG&gt;show platform hardware slot R0 ha_port interface stats&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 07:06:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289337#M283171</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-05-09T07:06:39Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289341#M283172</link>
      <description>&lt;P&gt;There are no indications or error counters, except I see multiple Tx fails on active WLC:&lt;/P&gt;
&lt;P&gt;WC-01#show platform software stack-mgr chassis active R0 sdp-counters&lt;BR /&gt;Stack Discovery Protocol (SDP) Counters&lt;/P&gt;
&lt;P&gt;---------------------------------------&lt;/P&gt;
&lt;P&gt;Message Tx Success Tx Fail Rx Success Rx Fail &lt;BR /&gt;------------------------------------------------------------------------------&lt;BR /&gt;Discovery 1883 &lt;STRONG&gt;2&lt;/STRONG&gt; 238 0 &lt;BR /&gt;Neighbor 24047679 &lt;STRONG&gt;55&lt;/STRONG&gt; 12023734 0 &lt;BR /&gt;Keepalive 396228 &lt;STRONG&gt;2416&lt;/STRONG&gt; 394779 0&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 07:22:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289341#M283172</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-05-09T07:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289342#M283173</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp; &amp;nbsp;&lt;FONT color="#FF6600"&gt;&lt;EM&gt;That's not the output from&lt;/EM&gt;&lt;/FONT&gt;&amp;nbsp;&lt;STRONG&gt;show platform hardware slot R0 ha_port interface stats&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 07:25:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289342#M283173</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-05-09T07:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289343#M283174</link>
      <description>&lt;P&gt;HA Port&lt;/P&gt;
&lt;P&gt;ha_port: flags=4163&amp;lt;UP,BROADCAST,RUNNING,MULTICAST&amp;gt; mtu 1500&lt;BR /&gt;inet 169.254.141.20 netmask 255.255.255.0 broadcast 169.254.141.255&lt;BR /&gt;inet6 fe80::fac6:50ff:fe22:2500 prefixlen 64 scopeid 0x20&amp;lt;link&amp;gt;&lt;BR /&gt;ether f8:c6:50:22:25:00 txqueuelen 1000 (Ethernet)&lt;BR /&gt;RX packets 50849464 bytes 6738675926 (6.2 GiB)&lt;BR /&gt;RX errors 0 dropped 0 overruns 0 frame 0&lt;BR /&gt;TX packets 53788973 bytes 16471078111 (15.3 GiB)&lt;BR /&gt;TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0&lt;BR /&gt;device memory 0xe1800000-e2000000&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Settings for ha_port:&lt;BR /&gt;Supported ports: [ TP ]&lt;BR /&gt;Supported link modes: 10baseT/Half 10baseT/Full&lt;BR /&gt;100baseT/Half 100baseT/Full&lt;BR /&gt;1000baseT/Full&lt;BR /&gt;Supported pause frame use: Symmetric&lt;BR /&gt;Supports auto-negotiation: Yes&lt;BR /&gt;Supported FEC modes: Not reported&lt;BR /&gt;Advertised link modes: 10baseT/Half 10baseT/Full&lt;BR /&gt;100baseT/Half 100baseT/Full&lt;BR /&gt;1000baseT/Full&lt;BR /&gt;Advertised pause frame use: Symmetric&lt;BR /&gt;Advertised auto-negotiation: Yes&lt;BR /&gt;Advertised FEC modes: Not reported&lt;BR /&gt;Speed: 1000Mb/s&lt;BR /&gt;Duplex: Full&lt;BR /&gt;Auto-negotiation: on&lt;BR /&gt;Port: Twisted Pair&lt;BR /&gt;PHYAD: 1&lt;BR /&gt;Transceiver: internal&lt;BR /&gt;MDI-X: on (auto)&lt;BR /&gt;Supports Wake-on: pumbg&lt;BR /&gt;Wake-on: g&lt;BR /&gt;Current message level: 0x00000007 (7)&lt;BR /&gt;drv probe link&lt;BR /&gt;Link detected: yes&lt;/P&gt;
&lt;P&gt;NIC statistics:&lt;BR /&gt;rx_packets: 50849465&lt;BR /&gt;tx_packets: 53788975&lt;BR /&gt;rx_bytes: 6942073876&lt;BR /&gt;tx_bytes: 16686251472&lt;BR /&gt;rx_broadcast: 14&lt;BR /&gt;tx_broadcast: 814&lt;BR /&gt;rx_multicast: 22&lt;BR /&gt;tx_multicast: 260&lt;BR /&gt;multicast: 22&lt;BR /&gt;collisions: 0&lt;BR /&gt;rx_crc_errors: 0&lt;BR /&gt;rx_no_buffer_count: 0&lt;BR /&gt;rx_missed_errors: 0&lt;BR /&gt;tx_aborted_errors: 0&lt;BR /&gt;tx_carrier_errors: 0&lt;BR /&gt;tx_window_errors: 0&lt;BR /&gt;tx_abort_late_coll: 0&lt;BR /&gt;tx_deferred_ok: 0&lt;BR /&gt;tx_single_coll_ok: 0&lt;BR /&gt;tx_multi_coll_ok: 0&lt;BR /&gt;tx_timeout_count: 0&lt;BR /&gt;rx_long_length_errors: 0&lt;BR /&gt;rx_short_length_errors: 0&lt;BR /&gt;rx_align_errors: 0&lt;BR /&gt;tx_tcp_seg_good: 0&lt;BR /&gt;tx_tcp_seg_failed: 0&lt;BR /&gt;rx_flow_control_xon: 0&lt;BR /&gt;rx_flow_control_xoff: 0&lt;BR /&gt;tx_flow_control_xon: 0&lt;BR /&gt;tx_flow_control_xoff: 0&lt;BR /&gt;rx_long_byte_count: 6942073876&lt;BR /&gt;tx_dma_out_of_sync: 0&lt;BR /&gt;tx_smbus: 0&lt;BR /&gt;rx_smbus: 0&lt;BR /&gt;dropped_smbus: 0&lt;BR /&gt;os2bmc_rx_by_bmc: 0&lt;BR /&gt;os2bmc_tx_by_bmc: 0&lt;BR /&gt;os2bmc_tx_by_host: 0&lt;BR /&gt;os2bmc_rx_by_host: 0&lt;BR /&gt;tx_hwtstamp_timeouts: 0&lt;BR /&gt;rx_hwtstamp_cleared: 0&lt;BR /&gt;rx_errors: 0&lt;BR /&gt;tx_errors: 0&lt;BR /&gt;tx_dropped: 0&lt;BR /&gt;rx_length_errors: 0&lt;BR /&gt;rx_over_errors: 0&lt;BR /&gt;rx_frame_errors: 0&lt;BR /&gt;rx_fifo_errors: 0&lt;BR /&gt;tx_fifo_errors: 0&lt;BR /&gt;tx_heartbeat_errors: 0&lt;BR /&gt;tx_queue_0_packets: 41049411&lt;BR /&gt;tx_queue_0_bytes: 10760587922&lt;BR /&gt;tx_queue_0_restart: 0&lt;BR /&gt;tx_queue_1_packets: 12739564&lt;BR /&gt;tx_queue_1_bytes: 5710492364&lt;BR /&gt;tx_queue_1_restart: 0&lt;BR /&gt;rx_queue_0_packets: 50849465&lt;BR /&gt;rx_queue_0_bytes: 6738676016&lt;BR /&gt;rx_queue_0_drops: 0&lt;BR /&gt;rx_queue_0_csum_err: 0&lt;BR /&gt;rx_queue_0_alloc_failed: 0&lt;BR /&gt;rx_queue_1_packets: 0&lt;BR /&gt;rx_queue_1_bytes: 0&lt;BR /&gt;rx_queue_1_drops: 0&lt;BR /&gt;rx_queue_1_csum_err: 0&lt;BR /&gt;rx_queue_1_alloc_failed: 0&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 07:28:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289343#M283174</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-05-09T07:28:11Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289345#M283176</link>
      <description>&lt;P&gt;Output of&amp;nbsp;&lt;STRONG&gt;show platform hardware slot R0 ha_port interface stats &lt;/STRONG&gt;attached&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 07:36:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289345#M283176</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-05-09T07:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289369#M283179</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp;Nothing special seen ,as stated also check the&lt;EM&gt; interface counters&lt;/EM&gt; on the switch ports where the RP ports are connected to ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 09:33:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289369#M283179</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-05-09T09:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289387#M283182</link>
      <description>&lt;P&gt;What do you mean by&amp;nbsp;&lt;EM&gt;check the&amp;nbsp;interface counters&amp;nbsp;on the switch ports where the RP ports are connected to?&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;RP ports on WLCs are connected to each other via cable, right?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are using Gi0 for MGMT of WLCs and then TenGig port for connection to uplink switch. There are no interface input/output errors or CRCs visible.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 10:21:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289387#M283182</guid>
      <dc:creator>Scorpioo</dc:creator>
      <dc:date>2025-05-09T10:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289403#M283183</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; -&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1838514"&gt;@Scorpioo&lt;/a&gt;&amp;nbsp; &lt;FONT color="#008000"&gt;&amp;nbsp;&lt;EM&gt;&amp;gt;...&lt;/EM&gt;&lt;/FONT&gt;&lt;SPAN&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;RP ports on WLCs are connected to each other via cable, right?&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Yes , that is&amp;nbsp; supported topology too.&amp;nbsp; When the standby reboots check&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;for&amp;nbsp; crashdumps on it's bootflash&amp;nbsp; ; checkout the commands below the first one&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;having priority&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;STRONG&gt;&amp;nbsp;dir bootflash:/core/ | i core|system-report&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;show version | inc reload&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; show platform&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; show inventory&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;show environment&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; (Remember ; to be executed on the&lt;STRONG&gt; Standby&lt;/STRONG&gt; in this case)&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 11:11:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5289403#M283183</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-05-09T11:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless C9800 update Redundancy settings</title>
      <link>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5290094#M283250</link>
      <description>&lt;P&gt;CSCwo69177&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 23:12:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-c9800-update-redundancy-settings/m-p/5290094#M283250</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-05-12T23:12:00Z</dc:date>
    </item>
  </channel>
</rss>

