<?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: ISE device information for non-auth interfaces in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765892#M486917</link>
    <description>&lt;P&gt;As far as I know at least MAB is required. Use monitor mode or return Permit from ISE unconditionally to avoid connectivity issues. Without an authentication request (a session) the endpoint is not added to ISE endpoint database.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Dec 2018 15:05:15 GMT</pubDate>
    <dc:creator>Peter Koltl</dc:creator>
    <dc:date>2018-12-18T15:05:15Z</dc:date>
    <item>
      <title>ISE device information for non-auth interfaces</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765719#M486909</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we're currently migrating from ACS 5.8 to ISE 2.2 and I was wondering, if it is possible to profile the devices that are not authenticated on a switch interface/ISE. Our authentication is vlan-based without dACL or SGT.&lt;/P&gt;&lt;P&gt;Or if there is a better way to authenticate devices that can't auth with dot1x and need to have network access on startup (except changing the auth-order from dot1x mab to mab dot1x). Sometimes some of the devices won't show their mac-address for some reason, thus authentication won't work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The first interface is our default switchport configuration and the second interface configuration is when the interface needs to be locked in a vlan for a device.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/0/3&lt;BR /&gt;&amp;nbsp;description dot1x&lt;BR /&gt;&amp;nbsp;switchport access vlan 54&lt;BR /&gt;&amp;nbsp;switchport mode access&lt;BR /&gt;&amp;nbsp;switchport voice vlan 121&lt;BR /&gt;&amp;nbsp;authentication control-direction in&lt;BR /&gt;&amp;nbsp;authentication event server dead action authorize vlan 55&lt;BR /&gt;&amp;nbsp;authentication event server dead action authorize voice&lt;BR /&gt;&amp;nbsp;authentication event server alive action reinitialize&lt;BR /&gt;&amp;nbsp;authentication host-mode multi-domain&lt;BR /&gt;&amp;nbsp;authentication order dot1x mab&lt;BR /&gt;&amp;nbsp;authentication priority dot1x mab&lt;BR /&gt;&amp;nbsp;authentication port-control auto&lt;BR /&gt;&amp;nbsp;authentication violation restrict&lt;BR /&gt;&amp;nbsp;mab&lt;BR /&gt;&amp;nbsp;dot1x pae authenticator&lt;BR /&gt;&amp;nbsp;dot1x timeout tx-period 7&lt;BR /&gt;&amp;nbsp;spanning-tree portfast&lt;BR /&gt;&amp;nbsp;spanning-tree bpduguard enable&lt;BR /&gt;&amp;nbsp;spanning-tree guard root&lt;BR /&gt;end&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/0/4&lt;BR /&gt;&amp;nbsp;description SALTO Liz-Serv&lt;BR /&gt;&amp;nbsp;switchport access vlan 111&lt;BR /&gt;&amp;nbsp;switchport mode access&lt;BR /&gt;&amp;nbsp;switchport port-security mac-address sticky&lt;BR /&gt;&amp;nbsp;switchport port-security mac-address sticky xxxx.xxxx.xxxx&lt;BR /&gt;&amp;nbsp;switchport port-security&lt;BR /&gt;end&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 11:45:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765719#M486909</guid>
      <dc:creator>Maxee</dc:creator>
      <dc:date>2018-12-18T11:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISE device information for non-auth interfaces</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765892#M486917</link>
      <description>&lt;P&gt;As far as I know at least MAB is required. Use monitor mode or return Permit from ISE unconditionally to avoid connectivity issues. Without an authentication request (a session) the endpoint is not added to ISE endpoint database.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 15:05:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765892#M486917</guid>
      <dc:creator>Peter Koltl</dc:creator>
      <dc:date>2018-12-18T15:05:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE device information for non-auth interfaces</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765921#M486935</link>
      <description>&lt;P&gt;MAB is the only method to authenticate devices that do not have a supplicant.&amp;nbsp; You can still profile devices so long as the MAC address of the endpoint is obtained.&amp;nbsp; There are a few ways to obtain the MAC address of the endpoint:&amp;nbsp; DHCP, SNMP polling, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;-Tim&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 15:27:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-device-information-for-non-auth-interfaces/m-p/3765921#M486935</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2018-12-18T15:27:56Z</dc:date>
    </item>
  </channel>
</rss>

