DHCP failover lease balancing with nearly saturated pools

[David W. Hankins]

On Wed, Jan 28, 2009 at 01:48:15PM -0600, Jack Kielsmeier wrote:
> Currently, when the pools become nearly 100% saturated, the primary
> server throws out 'peer holds all free leases' errors. This is correct
> because the peer holds the final lease. Since I'm shipping all traffic
> to the primary server, that last lease will never be given out.

I don't know as of what version, but if the servers agree on the
lease states (no db synch. problems), then the secondary should know
that there are zero free leases and will over-ride the LBA
algorithm.

So the version you're running might be an issue.

The only place I'm not sure is if you've got a series of pools in a
given shared network, and some of them have ACL's applied that don't
match the client.

The other thing is that the peer should offer the lease if the client
has been (re)trying for more than 'load balance max secs (n);'.
Note that this is advertised by the client (in the BOOTP header 'secs'
field), so the servers don't have a lot of say about it, but most
clients put something useful there.

-- 
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: 194 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20090128/ddc1da74/attachment.bin>