Hi Jeff, You have the option specified in the subnet and class. I would just specify in the class. Remove the option from the subnet. I have no idea if your configuration is correct for your Cisco device, but it looks like a correct specification of vendor specific options (https://kea.readthedocs.io/en/kea-2.4.1/arm/dhcp4-srv.html#dhcpv4-vendor-specific-options). You can inspect what is being sent to the Cisco devices in the options using `tcpdump -w dhcp.pcap port 67` and then opening the resulting dhcp.pcap file with wireshark. It should contain only DHCP traffic.
Thank you, Darren Ankney On Wed, Aug 7, 2024 at 10:48 AM Jeff Obrizok <[email protected]> wrote: > > Hello, > > > > I am working on finalizing our DHCP migration to Kea and running into a > problem with some Cisco access points. Kea appears to be working when I > debug the logs of some of the access points, and then changing the IP I have > in Kea, and it is reflected as updated in the debug logs (I switched the > Controller IP to 1.1.1.1 and the debug logs showed the APs trying to connect > to 1.1.1.1). That being said, different APs that join did not get the > correct controller information and tried joining a legacy controller on the > network. I am hoping to gain some insight/assistance on my existing > configuration and what needs to be changed, or should be updated to work > correct. My configuration was pieces together from older posts I saw on here. > > In the global configuration I have the following…. > > "option-def": [ > > { "name": "cisco-wlc-servers", "code": 241, "space": > "vendor-encapsulated-options-space", "type": "ipv4-address", "array": true } > > ], > > > "client-classes": [ > > { > > "name": "Cisco_AP", > > "test": "substring(option[60].hex,0,8) == 'Cisco AP'", > > "option-data": [ > > { > > "name": "cisco-wlc-servers", > > "code": 241, > > "space": "vendor-encapsulated-options-space", > > "csv-format": true, > > "data": "172.20.1.10" > > }, > > { > > "name": "vendor-encapsulated-options" > > } > > ] > > > > In the SPECIFIC Subnet that the access points go in, I have the following… > > "option-data": [ > > ….. > > { "name": "cisco-wlc-servers", "space": > "vendor-encapsulated-options-space", "code": 241, "csv-format": true, "data": > "xx.xx.xx.xx" , "always-send": true } > > ] > > }, > > Is this the correct way to be handling Cisco WLC IP address being handed out > to APs? Is all of the Client-class definitions needed if I want this > information to be given via DHCP to any device that is connecting to that > specific subnet? > > > Thanks, > > Jeff > > > > -- > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/kea-users -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
