Send dhcp-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Failover + Static host definitions (Ryan Shea)
2. Re: Failover + Static host definitions (Richard L. Hamilton)
3. Re: Failover + Static host definitions (Glenn Satchell)
----------------------------------------------------------------------
Message: 1
Date: Thu, 14 Jul 2022 10:51:04 -0400
From: Ryan Shea <[email protected]>
To: [email protected]
Subject: Failover + Static host definitions
Message-ID:
<CAL6QW496AknMABKu2874L=MSWvWp_Q9THoUm8QLQnnOjPhO=t...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20220714/12157430/attachment-0001.htm>
------------------------------
Message: 2
Date: Thu, 14 Jul 2022 11:22:13 -0400
From: "Richard L. Hamilton" <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Failover + Static host definitions
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
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 <[email protected]> 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
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
Message: 3
Date: Fri, 15 Jul 2022 11:04:26 +1000
From: Glenn Satchell <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Failover + Static host definitions
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20220715/6852c278/attachment-0001.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
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
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 165, Issue 6
******************************************
