Failover concept clarification

[David W. Hankins]

On Thu, Jun 18, 2009 at 04:11:43PM +0530, pat wrote:
> so now i got both the timers from omshell
> 
> mclt=00:00:00:0a
> partner-state=00:00:00:02
> local-state=00:00:00:03

State 3 is 'communications-interrupted' in all versions.  What I
described only takes affect in partner-down (either 1 or 4 depending
on version), which I thought from your earlier description you had
said you had set the local state to.

In communications-interrupted, the server cannot be sure that the
peer is not assigning leases to clients, so it cannot allocate from
the peer's free-state pool at any time.

> partner-stos=4a:38:99:e4
> local-stos=4a:3a:05:2a
> 
> so now what is the timer it will wait for to server all the lease.

In communications-interrupted, never.

In partner-down, local-stos+mclt, but this is easier to observe in the
dhcpd.leases file's lastmost 'failover {}' stanza.

-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
-------------- 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/20090618/b8cd0042/attachment.bin>