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
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
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
Peter,
thanks for the quick reply. please let me know if there is more detail
needed. i run Kea with ERROR level logging, so if more verbose logs are
needed, i would need to set up some time to test and collect the logs, etc.
the logs from the testing i did, as collected by my syslog
Hi Brendan,
Kea will not be able to grant leases if it cannot contact its lease
database.
Your configuration file and logging would be helpful.
Also, setting the "authoritative" to true will force Kea to always
reject INIT-REBOOT requests from unknown clients
/Peter
On 16/04/2024 18.16,
list members,
i am trying to migrate to Kea and have 2 HA+MT instances stood up. when
i start relaying dhcp requests to Kea, i get bunch of failed attempts to
obtain leases on the clients, which i believe is due to the clients not
having active leases from Kea. i am wondering if there is a
