<?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 Token Server or External Radius Server Down in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436283#M511226</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;I think AuthC policy should be able to accomodate this.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;If Process failed then "Drop"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Mar 2018 20:24:37 GMT</pubDate>
    <dc:creator>umahar</dc:creator>
    <dc:date>2018-03-28T20:24:37Z</dc:date>
    <item>
      <title>Radius Token Server or External Radius Server Down</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436282#M511225</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the event that a radius token server or proxy radius server goes down will ISE send an access-reject back to the NADs or will ISE not send any response back and the NADs will mark ISE server down sending the endpoints into critical auth vlan ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2018 20:08:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436282#M511225</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2018-03-28T20:08:32Z</dc:date>
    </item>
    <item>
      <title>Re: Radius Token Server or External Radius Server Down</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436283#M511226</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;I think AuthC policy should be able to accomodate this.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;If Process failed then "Drop"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2018 20:24:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436283#M511226</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2018-03-28T20:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: Radius Token Server or External Radius Server Down</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436284#M511227</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The options do not seem applicable to external RADIUS server sequence. I did a quick test in my lab and got below so it looks like always drop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" class="content_table"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="31%"&gt; Event&lt;/TD&gt;&lt;TD style="color: red;" width="69%"&gt; 5405 RADIUS Request dropped &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="31%"&gt; Failure Reason &lt;/TD&gt;&lt;TD style="color: red;" width="69%"&gt; 11353 No more external RADIUS servers; can't perform failover &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="31%"&gt; Resolution &lt;/TD&gt;&lt;TD width="69%"&gt; Verify the following: At least one of the remote RADIUS servers in the ISE proxy service is up and configured properly ; Shared secret specified in the ISE proxy service for every remote RADIUS server is same as the shared secret specified for the ISE server ; Port of every remote RADIUS server is properly specified in the ISE proxy service. &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="31%"&gt; Root cause &lt;/TD&gt;&lt;TD width="69%"&gt; Failover is not possible because no more external RADIUS servers are configured. Dropping the request. &lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case of RADIUS token server, you are correct that the server timeouts are treated as process failures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="3" class="content_table_steps"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt; &lt;/TD&gt;&lt;TD&gt; 24616 &lt;/TD&gt;&lt;TD&gt; RADIUS token identity store received timeout error &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt; &lt;/TD&gt;&lt;TD&gt; 22059 &lt;/TD&gt;&lt;TD&gt; The advanced option that is configured for process failure is used &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt; &lt;/TD&gt;&lt;TD&gt; 22062 &lt;/TD&gt;&lt;TD&gt; The 'Drop' advanced option is configured in case of a failed authentication request &lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2018 05:09:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-token-server-or-external-radius-server-down/m-p/3436284#M511227</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-03-29T05:09:36Z</dc:date>
    </item>
  </channel>
</rss>

