<?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 port-control force-unauthorized in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356709#M549495</link>
    <description>Yes you're right you can shutdown as well but it's a way to work. &lt;BR /&gt;I shutdown ports that are unused and leave unauthorized ports that will be on production later during the staging.&lt;BR /&gt;&lt;BR /&gt;I say to the customer to do a config on the interface and apply auto instead of no shutdown then I'm sure he won't unshut a port that needs to be shutted down</description>
    <pubDate>Wed, 28 Mar 2018 13:59:18 GMT</pubDate>
    <dc:creator>Francesco Molino</dc:creator>
    <dc:date>2018-03-28T13:59:18Z</dc:date>
    <item>
      <title>dot1x port-control force-unauthorized</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356316#M549476</link>
      <description>&lt;DIV class="lia-message-subject lia-component-message-view-widget-subject"&gt;
&lt;DIV class="MessageSubject"&gt;
&lt;DIV class="MessageSubjectIcons "&gt;
&lt;DIV class="lia-message-subject"&gt;
&lt;H5&gt;dot1x port-control force-unauthorized&lt;/H5&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="messageBodySimpleDisplay" class="lia-message-body lia-component-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;My understanding of the above command is the following -&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;force-unauthorized—causes the port to remain in the unauthorized state, ignoring all attempts by&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;&lt;STRONG&gt;&lt;EM&gt;the client to authenticate. The switch cannot provide authentication services to the client through the&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;&lt;STRONG&gt;&lt;EM&gt;port&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In what situation/s has anyone used the above command? Does this not essentially mean "nothing can use that port?"&amp;nbsp;&amp;nbsp;isn't that basically means I shut the port !!&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:52:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356316#M549476</guid>
      <dc:creator>HiTmAn47</dc:creator>
      <dc:date>2020-02-21T18:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x port-control force-unauthorized</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356324#M549481</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This means that this port is not shutdown but doesn't allow anyone to connect to it, your right.&lt;/P&gt;
&lt;P&gt;Usually, you will use auto to put the port in unauthorized and as soon as someone is connected to and authenticated, it will switch to authorized.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Personally, i use this command when I'm&amp;nbsp;staging your switch and don't want anyone to initiate any authentication process.&lt;/P&gt;
&lt;P&gt;Let's take an example: you're deploying a new switch on a remote site and you don't want anybody to authenticate while you finish your config to not generate any logs and bring pushed into quarantine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is that clear?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 04:13:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356324#M549481</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-03-28T04:13:16Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x port-control force-unauthorized</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356339#M549486</link>
      <description>In short this port won't be authorized and can't get DACL or VLAN vsa or&lt;BR /&gt;any other attribute from ISE. You can replace it with an ACL and restricted&lt;BR /&gt;ACEs or MAC security but I think you can use it if you want unified&lt;BR /&gt;environment where everything controlled from one place&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Mar 2018 04:46:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356339#M549486</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2018-03-28T04:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x port-control force-unauthorized</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356521#M549491</link>
      <description>Thanks alot , it makes sense now ....so this feature blocks anyone from connecting to the port without shutting it down .....But Still in your example I would have just shutdown every port instead of going through the hassle of applying this command on each port</description>
      <pubDate>Wed, 28 Mar 2018 10:16:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356521#M549491</guid>
      <dc:creator>HiTmAn47</dc:creator>
      <dc:date>2018-03-28T10:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: dot1x port-control force-unauthorized</title>
      <link>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356709#M549495</link>
      <description>Yes you're right you can shutdown as well but it's a way to work. &lt;BR /&gt;I shutdown ports that are unused and leave unauthorized ports that will be on production later during the staging.&lt;BR /&gt;&lt;BR /&gt;I say to the customer to do a config on the interface and apply auto instead of no shutdown then I'm sure he won't unshut a port that needs to be shutted down</description>
      <pubDate>Wed, 28 Mar 2018 13:59:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot1x-port-control-force-unauthorized/m-p/3356709#M549495</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-03-28T13:59:18Z</dc:date>
    </item>
  </channel>
</rss>

