Carsten
The following chapter:
https://kea.readthedocs.io/en/kea-3.0.0/arm/hooks.html#controlled-shutdown-and-maintenance-of-dhcp-servers
explains that:
"If the server has many relationships with different partners, the
ha-maintenance-start command attempts to transition all of the
relationships into the partner-in-maintenance state by sending
ha-maintenance-notify to all partner servers. If this step fails for any
server, an error is returned. If that happens, the ha-maintenance-cancel
command can be used to resume normal operations and fix the issue."
Marcin Siodelski
ISC
On 9.07.2025 17:20, Carsten Strotmann via Kea-users wrote:
Hi,
the API command "ha-maintenance-start" will set the partner DHCP server into
maintenance state.
So the command is usually being send to the machine that should "take over" the
whole DHCP service.
How does this work in an hub-and-spoke configuration.
When an "ha-maintenance-start" command is send (via the kea-ctrl-agent) to the central "hub"
machine, holding many different HA-relationships with "spoke" DHCP servers, will it set all "spoke"
DHCP servers into maintenance?
If yes, will it be possible to just set one HA-relationship into maintenance
mode?
Greetings
Carsten
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users