<?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: AAA Radius server Failure- ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296324#M565670</link>
    <description>&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;If we run this command, I believe this will bring the PSN node up. Will there be any impact for the end-users during the time-frame if ASA is forwarding the Radius Authentication requests to ISE&amp;nbsp; (if the ISE isn't responding or failing to the Radius Authentication for some reason)?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;-No you will be fine when running the test AAA command.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We've not specified the Reactivation mode and I believe it's depletion mode by default. Is it correct?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;-AFAIK, yes this is correct.&amp;nbsp; I believe the default settings are:&lt;/P&gt;
&lt;P&gt;Depletion &lt;BR /&gt;Dead time: 10 min&lt;BR /&gt;max fails: 3&lt;/P&gt;
&lt;P&gt;You do have the ability to switch it to Timed mode which will attempt to reactive failed AAA servers after X amount of time.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2021 19:38:13 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2021-02-23T19:38:13Z</dc:date>
    <item>
      <title>AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4295321#M565641</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;We've an ISE as an authentication server for the Remote access VPN users with ASA as the Authenticator with RSA as MFA. Noticed out of 2 PSN, ASA has marked the primary one as failed and authenticating via the secondary PSN node.&lt;/P&gt;&lt;P&gt;We've not specified the reactivation mode and I believe it's depletion by default.&amp;nbsp;Basic health checks of the ISE node looks good.&lt;/P&gt;&lt;P&gt;Not sure what to check. Can someone please assist.&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2021 16:24:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4295321#M565641</guid>
      <dc:creator>Srinivasan Nagarajan</dc:creator>
      <dc:date>2021-02-22T16:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296054#M565660</link>
      <description>&lt;P&gt;Assuming when you check, you run a # show aaa-server and the one shows as Active &amp;amp; the other does not?&lt;/P&gt;
&lt;P&gt;Some routine checks:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Can you ping the failed psn?&lt;/P&gt;
&lt;P&gt;-Are the PSNs located in the same subnet/location?&lt;/P&gt;
&lt;P&gt;-Are there possibly ACLs somewhere in the path blocking the ASA?&lt;/P&gt;
&lt;P&gt;-Have you attempted to run any debugs from the ASA to gather more log/failure reasons?&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 14:15:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296054#M565660</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-23T14:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296068#M565661</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, Both are in the same subnet and I'm able to ping the ISE&lt;/P&gt;&lt;P&gt;There is no ACL in the path and it's showing as 'FAILED' when I give 'show aaa-server protocol radius'&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 14:33:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296068#M565661</guid>
      <dc:creator>Srinivasan Nagarajan</dc:creator>
      <dc:date>2021-02-23T14:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296076#M565662</link>
      <description>&lt;P&gt;Are both PSNs in the same AAA group &amp;amp; referenced in same AAA list?&amp;nbsp; Are both PSNs properly setup with right persona in ISE? Have you attempted to run any tcpdumps on ISE side to further tshoot?&lt;/P&gt;
&lt;P&gt;-Maybe try running debugs on ASA side.&lt;/P&gt;
&lt;P&gt;-Also, you can test authentication via:&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;SPAN&gt;test aaa-server authentication GROUP_NAME username johndoe password cisco123&lt;/SPAN&gt;&amp;nbsp;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 14:46:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296076#M565662</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-23T14:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296082#M565663</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've not run tcpdumps on ISE node. We manage client network and we dont have the username/password for the test aaa-server command to run.&lt;/P&gt;&lt;P&gt;&amp;nbsp;If we run this command, I believe this will bring the PSN node up. Will there be any impact for the end-users during the time-frame if ASA is forwarding the Radius Authentication requests to ISE&amp;nbsp; (if the ISE isn't responding or failing to the Radius Authentication for some reason)?&lt;/P&gt;&lt;P&gt;We've not specified the Reactivation mode and I believe it's depletion mode by default. Is it correct?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 15:54:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296082#M565663</guid>
      <dc:creator>Srinivasan Nagarajan</dc:creator>
      <dc:date>2021-02-23T15:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296324#M565670</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;If we run this command, I believe this will bring the PSN node up. Will there be any impact for the end-users during the time-frame if ASA is forwarding the Radius Authentication requests to ISE&amp;nbsp; (if the ISE isn't responding or failing to the Radius Authentication for some reason)?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;-No you will be fine when running the test AAA command.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We've not specified the Reactivation mode and I believe it's depletion mode by default. Is it correct?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;-AFAIK, yes this is correct.&amp;nbsp; I believe the default settings are:&lt;/P&gt;
&lt;P&gt;Depletion &lt;BR /&gt;Dead time: 10 min&lt;BR /&gt;max fails: 3&lt;/P&gt;
&lt;P&gt;You do have the ability to switch it to Timed mode which will attempt to reactive failed AAA servers after X amount of time.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 19:38:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296324#M565670</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-23T19:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296643#M565677</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here we've username+passcode for RA VPN (Identity source is RSA and not AD), so if I enter the username/password using test aaa-server command, it's showing AAA failure.&lt;/P&gt;&lt;P&gt;Can you please let me know is there any other way to bring the ISE node up for authentication?&lt;/P&gt;&lt;P&gt;And please let me know which one is preferred? Is it timed or depletion mode?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 04:11:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296643#M565677</guid>
      <dc:creator>Srinivasan Nagarajan</dc:creator>
      <dc:date>2021-02-24T04:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296946#M565681</link>
      <description>&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Timed mode—&lt;/STRONG&gt;The failed or deactivated servers are reactivated after 30 seconds of downtime.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Depletion mode—&lt;/STRONG&gt;The failed or deactivated servers remain inactive until all other servers within the configured group are inactive.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;Can you please let me know is there any other way to bring the ISE node up for authentication?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I would suggest testing with timed mode.&amp;nbsp; Have you tried completely removing the failed AAA node, and then re-adding it back to config?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 14:12:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296946#M565681</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-24T14:12:21Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296953#M565682</link>
      <description>&lt;P&gt;Thanks Mike.&lt;/P&gt;&lt;P&gt;1. When using timed mode, if the server is down, then ASA will try to authenticate with it every 30seconds, affecting the users authentication requests?&lt;/P&gt;&lt;P&gt;2.Can you please suggest how to utilize the test aaa-server command when RSA is used as the Identity source?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 14:22:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4296953#M565682</guid>
      <dc:creator>Srinivasan Nagarajan</dc:creator>
      <dc:date>2021-02-24T14:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4297002#M565683</link>
      <description>&lt;P&gt;1. When using timed mode, if the server is down, then ASA will try to authenticate with it every 30seconds, affecting the users authentication requests?&lt;/P&gt;
&lt;P&gt;-This will not affect users auth request as you have two AAA servers configured.&lt;/P&gt;
&lt;P&gt;2.Can you please suggest how to utilize the test aaa-server command when RSA is used as the Identity source?&lt;/P&gt;
&lt;P&gt;-This is a good question that I am not 100% sure of.&amp;nbsp; The test AAA command will aide in verifying if your radius server/shared secret are correct.&amp;nbsp; This "test" command typically uses username/password to verify against the remote AAA source.&amp;nbsp; I suppose as a workaround you could quickly setup a local identity (user/pass) within ISE to then simply use with your test command just to see if that will bring the PSN back alive.&amp;nbsp; Keep in mind you will need some sort of basic policy that will allow your test to hit/match.&lt;/P&gt;
&lt;P&gt;Lastly, IMO you have several options here to test.&amp;nbsp; If none of them suffice I would suggest getting with TAC.&amp;nbsp; HTH!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 15:19:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4297002#M565683</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-24T15:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4297439#M565700</link>
      <description>&lt;P&gt;Thanks Mike.&lt;/P&gt;&lt;P&gt;I manually bring the server by the below command and it start authenticating as expected.&lt;/P&gt;&lt;P&gt;ciscoasa# aaa-server active host X.X.X.X&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Final one, Would like to understand why it was marked as 'Failed' though we've reachability? Any thoughts?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2021 08:01:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4297439#M565700</guid>
      <dc:creator>Srinivasan Nagarajan</dc:creator>
      <dc:date>2021-02-25T08:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Radius server Failure- ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4297640#M565707</link>
      <description>&lt;P&gt;Perhaps loss of connectivity at one point, honestly without digging deeper into logs everything would just be assumption based.&amp;nbsp; I would suggest looking at internal logs.&amp;nbsp; Glad you were able to manually active it again.&amp;nbsp; As a reminder, with depletion mode t&lt;SPAN&gt;he failed or deactivated servers remain inactive until all other servers within the configured group are inactive.&amp;nbsp; In your case I would keep an eye on them or consider switching the config to timed mode.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2021 13:54:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-radius-server-failure-ise/m-p/4297640#M565707</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-25T13:54:15Z</dc:date>
    </item>
  </channel>
</rss>

