<?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: 802.1x authentication when CiscoSecure is down in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344875#M430036</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In your AAA command, do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; aaa authentication dot1x default group radius &lt;B&gt;none&lt;/B&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The none keyword is a backup authentication method in case the Radius authentication fails (because the server is unavailable, not because of an incorrect username/password), and the switch should authenticate the user automatically.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Jan 2005 22:23:55 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2005-01-04T22:23:55Z</dc:date>
    <item>
      <title>802.1x authentication when CiscoSecure is down</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344874#M430035</link>
      <description>&lt;P&gt;I'm setting up Switch Port Authentication on my Catalysts using the CiscoSecure appliance and the Windows Active Directory user database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Everything works fine on the lab, but I need a way to enable all ports on the switches when the CiscoSecure is down (no communication from the switch to the CiscoSecure). This way, I could give network access to the users in case my CiscoSecure server goes down. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestion? &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 20:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344874#M430035</guid>
      <dc:creator>jalcala</dc:creator>
      <dc:date>2019-03-10T20:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x authentication when CiscoSecure is down</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344875#M430036</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In your AAA command, do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; aaa authentication dot1x default group radius &lt;B&gt;none&lt;/B&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The none keyword is a backup authentication method in case the Radius authentication fails (because the server is unavailable, not because of an incorrect username/password), and the switch should authenticate the user automatically.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Jan 2005 22:23:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344875#M430036</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2005-01-04T22:23:55Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x authentication when CiscoSecure is down</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344876#M430037</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did as suggested (add the "none" keyword to the aaa configuration) but it's still not working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "none" keyword works well with my Tacacs configuration for line access control to the switches and routers, but applied to the Radius configuration as suggested it seems to do nothing (if the ACS is not on the network, the switch ports remains disabled).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jan 2005 18:14:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344876#M430037</guid>
      <dc:creator>jalcala</dc:creator>
      <dc:date>2005-01-05T18:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x authentication when CiscoSecure is down</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344877#M430038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My apologies, I've been reliably informed that using the "none" keyword on the dot1x auth method does not at this time work.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this time there is no workaround for when the Radius server is unavailable.  Your best bet is to set up a backup Radius server, implement DB Replication between the two to sync up their configs, and configure the backup Radius server on your switches.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jan 2005 05:15:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344877#M430038</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2005-01-11T05:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x authentication when CiscoSecure is down</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344878#M430039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot. I guess we'll need to setup a backup serer.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jan 2005 11:52:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-when-ciscosecure-is-down/m-p/344878#M430039</guid>
      <dc:creator>jalcala</dc:creator>
      <dc:date>2005-01-11T11:52:09Z</dc:date>
    </item>
  </channel>
</rss>

