Failover + Static host definitions

[Richard L. Hamilton]

I have failover set up, and while I have a dynamic range, all known devices have static reservations configured.

Except for what has to be different between primary and secondary, the configuration files are the same; they both have the same host definitions.

Separating the configuration file into two parts: the main part with the primary or secondary information and pool definitions, which then includes on both an identical copy of  the file with the static host information, seems like it would simplify matters; you’d only be editing one file and copying it (and restarting both DHCP servers, presumably). Or you could script something really kewl with omshell to do both maybe, but if you make a mistake, you mess up both at the same time. At least if you’re editing a file, you can make sure the primary is behaving after restarting it before copying the edited file over to the secondary and restarting it too.

Putting the included file on a share that both can access would NOT be as good as it sounds, since that’s one more thing that has to be up in the right order, and could break.

> On Jul 14, 2022, at 10:51 AM, Ryan Shea <ryan at muppethouse.com> wrote:
> 
> Failover of a pool seems straightforward enough - however this is insufficient in the case where static reservations are present in host definitions. I am looking for some solution by which I have a redundant pair of dhcpd services which can not only fail over leases from a pool, but also keep those hosts with static reservations working.
> 
> Is this as simple as synchronizing the host config definitions and running both services - without any particular concern about which server replies? Manually managing host configs for reservations in two places seems sub-optimal.
> -- 
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users