<?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: Profiling with device-sensor and custom attributes in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/profiling-with-device-sensor-and-custom-attributes/m-p/5289991#M596294</link>
    <description>&lt;P&gt;It sends such TLV's. I even created a CUSTOMATTRIBUTE for profiling "cdp-tlv" contains CW916, but it does not seem to be matching as well&lt;/P&gt;&lt;TABLE border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;cdp-tlv&lt;/TD&gt;&lt;TD&gt;cdpCacheCapabilities=00:00:00:03&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;cdp-tlv&lt;/TD&gt;&lt;TD&gt;cdpCachePlatform=cisco CW9164I-ROW&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;lldp-tlv&lt;/TD&gt;&lt;TD&gt;lldpSystemCapabilitiesMap=00:04:00:04&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 12 May 2025 15:09:36 GMT</pubDate>
    <dc:creator>Doorahlek</dc:creator>
    <dc:date>2025-05-12T15:09:36Z</dc:date>
    <item>
      <title>Profiling with device-sensor and custom attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-with-device-sensor-and-custom-attributes/m-p/5289988#M596293</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to do NAC for AP's 916x series and 913x series. However on some occasions the AP does not get added to Internal Endpoints and even if I add it it does not match the profiling policy. In auth report I can see it sending RADIUS attributes like cdpCachePlatform = cisco CW9164-E, however ISE seems to be ignoring it at times.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Strange thing is also that these AP's match Cisco-Meraki-Device as a top profile because of OUI contains "Meraki" and sometimes Cisco-Router because of the OUI. I was thinking of adding the MAC OUI addresses to the top Cisco-Access-Point profile but it is just not scalable as same models have different OUI MAC's at times.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kindly checking for your help.&lt;/P&gt;&lt;P&gt;It will be very appreciated!&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 15:01:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-with-device-sensor-and-custom-attributes/m-p/5289988#M596293</guid>
      <dc:creator>Doorahlek</dc:creator>
      <dc:date>2025-05-12T15:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling with device-sensor and custom attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-with-device-sensor-and-custom-attributes/m-p/5289991#M596294</link>
      <description>&lt;P&gt;It sends such TLV's. I even created a CUSTOMATTRIBUTE for profiling "cdp-tlv" contains CW916, but it does not seem to be matching as well&lt;/P&gt;&lt;TABLE border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;cdp-tlv&lt;/TD&gt;&lt;TD&gt;cdpCacheCapabilities=00:00:00:03&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;cdp-tlv&lt;/TD&gt;&lt;TD&gt;cdpCachePlatform=cisco CW9164I-ROW&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;lldp-tlv&lt;/TD&gt;&lt;TD&gt;lldpSystemCapabilitiesMap=00:04:00:04&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 15:09:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-with-device-sensor-and-custom-attributes/m-p/5289991#M596294</guid>
      <dc:creator>Doorahlek</dc:creator>
      <dc:date>2025-05-12T15:09:36Z</dc:date>
    </item>
  </channel>
</rss>

