Active lease that does not move to expired

[David W. Hankins]

On Wed, Jul 19, 2006 at 12:57:52PM -0400, John Wobus wrote:
> On the primary:
> lease 128.84.152.133 {
>    starts 3 2006/07/19 09:49:44;
>    ends 3 2006/07/19 10:48:44;
>    tstp 3 2006/07/19 10:48:44;
>    tsfp 3 2006/07/19 10:48:44;
>    atsfp 3 2006/07/19 10:48:44;
>    cltt 3 2006/07/19 09:49:44;
>    binding state free;
>    hardware ethernet 00:02:2d:53:32:1e;
>    uid "\001\000\002-S2\036";
> }
> 
> On the secondary:
> lease 128.84.152.133 {
>    starts 3 2006/07/19 09:49:44;
>    ends 3 2006/07/19 10:48:44;
>    tstp 3 2006/07/19 10:48:44;
>    tsfp 3 2006/07/19 10:48:44;
>    atsfp 3 2006/07/19 10:48:44;
>    cltt 3 2006/07/19 09:49:44;
>    binding state active;
>    next binding state expired;
>    hardware ethernet 00:02:2d:53:32:1e;
>    uid "\001\000\002-S2\036";
> }

That's a neat trick.

The primary's entry indicates clearly that the secondary
acknowledged the lease as being in that state.  There's
no reason for the primary to retransmit that lease's
state.

The secondary's entry looks as though it never got the
expired binding update from the primary (whose ACK it
would send to tell the primary to move from expired to
free).


Did you roll back to an older leases database?

Has the secondary been having a bout of restarts?

-- 
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