<?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: After power outage, WLC not correctly transacting with RADIUS serv in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615568#M242364</link>
    <description>&lt;P&gt;Was the WLC config saved before the power failure?&amp;nbsp;&amp;nbsp;Maybe it's using the wrong radius secret for example?&lt;/P&gt;
&lt;P&gt;Get a packet capture to see what is happening.&lt;/P&gt;
&lt;P&gt;What do the radius server logs show?&lt;/P&gt;
&lt;P&gt;Try to re-apply the correct secret.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 May 2022 14:13:48 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2022-05-23T14:13:48Z</dc:date>
    <item>
      <title>After power outage, WLC not correctly transacting with RADIUS server.</title>
      <link>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615387#M242349</link>
      <description>&lt;P&gt;After power outage WLC&amp;nbsp;AIR-CT5508-100-K9 is not correctly communicating with RADIUS server. IP communication between 2 devices is intact. Cisco APs are up but clients failing communication because of authentication.&lt;STRONG&gt; Aruba APs connected to same WLC are up and servicing wireless clients fine.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;1. Why is WLC not correctly communicating with RADIUS server?&lt;/P&gt;
&lt;P&gt;2. How can I make this connection healthy again?&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 11:19:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615387#M242349</guid>
      <dc:creator>jonathan.maxwell</dc:creator>
      <dc:date>2022-05-23T11:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: After power outage, WLC not correctly transacting with RADIUS serv</title>
      <link>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615398#M242352</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;"Aruba APs connected to same WLC are up and servicing wireless clients fine."&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tell me&amp;nbsp; more about it please.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can try to guess here what might be happening but will not help you. We need logs to help you. Connect to the WLC, choose one failing client and issue "debug client 'mac address' . Save the output while trying to connect. Then, share the result.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And share the output of "&lt;SPAN&gt;show radius auth statistics &lt;/SPAN&gt;" from the WLC.&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 11:34:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615398#M242352</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2022-05-23T11:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: After power outage, WLC not correctly transacting with RADIUS serv</title>
      <link>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615486#M242353</link>
      <description>&lt;P&gt;WLC loss client auth data but radius still have it?&lt;/P&gt;&lt;P&gt;check this point&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 15:26:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615486#M242353</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-05-23T15:26:53Z</dc:date>
    </item>
    <item>
      <title>Re: After power outage, WLC not correctly transacting with RADIUS serv</title>
      <link>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615568#M242364</link>
      <description>&lt;P&gt;Was the WLC config saved before the power failure?&amp;nbsp;&amp;nbsp;Maybe it's using the wrong radius secret for example?&lt;/P&gt;
&lt;P&gt;Get a packet capture to see what is happening.&lt;/P&gt;
&lt;P&gt;What do the radius server logs show?&lt;/P&gt;
&lt;P&gt;Try to re-apply the correct secret.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 14:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615568#M242364</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-05-23T14:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: After power outage, WLC not correctly transacting with RADIUS serv</title>
      <link>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615593#M242367</link>
      <description>&lt;P&gt;Thank you all for your input. I appreciate it indeed.&lt;/P&gt;
&lt;P&gt;The problem is solved...&lt;/P&gt;
&lt;P&gt;The WLC's were authenticating through an AD network policy server to a radius server. After the power outage it is unknown why the AD radius server authentication is failing.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The solution was to eliminate the authentication path through the AD network policy server, and instead connect the WLC’s directly to RADIUS servers.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Thank you all.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 15:05:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/after-power-outage-wlc-not-correctly-transacting-with-radius/m-p/4615593#M242367</guid>
      <dc:creator>jonathan.maxwell</dc:creator>
      <dc:date>2022-05-23T15:05:54Z</dc:date>
    </item>
  </channel>
</rss>

