Handling external changes with Kea - User Guide - Micetro - 25.2.0

Micetro uses the in-memory configuration of the Kea server. If external changes must be made to a Kea DHCP server’s configuration file, the changes to the configuration file aren’t processed by the server until forced to parse the file to its in-memory structure, so Micetro can be made aware of these changes.

To make the Kea DHCP server process changes to its configuration file, a call has to be made to either the Kea Control Agent or the socket that Kea uses.

Here's an example of the call to the Control Agentt:

curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-reload", "service": [ "dhcp4" ] }' localhost:8000

If successful, the result looks like this:

[{"result":0,"text":"Configuration successful."}]

After the changes to the configuration file have been accepted and parsed into the Kea DHCP server's memory structure, you can use the Edit configuration action to display them in Micetro.