Profiling with device-sensor and custom attributes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 08:01 AM
Hello,
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.
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.
Kindly checking for your help.
It will be very appreciated!
- Labels:
-
Identity Services Engine (ISE)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2025 08:08 AM - edited 05-12-2025 08:09 AM
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
cdp-tlv | cdpCacheCapabilities=00:00:00:03 |
cdp-tlv | cdpCachePlatform=cisco CW9164I-ROW |
lldp-tlv | lldpSystemCapabilitiesMap=00:04:00:04 |
