Handling external changes with Kea - User Guide - BlueCat Horizon

DDI orchestrator uses the in-memory configuration of the Kea server. If changes must be made to a Kea DHCP server’s configuration file outside of DDI orchestrator, the changes to the configuration file will not be processed by the server until it's forced to parse the file to its in-memory structure, so that DDI orchestrator can be made aware of these changes.

If the server is the primary server in a High Availability setup, all changes made to the configuration file through DDI orchestrator will be automatically and instantly propagated to the secondary servers in the failover relationship.

However, if you make changes to the Kea DHCP server's configuration outside of DDI orchestrator, a call must be made to the DHCP Agent, Kea Control Agent (if applicable), or the socket that Kea uses in order to force the server to process those changes.

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

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 view them in DDI orchestrator.