<?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: Authorization Pending in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943535#M456344</link>
    <description>Hi Damien,&lt;BR /&gt;&lt;BR /&gt;What would you suggest for a NAC solution using NX-OS 9Ks as access switches and ISE as a radius server?</description>
    <pubDate>Fri, 18 Oct 2019 19:25:21 GMT</pubDate>
    <dc:creator>s1nsp4wn</dc:creator>
    <dc:date>2019-10-18T19:25:21Z</dc:date>
    <item>
      <title>Authorization Pending</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943481#M456342</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm running ISE 2.4 and I'm trying to get NAC via dot1x/radius working.&amp;nbsp; I have a NX-OS 9K switch in my network devices with correct radius key.&amp;nbsp; I also have a default policy set to accept dotx wired users and allow them to do anything.&amp;nbsp; On the switch I have aaa setup to use ISE as a radius server and I've confirmed reachability.&amp;nbsp; I've also enabled dot1x on a test port I have a laptop connected to.&amp;nbsp; When I connect I get 'authorization pending' and see nothing else in show dot1x all or show radius.&amp;nbsp; &amp;nbsp;I see nothing in ISE's radius logs so I assume I'm not even talking to it.&amp;nbsp; What else can I check?&amp;nbsp; I followed directions below:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x_chapter_0100.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/security/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x_chapter_0100.html" target="_blank" rel="noopener"&gt;OS_Security_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Security_Configuration_Guide_7x_chapter_0100.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Switch configs:&lt;/P&gt;&lt;P&gt;feature dot1x&lt;BR /&gt;radius-server host 1.3.5.7 key 7 "x" authentication accounting timeout 5 retransmit 3&lt;BR /&gt;radius-server host 2.4.6.8 key 7 "x" authentication accounting timeout 5 retransmit 3&lt;BR /&gt;aaa group server radius MuhISE&lt;BR /&gt;server 1.3.5.7&lt;BR /&gt;server 2.4.6.8&lt;BR /&gt;source-interface mgmt0&lt;BR /&gt;!&lt;BR /&gt;dot1x radius-accounting&lt;BR /&gt;dot1x radius-accounting&lt;BR /&gt;dot1x system-auth-control&lt;BR /&gt;!&lt;BR /&gt;ip access-list ALLOW-ALL&lt;BR /&gt;10 permit ip any any&lt;BR /&gt;!&lt;BR /&gt;aaa authentication dot1x default group MuhISE&lt;BR /&gt;aaa accounting dot1x default group MuhISE&lt;BR /&gt;aaa authentication login error-enable&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet1/1&lt;BR /&gt;ip access-group ALLOW-ALL in&lt;BR /&gt;switchport&lt;BR /&gt;dot1x pae authenticator&lt;BR /&gt;dot1x port-control auto&lt;BR /&gt;dot1x re-authentication&lt;BR /&gt;dot1x timeout tx-period 10&lt;BR /&gt;switchport access vlan 666&lt;BR /&gt;spanning-tree port type edge&lt;BR /&gt;spanning-tree bpduguard enable&lt;BR /&gt;mtu 9216&lt;BR /&gt;no shutdown&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ISE Configs:&lt;/P&gt;&lt;P&gt;network devices - nexus switch above added using mgmt0 interface in vrf&lt;/P&gt;&lt;P&gt;policy (radius = 802.1x)&lt;/P&gt;&lt;P&gt;authentication (wired mab and default both look in all stores0&lt;/P&gt;&lt;P&gt;authorization (wired mab and default both allow all)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2019 18:41:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943481#M456342</guid>
      <dc:creator>s1nsp4wn</dc:creator>
      <dc:date>2019-10-18T18:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Pending</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943532#M456343</link>
      <description>This is not something I have gone down the path of configuring, I have only leveraged ISE with TrustSec functionality on Nexus. Maybe others will have direct 802.1x/Nexus experience. &lt;BR /&gt;&lt;BR /&gt;However, I wanted to add that you're entering very rare territory trying to use access layer 802.1x features on Nexus.  I understand that there is a Nexus 802.1x configuration section within the command guide, but Nexus isn't even listed within the Cisco validated ISE compatibility matrix. This would leave me questioning how well things have been tested before even starting.  &lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/compatibility/b_ise_sdt_24.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/compatibility/b_ise_sdt_24.html&lt;/A&gt;</description>
      <pubDate>Fri, 18 Oct 2019 19:23:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943532#M456343</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-10-18T19:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Pending</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943535#M456344</link>
      <description>Hi Damien,&lt;BR /&gt;&lt;BR /&gt;What would you suggest for a NAC solution using NX-OS 9Ks as access switches and ISE as a radius server?</description>
      <pubDate>Fri, 18 Oct 2019 19:25:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3943535#M456344</guid>
      <dc:creator>s1nsp4wn</dc:creator>
      <dc:date>2019-10-18T19:25:21Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization Pending</title>
      <link>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3944447#M456345</link>
      <description>ISE is the NAC solution, nothing else to propose. these aren't access switches..</description>
      <pubDate>Mon, 21 Oct 2019 10:42:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authorization-pending/m-p/3944447#M456345</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-10-21T10:42:41Z</dc:date>
    </item>
  </channel>
</rss>

