<?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 Profiling attributes are in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-probe-attribute-overlap/m-p/2674985#M55830</link>
    <description>&lt;P&gt;Profiling attributes are constantly collected and stored in the ISE database. One attributed is not preferred over the other. Instead, it is the profiling rules that decide how a device is profiled. More specifically, Profiling rules with higher Certainty Factor are preferred over the others. For instance, a device is profiled as a "Cisco Phone" with a CF=10. Later on, more attributes are collected, and now ISE has enough information to match a Profiling Rule for Cisco-IP-Phone-7945 with CF=30. As a result, the device will be profiled as a Cisco-IP-Phone-7945.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 04 May 2015 07:23:25 GMT</pubDate>
    <dc:creator>nspasov</dc:creator>
    <dc:date>2015-05-04T07:23:25Z</dc:date>
    <item>
      <title>ISE Probe attribute overlap</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-probe-attribute-overlap/m-p/2674984#M55828</link>
      <description>&lt;P&gt;I'm curious what is the logic in ISE 1.3 when more than one probe report different information for an endpoint. Say an endpoint with a MAC address got identified, and next it gets two different IP addresses for the same MAC from DHCP probe and maybe from SNMP CDP cache probe? Which one will it prefer? It appears that maybe it takes the last probe updated received regardless of the probe, is that correct?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:41:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-probe-attribute-overlap/m-p/2674984#M55828</guid>
      <dc:creator>trevorjenix</dc:creator>
      <dc:date>2019-03-11T05:41:50Z</dc:date>
    </item>
    <item>
      <title>Profiling attributes are</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-probe-attribute-overlap/m-p/2674985#M55830</link>
      <description>&lt;P&gt;Profiling attributes are constantly collected and stored in the ISE database. One attributed is not preferred over the other. Instead, it is the profiling rules that decide how a device is profiled. More specifically, Profiling rules with higher Certainty Factor are preferred over the others. For instance, a device is profiled as a "Cisco Phone" with a CF=10. Later on, more attributes are collected, and now ISE has enough information to match a Profiling Rule for Cisco-IP-Phone-7945 with CF=30. As a result, the device will be profiled as a Cisco-IP-Phone-7945.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2015 07:23:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-probe-attribute-overlap/m-p/2674985#M55830</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2015-05-04T07:23:25Z</dc:date>
    </item>
  </channel>
</rss>

