<?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: ip device tracking and ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3817893#M484419</link>
    <description>&lt;P&gt;Also, I am using the 802.1x feature on the switch, and one of the authentication / authorization commands may be changing the switch configuration mode. I think it's my fault. Thanks for the explanations.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 09:13:57 GMT</pubDate>
    <dc:creator>Sp@wn</dc:creator>
    <dc:date>2019-03-12T09:13:57Z</dc:date>
    <item>
      <title>ip device tracking and ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3816376#M484411</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the importance of ip device tracking for CISCO ISE?&amp;nbsp;Because in the cisco switch version 16.6.x and later, the ip device tracking is forcing the authentication mode to switch from the legacy mode to new-style (C3PL)configuration mode.&amp;nbsp;Can we do ISE configuration without using ip device tracking on the switch?&amp;nbsp;If we have to use ip device tracking, is there any confirmed C3PL ISE configuration for 3650-3850 switches?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Sp@wn&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 15:52:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3816376#M484411</guid>
      <dc:creator>Sp@wn</dc:creator>
      <dc:date>2019-03-08T15:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: ip device tracking and ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3816668#M484412</link>
      <description>&lt;P&gt;Hi , that is not true. I have 3650 version 16.6.7 and i apply device tracking. There is a little difference. With this switches they comming with default device-tracking policy. I modified it a little . Conf t , device-tracking policy ISE , and ypu can config like ypu want . And attach it to the port . Interface gi 1/1/1&amp;nbsp;&lt;/P&gt;&lt;P&gt;device-tracking policy Ise&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 04:45:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3816668#M484412</guid>
      <dc:creator>ognyan.totev</dc:creator>
      <dc:date>2019-03-09T04:45:29Z</dc:date>
    </item>
    <item>
      <title>Re: ip device tracking and ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3816693#M484416</link>
      <description>I agree with ognyan here, while it's policy based IPDT, you can still use IBNS 1.0 configs with it.  I have done just that many times on 16.6.x, old style IBNS 1 config with a new IPDT policy.  What I don't like is that when we upgrade from 3.x, we have to manually do this.  &lt;BR /&gt;&lt;BR /&gt;Now you might use &lt;BR /&gt;!&lt;BR /&gt;device-tracking policy DOT1X_INTERFACE&lt;BR /&gt;security-level glean&lt;BR /&gt;no protocol ndp&lt;BR /&gt;no protocol udp&lt;BR /&gt;tracking enable reachable-lifetime 10&lt;BR /&gt;!&lt;BR /&gt;int x/x/x&lt;BR /&gt;device-tracking attach-policy DOT1X_INTERFACE&lt;BR /&gt;</description>
      <pubDate>Sat, 09 Mar 2019 08:33:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3816693#M484416</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-03-09T08:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: ip device tracking and ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3817893#M484419</link>
      <description>&lt;P&gt;Also, I am using the 802.1x feature on the switch, and one of the authentication / authorization commands may be changing the switch configuration mode. I think it's my fault. Thanks for the explanations.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 09:13:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ip-device-tracking-and-ise/m-p/3817893#M484419</guid>
      <dc:creator>Sp@wn</dc:creator>
      <dc:date>2019-03-12T09:13:57Z</dc:date>
    </item>
  </channel>
</rss>

