[Kea-users] migrating from DHCPd to Kea

[Peter Davies]

Hi Brendan,
    Logging is needed to troubleshoot in any meaningful way.
Regarding host reservations, there are no fast rules; it is intended to 
be as
flexible as possible. Having globals and subnet reservations is common.

The only thing we advise against is using global reservations to 
associate IP
addresses with clients; this may lead to clients receiving unusable leases.
Global reservations can be used to associate client classes etc..

Kind Regards Peter


On 17/04/2024 17.14, Brendan Kearney wrote:
> Peter,
>
> thanks for the insight.  it will take me a bit to get the env setup 
> for verbose logging, but will share the logs once they are generated.  
> regarding the reservations, are there best practices around global vs 
> subnet based reservations.  i have read 
> https://kea.readthedocs.io/en/kea-2.4.1/arm/dhcp4-srv.html#global-reservations-in-dhcpv4, 
> and understand why the capability for both exist, but are there 
> general "rules of the road" around this subject?  in cases where i 
> classify, but do not specify a reserved IP, i could see the global 
> reservation being appropriate.  in cases where a reserved IP is 
> assigned, what pros and cons are there around where the reservation is 
> defined?  in my case, i have <?include "/path/to/file.json?> call outs 
> for many of the config stanzas, to help organize the different 
> capabilities of Kea, and thats why i have all the reservations set 
> globally.  its based out of convenience and clarity, but doesnt mean 
> i'm right/wrong or following best practices.
>
> thanks for the help and effort,
>
> brendan
>
> On 4/17/24 5:49 AM, Peter Davies wrote:
>> Hi Brendan,
>>    It is not possible to see any details from this logging.
>>
>> You should check your haproxy configuration, Kea cannot continue 
>> processing
>> requests if it is unable to connect to the lease database.
>>
>> I suggest that you temporarily enable Severity DEBUG and debuglevel 
>> 99 so you
>> can see requests and how Kea is processing them.
>>
>>  As all your reservations are global, you should define
>>  "reservations-global": true,"
>>  the default is false.
>>
>>  All pools are guarded by client classes. The client may not be 
>> associated with
>>  any of these classes.
>>
>> /Peter
>>
>>
-- 
Peter Davies
Support Engineer
Internet Systems Corporation