<?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 IBNS 2.0 Intelligent Aging /w SISF based device-tracking Cat9k 16.x in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-intelligent-aging-w-sisf-based-device-tracking-cat9k-16/m-p/4716597#M578069</link>
    <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Problem description&lt;/STRONG&gt;: Indirectly connected devices (e.g. PCs daisy-chained via. Phones) do not age out in an ISE + 802.1x (Monitor Mode) on Catalyst 3850/9300 switches environment. Configuration to fix this (subscriber aging) has changed between 3.x and 16.x code.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The current issue I'm facing is that the IPDT-based Device Tracking infrastructure has changed between IOS XE 3.x and 16.x yet the documentation is not clear about how this impacts the Intelligent Aging "probe" functionality in IBNS 2.0 (i.e. The command “subscriber aging inactivity-timer 60 &lt;STRONG&gt;probe&lt;/STRONG&gt;”)&lt;/P&gt;&lt;P&gt;The original behavior of this command was when applied to a dot1X template it would age out STATIC MAC entries of clients, with the addition of the "probe" keyword it would ARP probe a device at around the 50-55 second mark before then declaring the host “state/dead” and removing its STATIC MAC address entry in the CAM table. This would ensure that if a host was “silent” during that time its dot1x session wouldn’t be prematurely cleared. I'm aware that in 16.x code and beyond that the Device tracking infrastructure has been changed from IPDT (old) =&amp;gt; SISF (new) based tracking, but I cannot seem to get the same behavior for intelligent aging even though the commands still exist in the CLI parser.&lt;/P&gt;&lt;P&gt;Does anyone know how to get the “probe” behavior previously seen in 3.6.x code “subscriber aging inactivity-timer 60 probe” where the ARP probe Is sent from the access switch before evicting the dot1x session? This eviction appears to have been based on “traffic” through the session and was verified by an ARP probe to see if the host was really “alive”. Now, I need to modify the SISF policy and set something like “device-tracking binding reachable-lifetime 50” which results in the switch having to constantly ARP probe because SISF device tracking only checks for the presence of ARP, DHCPv4 packets and not generic session traffic.&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@&lt;BR /&gt;&lt;/FONT&gt;&lt;FONT face="courier new,courier"&gt;+ Configuration snippets of what we’re running (Manually enabling device tracking with a custom Policy)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;device-tracking policy dot1x&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no protocol udp&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;tracking enable&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;vlan configuration 27&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;device-tracking attach-policy dot1x&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;+ dot1X configuration to enable the aging + ARP probe&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;subscriber aging inactivity-timer 60 probe&lt;BR /&gt;@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Not sure if there is something easy I'm missing. But long story short I'd just like to achieve the same functionality as 3.6.x (Intelligent Aging /w Silent host detection in &amp;gt;= 16.x code)&lt;/P&gt;&lt;P&gt;Any assistance would be appreciated.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Jason.&lt;/P&gt;</description>
    <pubDate>Sun, 06 Nov 2022 00:31:53 GMT</pubDate>
    <dc:creator>JasonLeschnik</dc:creator>
    <dc:date>2022-11-06T00:31:53Z</dc:date>
    <item>
      <title>IBNS 2.0 Intelligent Aging /w SISF based device-tracking Cat9k 16.x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-intelligent-aging-w-sisf-based-device-tracking-cat9k-16/m-p/4716597#M578069</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Problem description&lt;/STRONG&gt;: Indirectly connected devices (e.g. PCs daisy-chained via. Phones) do not age out in an ISE + 802.1x (Monitor Mode) on Catalyst 3850/9300 switches environment. Configuration to fix this (subscriber aging) has changed between 3.x and 16.x code.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The current issue I'm facing is that the IPDT-based Device Tracking infrastructure has changed between IOS XE 3.x and 16.x yet the documentation is not clear about how this impacts the Intelligent Aging "probe" functionality in IBNS 2.0 (i.e. The command “subscriber aging inactivity-timer 60 &lt;STRONG&gt;probe&lt;/STRONG&gt;”)&lt;/P&gt;&lt;P&gt;The original behavior of this command was when applied to a dot1X template it would age out STATIC MAC entries of clients, with the addition of the "probe" keyword it would ARP probe a device at around the 50-55 second mark before then declaring the host “state/dead” and removing its STATIC MAC address entry in the CAM table. This would ensure that if a host was “silent” during that time its dot1x session wouldn’t be prematurely cleared. I'm aware that in 16.x code and beyond that the Device tracking infrastructure has been changed from IPDT (old) =&amp;gt; SISF (new) based tracking, but I cannot seem to get the same behavior for intelligent aging even though the commands still exist in the CLI parser.&lt;/P&gt;&lt;P&gt;Does anyone know how to get the “probe” behavior previously seen in 3.6.x code “subscriber aging inactivity-timer 60 probe” where the ARP probe Is sent from the access switch before evicting the dot1x session? This eviction appears to have been based on “traffic” through the session and was verified by an ARP probe to see if the host was really “alive”. Now, I need to modify the SISF policy and set something like “device-tracking binding reachable-lifetime 50” which results in the switch having to constantly ARP probe because SISF device tracking only checks for the presence of ARP, DHCPv4 packets and not generic session traffic.&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@&lt;BR /&gt;&lt;/FONT&gt;&lt;FONT face="courier new,courier"&gt;+ Configuration snippets of what we’re running (Manually enabling device tracking with a custom Policy)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;device-tracking policy dot1x&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no protocol udp&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;tracking enable&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;vlan configuration 27&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;device-tracking attach-policy dot1x&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;+ dot1X configuration to enable the aging + ARP probe&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;subscriber aging inactivity-timer 60 probe&lt;BR /&gt;@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Not sure if there is something easy I'm missing. But long story short I'd just like to achieve the same functionality as 3.6.x (Intelligent Aging /w Silent host detection in &amp;gt;= 16.x code)&lt;/P&gt;&lt;P&gt;Any assistance would be appreciated.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Jason.&lt;/P&gt;</description>
      <pubDate>Sun, 06 Nov 2022 00:31:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-intelligent-aging-w-sisf-based-device-tracking-cat9k-16/m-p/4716597#M578069</guid>
      <dc:creator>JasonLeschnik</dc:creator>
      <dc:date>2022-11-06T00:31:53Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 Intelligent Aging /w SISF based device-tracking Cat9k 16.</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-intelligent-aging-w-sisf-based-device-tracking-cat9k-16/m-p/4716788#M578079</link>
      <description>&lt;P&gt;(Same person, Different CCO account).&lt;/P&gt;&lt;P&gt;So I think I might have figured it out, it seems to be a combination of the following configuration. I'm going to follow up with Cisco TAC to determine if this is correct. I cannot find any documentation that explains this &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Global Configuration:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ip dhcp snooping&lt;/LI&gt;&lt;LI&gt;ip dhcp snooping vlan x&lt;/LI&gt;&lt;LI&gt;device-tracking binding reachable-lifetime 60&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;&amp;nbsp;Interface configuration:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;subscriber aging inactivity-timer 60 probe&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 07 Nov 2022 03:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-intelligent-aging-w-sisf-based-device-tracking-cat9k-16/m-p/4716788#M578079</guid>
      <dc:creator>jl</dc:creator>
      <dc:date>2022-11-07T03:00:36Z</dc:date>
    </item>
  </channel>
</rss>

