static IP allocations in dynamic ranges -why not?

[Foggi, Nicola]

Something like this will set the reserved flag via omshell:

port 7911
server 10.1.1.1
key xxxx xxxx
connect
new lease
set ip-address=$IP
open
set flags=04:00:00:00
update
refresh

you do need to set it on both servers if you're running failover between them.  You cannot unset it reserved from what i've found.  The funkiness I've seen that ISN'T patched yet:

1. Lease prioritization in a 2 server pair environment the lease prioritization that classifies the "reserved" lease as preferred over a new lease is not always accurate, so doing a dhcp discover may result in a different ip being assigned.  We've seen it pretty heavily, a patch that seems to work for me is posted here:

https://lists.isc.org/mailman/htdig/dhcp-users/2009-November/010355.html

the response was that should never be executed as it overlaps, but without it i have problems, i haven't had time to go track down if there is a bug somewhere else.

2. If the lease is not in an ACTIVE state when you set it to RESERVED the server will error out and shut down with an error message something like lease state transition invalid.  You can then go manually edit the lease file and fix the lease.  Again, only saw this on our failover pair of dhcp servers, not on a stand alone, but this was harder to duplicate, so i may of not done it right on the stand alone.

This one is pretty annoying when it happens... probably an easy way to fix it, but haven't had time...

Nicola
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3646 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20100607/8e7446c5/attachment.bin>