I was looking into Radius profiling on the WLAN controller. I would like to make the recommendation that DHCP should not have to be required in order to do profiling. I understand that DHCP is required to actually profile. However, it would not be necessary to profile a device with a static IP address.
Here is some additional logic:
If a device that is allowed on the network has a static IP address, that would be ok.
If a device that should not be allowed on the network is trying to get on the network with a static IP address, it should still be blocked by ISE.
Is there any reason for this requirement that is not obvious which would make it 100% necessary?
Both the DHCP and DHCP SPAN probes deliver the same key profiling attributes to ISE. These include some of the following:
dhcp-message-type (Option 53)
mud-url (Option 161)
dhcpv6-user-class (Option 15)
dhcpv6-vendor-class (Option 16)
dhcpv6-vendor-opts (Option 17)
dhcpv6-mud-url (Option 112)
Since DHCP provides both a MAC address (dhcp-client-identifier) and an IP address (dhcp-requested-address), it is also capable of establishing IP-to-MAC address bindings for the ISE ARP cache table. This is useful in supporting other probes that rely on IP address rather than MAC address. To apply and save the attributes they provide about a specific endpoint into the ISE database, the IP address needs to be correlated to a specific endpoint based on its MAC address.
In addition todhcp-client-identifieranddhcp-requested-address, other key attributes includedhcp-class-identifier,dhcp-user-class-id, anddhcp-parameters-request-list. The class identifier is often used to convey platform or OS information. Class identifier as well as User Class ID may be customized on some client operating systems like Mac OS and Microsoft Windows, respectively, to be used as unique corporate identifiers for profiling or to return unique scope values by the DHCP server.
Thedhcp-parameters-request-listoffers a potentially unique indicator of the device type since the values and sequence of parameters requested are often unique to a limited set of device types or operating systems. For example, adhcp-parameters-request-listvalue of 1, 3, 6, 15, 119, 252 is indicative of an Apple iOS device such as an iPad, iPod, or iPhone.
It’s been about two and half years, since the launch of next generation Cisco Catalyst 9800 Wireless LAN Controllers that has the most deployment flexibility and runs the modular, scalable, highly reliable, open and programmable operating system, I...
Hi All, I have made this video for Cisco Pitch the Future Contest in Malaysia which talks about Wi-Fi 6 and EWC Demo. Please feel free to view the video below and please support me for this contest by giving the video a like as the Contest will end o...
On the Cisco Catalyst 9800 Series WLC, enabling/disabling the remote LAN (RLAN) ports on APs requires going into the configuration for each AP and manually enabling/disabling the ports. However, as the number of APs that need to have their RLAN...
It’s been a long road for our AireOS wireless controllers. In fact these products have been around Cisco in some form since 2005. As you may have heard, Cisco made the decision to End-of-Sale (EOS) these products last month.
That means that these AireOS ...