Hi Benedikt,
I’m not really getting your idea of what you want to achieve, but let me
provide you another possibility. Instead of running an active-backup KEA
cluster run 2 kea servers with a common (and redundant) backend (mysql, pgsql,
cassandra) and on the dhcp-relays (I assume you’ve one since you’re building
something bigger) add both servers.
When a client’s request hits the relay the packet is relayed to the first KEA
(or both), if there is no response, then to the second. Anyway one of them will
respond.
Other possibility is to have one HA IP (VIP IP, VRRP IP) on the KEA cluster.
Hope this helps somehow.
Cheers,
Tom
From: Kea-users [mailto:[email protected]] On Behalf Of Oehlrich,
Benedikt
Sent: Tuesday, January 14, 2020 7:45 AM
To: [email protected]
Subject: [Kea-users] get backup server into ready state
Hey everyone,
I'm setting up a ha cluster and wonder if there is a way to get a server, that
is configured as a backup server, to transit into a ready state.
E.g. I have a monitoring instance that realizes that one of my kea instances
fails and does not respond any more. Of course the service stays available as
the second running kea instance takes over. But if my second instance would
fail, there would be no working DHCP service available anymore.
I now want this monitoring service to automatically enable the backup server to
take the place of the failed kea instance.
Can this be achieved without updating the config file just by using the REST
backend?
It's not really documented what the backup server is for, besides to have a
lease backup which can be turned on manually.
Cheers,
Benedikt
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
