<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFCC">
Just to clarify, "host reservations" can be two things.<br>
<br>
Host statement, possibly with a fixed address statement -
synchronized via file transfer.<br>
<br>
Reservation in the leases file - how would these function in a fail
over pair?<br>
<br>
<br>
<div class="moz-cite-prefix">On 31/07/2018 16.16, Thomas Markwalder
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:fa1eaa1b-8997-09b3-b000-3c0bd6779d1b@isc.org">Hello
Sandra:
<br>
<br>
Yes. Anything specified via configuration file must be sync'd
outside of ISC DHCP.
<br>
Fail over, in ISC DHCP, is based on draft RFC:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-dhc-failover-12">https://tools.ietf.org/html/draft-ietf-dhc-failover-12</a>
<br>
<br>
It does not call for exchanging information beyond lease and
server state information, and
<br>
was written such that any two servers which adhere to it, should
be inter operable. At least
<br>
that was the original intent.
<br>
<br>
Host reservations are "a policy mechanism" and as such are not
governed by RFCs. Thus they
<br>
are entirely specific to DHCP server implementations.
<br>
<br>
Regards,
<br>
<br>
Thomas Markwalder
<br>
ISC Software Engineering
<br>
<br>
On 07/31/2018 10:00 AM, Sandra Schlichting wrote:
<br>
<blockquote type="cite">
<blockquote type="cite">One point of clarification, Host
reservations are not synchronized
<br>
between servers via fail over. Any host reservations you have
in one
<br>
configuration file, you must include in the peer server's
configuration
<br>
file. For dynamic reservations (i.e. those that do not
include a fixed
<br>
address), the leases allocated for each host will be
synchronized
<br>
(assuming they come from within a FO pool), but not the actual
<br>
reservation specifications.
<br>
</blockquote>
So for the reservation I would have to rsync/scp them over?
<br>
_______________________________________________
<br>
dhcp-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
dhcp-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
<br>
</blockquote>
<br>
</body>
</html>