<?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: Recent 802.1X failure on Meraki Access point in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519418#M307567</link>
    <description>&lt;P&gt;This page might help : &lt;A href="https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alert_-_Recent_802.1X_Failure" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alert_-_Recent_802.1X_Failure&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Seems like your radius server is not responding to the testing done by Meraki : &lt;EM&gt;A node displays the &lt;STRONG&gt;Recent 802.1X Failure &lt;/STRONG&gt;alert when the &lt;STRONG&gt;RADIUS testing&lt;/STRONG&gt; feature is enabled and it doesn't get a reply from one or more of the configured RADIUS servers. The alert may just mean that the device didn't get a reply from the server once due to network conditions in that particular moment. Please keep reading to verify if is this a one-time situation or if there's a bigger problem.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Mar 2024 11:50:39 GMT</pubDate>
    <dc:creator>Raphael_L</dc:creator>
    <dc:date>2024-03-15T11:50:39Z</dc:date>
    <item>
      <title>Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519416#M307565</link>
      <description>&lt;P&gt;There are 4 AP' in the network, 2 AP's showing  802.1X failure, Remaining 2 AP's fine. All the AP's connected same switch. &lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 04:31:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519416#M307565</guid>
      <dc:creator>Bhavani Shankar</dc:creator>
      <dc:date>2024-03-15T04:31:01Z</dc:date>
    </item>
    <item>
      <title>Re: Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519417#M307566</link>
      <description>&lt;P&gt;Very generic, what are you using as a basis for authentication? Meraki cloud or an external radius server?&lt;/P&gt;&lt;P&gt;If it is a radius server, are the APs registered as radius clients correctly?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 08:44:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519417#M307566</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2024-03-15T08:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519418#M307567</link>
      <description>&lt;P&gt;This page might help : &lt;A href="https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alert_-_Recent_802.1X_Failure" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alert_-_Recent_802.1X_Failure&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Seems like your radius server is not responding to the testing done by Meraki : &lt;EM&gt;A node displays the &lt;STRONG&gt;Recent 802.1X Failure &lt;/STRONG&gt;alert when the &lt;STRONG&gt;RADIUS testing&lt;/STRONG&gt; feature is enabled and it doesn't get a reply from one or more of the configured RADIUS servers. The alert may just mean that the device didn't get a reply from the server once due to network conditions in that particular moment. Please keep reading to verify if is this a one-time situation or if there's a bigger problem.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 11:50:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519418#M307567</guid>
      <dc:creator>Raphael_L</dc:creator>
      <dc:date>2024-03-15T11:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519419#M307568</link>
      <description>&lt;P&gt;Thank you for suggestion. &lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 05:08:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519419#M307568</guid>
      <dc:creator>Bhavani Shankar</dc:creator>
      <dc:date>2024-03-18T05:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519420#M307569</link>
      <description>&lt;P&gt;Thank you for your information..Here Using External radius server..&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 05:09:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519420#M307569</guid>
      <dc:creator>Bhavani Shankar</dc:creator>
      <dc:date>2024-03-18T05:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519421#M307570</link>
      <description>&lt;P&gt;Hi &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/105273"&gt;@Bhavani Shankar&lt;/A&gt;, &lt;/P&gt;&lt;P&gt;I would advise taking a packet capture on the upstream switch port that the AP is plugged into. Verify if you are getting any sort of RADIUS return traffic from the RADIUS server. If you are not, take a capture directly above the RADIUS server to see if it’s even getting the initial RADIUS responses and possibly investigate the RADIUS log messages and configuration to better understand why it’s not replying back.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 17:41:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519421#M307570</guid>
      <dc:creator>CFStevens</dc:creator>
      <dc:date>2024-03-18T17:41:44Z</dc:date>
    </item>
    <item>
      <title>Re: Recent 802.1X failure on Meraki Access point</title>
      <link>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519422#M307571</link>
      <description>&lt;P&gt;Thanks for the update..&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2024 10:29:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/recent-802-1x-failure-on-meraki-access-point/m-p/5519422#M307571</guid>
      <dc:creator>Bhavani Shankar</dc:creator>
      <dc:date>2024-03-28T10:29:36Z</dc:date>
    </item>
  </channel>
</rss>

