I am the using the following device sensor configuration on the catalyst 3850 and 4500 models:
device-sensor filter-list sip list sip_profiling
tlv name device-name
tlv name device-version
tlv name device-vendor
!
device-sensor filter-list dhcp list dhcp_profiling
option name host-name
option name default-ip-ttl
option name requested-address
option name parameter-request-list
option name class-identifier
option name client-identifier
!
device-sensor filter-list lldp list lldp_profiling
tlv name system-name
tlv name system-description
!
device-sensor filter-list cdp list cdp_profiling
tlv name device-name
tlv name address-type
tlv name capabilities-type
tlv name platform-type
device-sensor filter-spec sip include list sip_profiling
device-sensor filter-spec dhcp include list dhcp_profiling
device-sensor filter-spec lldp include list lldp_profiling
device-sensor filter-spec cdp include list cdp_profiling
device-sensor accounting
device-sensor notify all-changes
I am trying to profile a Cisco IP Phone 7841. The switchport is configured with a voice vlan and cdp is enabled. ISE is configured with a wired MAB policy that uses an endpoint groups for voip phones AND cisco-ip-phone profiling to assign the ip phone to a voice vlan. When I had the following probes enabled on the PSNs - radius, dhcp, http, snmpquery, and snmptrap - the ip phone was correctly profiled and immediately assigned to the voice vlan. When I configured the PSNs to only use radius for profiling, it took the phone a very long time to correctly profile and sometimes not they didn't authorize at all. I figured out the issue was profiling. My question is....even though device sensors are configured on the switch and passed to ISE via Radius, do I need to have the DHCP and Radius probes enabled to properly profile an IP phone?
