<?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: dot1x interface config interpretation in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3819529#M24885</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp; explained it perfectly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just wanted to add few thing to make your config more optimal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;add also this on the switcvhport:&lt;/P&gt;
&lt;P&gt;authentication event server alive action reinitialize&amp;nbsp; (this will reauthenticate the interface who is critical VLAN where the AAA server is marked ALIVE).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In global config&lt;/P&gt;
&lt;P&gt;radius-server dead-criteria time 5 tries 3 (declare the AAA as dead if no reply within 15 sec)&lt;BR /&gt;radius-server deadtime 10&amp;nbsp; (if server is DEAD after 10 minutes try to Probe with the dummy user)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in the raduis server config add a dummy user with Probe-ON otherwise if AAA server is dead then you will have a creapie authentication looping&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;radius server RADSERVER1&lt;BR /&gt;address ipv4 10.7.1.200 auth-port 1812 acct-port 1813&lt;BR /&gt;automate-tester username dummy ignore-acct-port probe-on&lt;BR /&gt;key 7XXXXXXXXYYYYY&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please rate if helpfull&lt;/P&gt;</description>
    <pubDate>Thu, 14 Mar 2019 13:01:32 GMT</pubDate>
    <dc:creator>bern81</dc:creator>
    <dc:date>2019-03-14T13:01:32Z</dc:date>
    <item>
      <title>dot1x interface config interpretation</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3816396#M24881</link>
      <description>&lt;P&gt;interface GigabitEthernetX/X&lt;BR /&gt;description xxxx&lt;BR /&gt;switchport&lt;BR /&gt;&lt;FONT color="#000000"&gt;switchport access vlan 22&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;switchport mode access&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;switchport voice vlan 26&lt;/FONT&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;authentication event server dead action authorize vlan 22&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;authentication event server dead action authorize voice&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;authentication event no-response action authorize vlan 27&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;authentication host-mode multi-domain&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;authentication port-control auto&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;authentication violation replace&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;mls qos trust dscp&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;dot1x pae authenticator&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;no cdp enable&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;can someone please tell me the meaning of the bold commands?&amp;nbsp; I need to understand the policy implications.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 16:33:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3816396#M24881</guid>
      <dc:creator>davinci</dc:creator>
      <dc:date>2019-03-08T16:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x interface config interpretation</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3816397#M24883</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;authentication event server dead action authorize vlan 22&lt;/STRONG&gt;&lt;/EM&gt; = authorize session into data vlan 22 when the radius server(s) are all marked dead&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;authentication event server dead action authorize voice&lt;/STRONG&gt;&lt;/EM&gt; = authorize voice when the radius server(s) are all marked dead&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;authentication event no-response action authorize vlan 27&lt;/STRONG&gt;&lt;/EM&gt; = authorize guest vlan (when user failed dot1x and mab)&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;authentication host-mode multi-domain&lt;/STRONG&gt;&lt;/EM&gt; = allows an IP Phone and a PC to authenticate on the same switch port&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;authentication port-control auto&lt;/STRONG&gt;&lt;/EM&gt; = authentication enabled on a port&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;authentication violation replace&lt;/STRONG&gt;&lt;/EM&gt; = upon violation, remove the current session and authenticates with the new host.&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;mls qos trust dscp&lt;/STRONG&gt;&lt;/EM&gt; = Qos related, not dot1x&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;dot1x pae authenticator&lt;/STRONG&gt; &lt;/EM&gt;= Enables 802.1X authentication on the port with default parameters.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 16:45:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3816397#M24883</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2019-03-08T16:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x interface config interpretation</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3819529#M24885</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp; explained it perfectly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just wanted to add few thing to make your config more optimal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;add also this on the switcvhport:&lt;/P&gt;
&lt;P&gt;authentication event server alive action reinitialize&amp;nbsp; (this will reauthenticate the interface who is critical VLAN where the AAA server is marked ALIVE).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In global config&lt;/P&gt;
&lt;P&gt;radius-server dead-criteria time 5 tries 3 (declare the AAA as dead if no reply within 15 sec)&lt;BR /&gt;radius-server deadtime 10&amp;nbsp; (if server is DEAD after 10 minutes try to Probe with the dummy user)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in the raduis server config add a dummy user with Probe-ON otherwise if AAA server is dead then you will have a creapie authentication looping&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;radius server RADSERVER1&lt;BR /&gt;address ipv4 10.7.1.200 auth-port 1812 acct-port 1813&lt;BR /&gt;automate-tester username dummy ignore-acct-port probe-on&lt;BR /&gt;key 7XXXXXXXXYYYYY&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please rate if helpfull&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2019 13:01:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3819529#M24885</guid>
      <dc:creator>bern81</dc:creator>
      <dc:date>2019-03-14T13:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x interface config interpretation</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3839007#M24887</link>
      <description>&lt;P&gt;awesome, thanks for the comments&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2019 20:51:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3839007#M24887</guid>
      <dc:creator>davinci</dc:creator>
      <dc:date>2019-04-15T20:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x interface config interpretation</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3958064#M24888</link>
      <description>&lt;P&gt;I have a problem where workstations (supplicants) keep getting kicked into the guest vlan 27 seemingly inadvertently.&amp;nbsp; After I shut/no shut the port then they regain access via regular data vlan 22.&amp;nbsp; What could possibly be the reason?&amp;nbsp; Is there a workaround or way to eliminate this issue from occuring?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2019 16:15:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-interface-config-interpretation/m-p/3958064#M24888</guid>
      <dc:creator>davinci</dc:creator>
      <dc:date>2019-11-13T16:15:54Z</dc:date>
    </item>
  </channel>
</rss>

