<?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 IBNS 2.0 and Switch Configuration in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3095414#M25404</link>
    <description>&lt;P&gt;I am building a&amp;nbsp;dot1x configuration for my switches. &amp;nbsp;I am using the new-style (authentication display config-mode). &amp;nbsp;I have built the configuration to work correctly for MAB and dot1x authenticates successfully. &amp;nbsp;I am at the point of creating the configuration to handle the exceptions. &amp;nbsp;Currently I am focused on if the AAA server is down.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;So does any have any sample configurations on how to fail open when the AAA server is down? &amp;nbsp;Possibly try retry authentication after a period of time.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The current configuration is below. &amp;nbsp;My (failed) attempts to included proper handling of the AAA being down are included.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;class-map type control subscriber match-all DOT1X_NO_RESP&lt;BR /&gt; match method dot1x&lt;BR /&gt; match result-type method dot1x agent-not-found&lt;BR /&gt;class-map type control subscriber match-all MAB_FAILED&lt;BR /&gt; match method mab&lt;BR /&gt; match result-type method mab authoritative&lt;BR /&gt;class-map type control subscriber match-all SERVER_DOWN&lt;BR /&gt; match result-type aaa-timeout&lt;BR /&gt;class-map type control subscriber match-all dot1x_FAILED_PASSWORD&lt;BR /&gt; match method dot1x&lt;BR /&gt; match result-type authoritative&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;policy-map type control subscriber user_default&lt;BR /&gt; event session-started match-all&lt;BR /&gt; 10 class always do-until-failure&lt;BR /&gt; 10 authenticate using dot1x priority 10&lt;BR /&gt; 20 authenticate using mab priority 20&lt;BR /&gt; event authentication-failure match-first&lt;BR /&gt; 10 class SERVER_DOWN do-until-failure&lt;BR /&gt; 10 authorize&lt;BR /&gt; 20 class MAB_FAILED do-until-failure&lt;BR /&gt; 10 terminate mab&lt;BR /&gt; 20 activate service-template null_vlan&lt;BR /&gt; 30 authentication-restart 60&lt;BR /&gt; 30 class always do-until-failure&lt;BR /&gt; 10 terminate dot1x&lt;BR /&gt; 20 terminate mab&lt;BR /&gt; 30 activate service-template null_vlan&lt;BR /&gt; 40 authentication-restart 60&lt;BR /&gt; event agent-found match-all&lt;BR /&gt; 10 class always do-until-failure&lt;BR /&gt; 10 terminate mab&lt;BR /&gt; 20 authenticate using dot1x priority 10&lt;BR /&gt; event timer-expiry match-all&lt;BR /&gt; 10 class SERVER_DOWN do-until-failure&lt;BR /&gt; 10 authorize&lt;BR /&gt; event absolute-timeout match-all&lt;BR /&gt; 10 class SERVER_DOWN do-until-failure&lt;BR /&gt; 10 authorize&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 07:56:56 GMT</pubDate>
    <dc:creator>rmeans</dc:creator>
    <dc:date>2019-03-11T07:56:56Z</dc:date>
    <item>
      <title>IBNS 2.0 and Switch Configuration</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3095414#M25404</link>
      <description>&lt;P&gt;I am building a&amp;nbsp;dot1x configuration for my switches. &amp;nbsp;I am using the new-style (authentication display config-mode). &amp;nbsp;I have built the configuration to work correctly for MAB and dot1x authenticates successfully. &amp;nbsp;I am at the point of creating the configuration to handle the exceptions. &amp;nbsp;Currently I am focused on if the AAA server is down.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;So does any have any sample configurations on how to fail open when the AAA server is down? &amp;nbsp;Possibly try retry authentication after a period of time.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The current configuration is below. &amp;nbsp;My (failed) attempts to included proper handling of the AAA being down are included.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;class-map type control subscriber match-all DOT1X_NO_RESP&lt;BR /&gt; match method dot1x&lt;BR /&gt; match result-type method dot1x agent-not-found&lt;BR /&gt;class-map type control subscriber match-all MAB_FAILED&lt;BR /&gt; match method mab&lt;BR /&gt; match result-type method mab authoritative&lt;BR /&gt;class-map type control subscriber match-all SERVER_DOWN&lt;BR /&gt; match result-type aaa-timeout&lt;BR /&gt;class-map type control subscriber match-all dot1x_FAILED_PASSWORD&lt;BR /&gt; match method dot1x&lt;BR /&gt; match result-type authoritative&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;policy-map type control subscriber user_default&lt;BR /&gt; event session-started match-all&lt;BR /&gt; 10 class always do-until-failure&lt;BR /&gt; 10 authenticate using dot1x priority 10&lt;BR /&gt; 20 authenticate using mab priority 20&lt;BR /&gt; event authentication-failure match-first&lt;BR /&gt; 10 class SERVER_DOWN do-until-failure&lt;BR /&gt; 10 authorize&lt;BR /&gt; 20 class MAB_FAILED do-until-failure&lt;BR /&gt; 10 terminate mab&lt;BR /&gt; 20 activate service-template null_vlan&lt;BR /&gt; 30 authentication-restart 60&lt;BR /&gt; 30 class always do-until-failure&lt;BR /&gt; 10 terminate dot1x&lt;BR /&gt; 20 terminate mab&lt;BR /&gt; 30 activate service-template null_vlan&lt;BR /&gt; 40 authentication-restart 60&lt;BR /&gt; event agent-found match-all&lt;BR /&gt; 10 class always do-until-failure&lt;BR /&gt; 10 terminate mab&lt;BR /&gt; 20 authenticate using dot1x priority 10&lt;BR /&gt; event timer-expiry match-all&lt;BR /&gt; 10 class SERVER_DOWN do-until-failure&lt;BR /&gt; 10 authorize&lt;BR /&gt; event absolute-timeout match-all&lt;BR /&gt; 10 class SERVER_DOWN do-until-failure&lt;BR /&gt; 10 authorize&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:56:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3095414#M25404</guid>
      <dc:creator>rmeans</dc:creator>
      <dc:date>2019-03-11T07:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 and Switch Configuration</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3358131#M25405</link>
      <description>&lt;P&gt;you can refer to the guide documented here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/identity-based-networking-services/whitepaper_C11-729965.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/identity-based-networking-services/whitepaper_C11-729965.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class=" pBodyIndentCMT"&gt;it has sample configs and descriptions to reauth mab and dot1x automatically if radius is unreachable&lt;/DIV&gt;</description>
      <pubDate>Fri, 30 Mar 2018 16:05:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3358131#M25405</guid>
      <dc:creator>Sandeep Ramakrishnan</dc:creator>
      <dc:date>2018-03-30T16:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 and Switch Configuration</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3774447#M25406</link>
      <description>&lt;P&gt;Is there a newer version of the guide for ISE 2.x? I realize most things will be the same, but I'm curious if there are any differences.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jan 2019 21:19:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-and-switch-configuration/m-p/3774447#M25406</guid>
      <dc:creator>Michael Thornton</dc:creator>
      <dc:date>2019-01-07T21:19:48Z</dc:date>
    </item>
  </channel>
</rss>

