<?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:radius and dot1x in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/radius-and-dot1x/m-p/2017960#M163627</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The radius server is only detected dead when it doesn't respond to a radius request based on its dead criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please look up the dead criteria using the software configuration guide for your switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active clients will not suffer connectivity issues when the radius server goes down. Only client requesting authentication will experience some latency but that is based on the radius dead criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Sep 2012 13:01:18 GMT</pubDate>
    <dc:creator>Tarik Admani</dc:creator>
    <dc:date>2012-09-26T13:01:18Z</dc:date>
    <item>
      <title>radius and dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-and-dot1x/m-p/2017959#M163599</link>
      <description>&lt;P&gt;We are deploying dot1x in our network.&lt;/P&gt;&lt;P&gt;We have deployed 2 ISE policy service nodes. I am seeing a behavior in which switch is not detecting radius server becoming unreachable/reachable quick enough. It detects that radius server is down, but after much delay.&lt;/P&gt;&lt;P&gt;How can I make sure that the radius server down/up events are detected quickly?&lt;/P&gt;&lt;P&gt;We also have something in mind where when the switch detects that radius server has become unreachable, all the dot1x configurd ports will be force-authorized. &lt;/P&gt;&lt;P&gt;Now during the time when the radius-server went down and when the ports became force-authorized, will the clients suffer any loss of connectivity?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:35:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-and-dot1x/m-p/2017959#M163599</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2019-03-11T02:35:34Z</dc:date>
    </item>
    <item>
      <title>Re:radius and dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-and-dot1x/m-p/2017960#M163627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The radius server is only detected dead when it doesn't respond to a radius request based on its dead criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please look up the dead criteria using the software configuration guide for your switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active clients will not suffer connectivity issues when the radius server goes down. Only client requesting authentication will experience some latency but that is based on the radius dead criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2012 13:01:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-and-dot1x/m-p/2017960#M163627</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-09-26T13:01:18Z</dc:date>
    </item>
  </channel>
</rss>

