<?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: ISE Behaviour if Server down - Fail Open? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344211#M550208</link>
    <description>&lt;P&gt;Without "&lt;SPAN&gt;authentication event server alive action reinitialize&lt;/SPAN&gt;" the endpoint will stay in critical auth until re-authenticated for some other reason. That command forces re-authentication when RADIUS server becomes available again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For fail open, I have the following two commands:&lt;/P&gt;
&lt;P&gt;authentication event server dead action authorize (if you don't put vlan X at the end here, it will fail-open to whatever vlan is configured on the port)&lt;BR /&gt; authentication event server dead action authorize voice&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 07 Mar 2018 16:49:49 GMT</pubDate>
    <dc:creator>agrissimanis</dc:creator>
    <dc:date>2018-03-07T16:49:49Z</dc:date>
    <item>
      <title>ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3331973#M550195</link>
      <description>&lt;P&gt;I want to understand the switchport or ISE config required that if switch cannot contact ISE server that the authentication fails open&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe it's called Fail Open, but I want to make sure if the ISE server is unreachable that user still connects to VLAN configured on port&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:45:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3331973#M550195</guid>
      <dc:creator>roger perkin</dc:creator>
      <dc:date>2020-02-21T18:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3332032#M550198</link>
      <description>&lt;P&gt;Hi Roger,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try these interface level commands: &lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;authentication event server dead action reinitialize vlan X&lt;BR /&gt;&amp;nbsp;authentication event server dead action authorize voice&lt;/P&gt;
&lt;P&gt;&amp;nbsp;authentication event server alive action reinitialize&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;// You will need the global dead-time criteria set in order to detect a dead AAA server&lt;/P&gt;
&lt;P&gt;radius-server dead-criteria time 3 tries 2&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2018 20:35:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3332032#M550198</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2018-02-15T20:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3332048#M550202</link>
      <description>&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So to be clear&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt; global command&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;radius-server dead-criteria time 3 tries 2&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;EM&gt;Wait 2 x 3 seconds before marking Radius Server as dead&amp;nbsp;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Interface command&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;authentication event server dead action reinitialize vlan X&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;If Radius server is dead reinitialise the port into vlan X (Could be another VLAN or could be same access VLAN)&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;authentication event server dead action authorize voice&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;If Radius server is dead - allow voice vlan&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;authentication event server alive action reinitialize&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;When the Radius server comes online - reinitialize authentications&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So if I have 2 Radius Servers with the above configuration it would try ISE 1 for 6 seconds and then ISE 2 for 6 seconds and then reinitialize port into specified VLAN&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2018 21:03:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3332048#M550202</guid>
      <dc:creator>roger perkin</dc:creator>
      <dc:date>2018-02-15T21:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3342586#M550203</link>
      <description>Hello Guys,&lt;BR /&gt;&lt;BR /&gt;I got a question on this. If  = "authentication event server alive action reinitialize" is not included in switchport configuration what will be the behaviour? Will it not go back to authentication from the ISE until restarted?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;George</description>
      <pubDate>Mon, 05 Mar 2018 16:43:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3342586#M550203</guid>
      <dc:creator>georgehewittuk1</dc:creator>
      <dc:date>2018-03-05T16:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344211#M550208</link>
      <description>&lt;P&gt;Without "&lt;SPAN&gt;authentication event server alive action reinitialize&lt;/SPAN&gt;" the endpoint will stay in critical auth until re-authenticated for some other reason. That command forces re-authentication when RADIUS server becomes available again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For fail open, I have the following two commands:&lt;/P&gt;
&lt;P&gt;authentication event server dead action authorize (if you don't put vlan X at the end here, it will fail-open to whatever vlan is configured on the port)&lt;BR /&gt; authentication event server dead action authorize voice&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2018 16:49:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344211#M550208</guid>
      <dc:creator>agrissimanis</dc:creator>
      <dc:date>2018-03-07T16:49:49Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344213#M550214</link>
      <description>Thanks for the reply - When you say the endpoint (port) stays in critical auth until re-autentication. The behaviour of the authentication command is this until a new host is connected or after so long a time?  Its not so clear in my mind if you can shed some light.&lt;BR /&gt;&lt;BR /&gt;Thanks again</description>
      <pubDate>Wed, 07 Mar 2018 16:56:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344213#M550214</guid>
      <dc:creator>georgehewittuk1</dc:creator>
      <dc:date>2018-03-07T16:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Behaviour if Server down - Fail Open?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344308#M550219</link>
      <description>&lt;P&gt;Absolutely, if a new host was connected to the port then there would be a new authentication event, and if the radius server is up at that point then the request would go to ISE. Or if you have a&amp;nbsp;periodic re-authentication enabled then the old host would get re-authenticated when the timer expires. That command re-authenticates endpoints in critical auth when at least one RADIUS server becomes available.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Mar 2018 19:03:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-if-server-down-fail-open/m-p/3344308#M550219</guid>
      <dc:creator>agrissimanis</dc:creator>
      <dc:date>2018-03-07T19:03:23Z</dc:date>
    </item>
  </channel>
</rss>

