<?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 Authentication Open Failure in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054368#M152766</link>
    <description>&lt;P&gt;Is there away to stop the port from reauthenticating when a device fails to open. I am trying to set up low-impact mode on a wired network. And I have some WYSE terminals that I don't want to authenticate to the network so I would like them to fail open with an ACL limiting their access. However the switch continues to try and authenticate the device even after it has failed authentication. This is causing my logs on ISE to be full of bogus authentication failures. Is there a way to limit thoses errors or the the switchport from trying to reauthenticate? Below is the switchport config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;switchport access vlan 33&lt;/P&gt;&lt;P&gt;switchport mode access&lt;/P&gt;&lt;P&gt;switchport voice vlan 233&lt;/P&gt;&lt;P&gt;ip access-group ACL-DEFAULT in&lt;/P&gt;&lt;P&gt;authentication event fail retry 1 action next-method&lt;/P&gt;&lt;P&gt;authentication event server dead action authorize vlan 33&lt;/P&gt;&lt;P&gt;authentication event server alive action reinitialize&lt;/P&gt;&lt;P&gt;authentication host-mode multi-auth&lt;/P&gt;&lt;P&gt;authentication open&lt;/P&gt;&lt;P&gt;authentication order dot1x mab&lt;/P&gt;&lt;P&gt;authentication priority dot1x mab&lt;/P&gt;&lt;P&gt;authentication port-control auto&lt;/P&gt;&lt;P&gt;authentication timer reauthenticate server&lt;/P&gt;&lt;P&gt;authentication violation restrict&lt;/P&gt;&lt;P&gt;mab&lt;/P&gt;&lt;P&gt;dot1x pae authenticator&lt;/P&gt;&lt;P&gt;dot1x timeout tx-period 10&lt;/P&gt;&lt;P&gt;spanning-tree portfast&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 02:40:49 GMT</pubDate>
    <dc:creator>Nicholas Copeland</dc:creator>
    <dc:date>2019-03-11T02:40:49Z</dc:date>
    <item>
      <title>Authentication Open Failure</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054368#M152766</link>
      <description>&lt;P&gt;Is there away to stop the port from reauthenticating when a device fails to open. I am trying to set up low-impact mode on a wired network. And I have some WYSE terminals that I don't want to authenticate to the network so I would like them to fail open with an ACL limiting their access. However the switch continues to try and authenticate the device even after it has failed authentication. This is causing my logs on ISE to be full of bogus authentication failures. Is there a way to limit thoses errors or the the switchport from trying to reauthenticate? Below is the switchport config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;switchport access vlan 33&lt;/P&gt;&lt;P&gt;switchport mode access&lt;/P&gt;&lt;P&gt;switchport voice vlan 233&lt;/P&gt;&lt;P&gt;ip access-group ACL-DEFAULT in&lt;/P&gt;&lt;P&gt;authentication event fail retry 1 action next-method&lt;/P&gt;&lt;P&gt;authentication event server dead action authorize vlan 33&lt;/P&gt;&lt;P&gt;authentication event server alive action reinitialize&lt;/P&gt;&lt;P&gt;authentication host-mode multi-auth&lt;/P&gt;&lt;P&gt;authentication open&lt;/P&gt;&lt;P&gt;authentication order dot1x mab&lt;/P&gt;&lt;P&gt;authentication priority dot1x mab&lt;/P&gt;&lt;P&gt;authentication port-control auto&lt;/P&gt;&lt;P&gt;authentication timer reauthenticate server&lt;/P&gt;&lt;P&gt;authentication violation restrict&lt;/P&gt;&lt;P&gt;mab&lt;/P&gt;&lt;P&gt;dot1x pae authenticator&lt;/P&gt;&lt;P&gt;dot1x timeout tx-period 10&lt;/P&gt;&lt;P&gt;spanning-tree portfast&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:40:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054368#M152766</guid>
      <dc:creator>Nicholas Copeland</dc:creator>
      <dc:date>2019-03-11T02:40:49Z</dc:date>
    </item>
    <item>
      <title>Authentication Open Failure</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054369#M152767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nicolas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can configure a Restricted VLAN using the command "authentication event fail action authorize vlan (number)" and limit the access for that vlan using ACLs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can refer to &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_58_se/configuration/guide/sw8021x.html#wp1179086"&gt;http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_58_se/configuration/guide/sw8021x.html#wp1179086&lt;/A&gt;&lt;SPAN&gt; for more info.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kush&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Oct 2012 23:13:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054369#M152767</guid>
      <dc:creator>kussriva</dc:creator>
      <dc:date>2012-10-16T23:13:39Z</dc:date>
    </item>
    <item>
      <title>Authentication Open Failure</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054370#M152768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Perfect. I thought that would fail it from trying to do MAB. But it still runs through the order and then fails back to the VLAN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Oct 2012 13:51:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-open-failure/m-p/2054370#M152768</guid>
      <dc:creator>Nicholas Copeland</dc:creator>
      <dc:date>2012-10-17T13:51:44Z</dc:date>
    </item>
  </channel>
</rss>

