For ISC Kea DHCP services, an agent handles standalone DHCPv4 or DHCPv6 services without the need for the Kea Control Agent. Micetro first attempts to connect using the agent. If it detects that communication is being handled through a Control Agent, it uses that instead.
We recommend upgrading to Kea 3.0 without the Control Agent and using that setup going forward.
Managing Kea DHCP without the Kea Control Agent
In Micetro, an agent handles a standalone Kea DHCP service. This means that one agent handles DHCPv4 and a different agent handles DHCPv6. This agent does not need to communicate through the Kea Control Agent, as was required previously.
Ports
The default port for a Kea service is 8000. However, if two services
are running on the same host but have different port numbers, you can specify the
port number when Adding a Kea DHCP server to Micetro.
Using the Kea Control Agent
For Kea DHCP servers v2.7.2 and earlier, the Kea Control Agent serves as a crucial component, operating as a daemon that provides a RESTful control interface for the seamless management of Kea servers. This agent can receive control commands via HTTP and can either forward them to the respective Kea servers or execute them on its own.
Using the Kea Control Agent, you can add Kea DHCP servers to Micetro without a DHCP agent running on every machine hosting Kea. One DHCP agent, installed on a machine with access to the Kea service instances, is sufficient and will communicate with all Kea servers on behalf of Micetro.
Ports
The default port for the Kea Control Agent is 8000.