failover timeout

[David W. Hankins]

On Mon, Apr 12, 2010 at 10:32:34PM +1000, Glenn Satchell wrote:
> The theory was that any logic required to determine if the partner was 
> truly down was all external to dhcpd and often very specific to the site. 
> As there is an existing way to remotely control dhcpd using omshell, the 
> idea was to leave the determination to the site admin.
>
> The auto-partner-feature in version 4.2.0 is probably does what you want. 
> Maybe download the source and have a look at the new documentation.

Spot on Glenn.

Note that in 4.2.0a2 I also included an optimization that permits the
servers to "rewind" leases to the state most recently negotiated with
the peer.  This alone may be enough for geographic-diversity types of
server pairings, and you wouldn't want to use auto-partner-down in
such situations because of the risk of addressing conflicts.

auto-partner-down is mainly intended to help operators of "HA",
heartbeat-cable type deployments find failover a more comfortable
interim tool (where disconnection really does mean they are down).

-- 
David W. Hankins	BIND 10 needs more DHCP voices.
Software Engineer		There just aren't enough in our heads.
Internet Systems Consortium, Inc.		http://bind10.isc.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20100413/d7fd32ed/attachment.bin>