static IP allocations in dynamic ranges -why not?

[Foggi, Nicola]

We heavily use the RESERVED flag, it can be set via OMAPI.  I will caution you there are some bugs around it that we've run into that i have hacked some code around to make work, but we still run into problems every so often, so be cautious :)

That being said when the RESERVED flag works, it's been great for us!

Nicola

-----Original Message-----
From: dhcp-users-bounces+nfoggi=depaul.edu at lists.isc.org on behalf of Dorsey, Chris
Sent: Thu 6/3/2010 11:35 AM
To: dhcp-users at lists.isc.org
Subject: Re: static IP allocations in dynamic ranges -why not?
 
Glenn, Doug, Simon,

Thank you for the excellent feedback.  Totally understand about the history/design decisions of dhcpd.  I wish I had a piece of code I wrote that is still running for (17) years. :^)   I was reading up on reserved leases last night, and it seems that this might help me navigate the requirements set before us.  I would assume that editing the dhcpd.leases file is a non-starter for all but the most static of environments due to dhcpd writing to the file and the desire to keep dhcpd running as long as possible.  I guess that leaves omapi/omshell.  I looked at that a number of months ago and was able to perform a few operations but it was pretty cryptic.  I should probably take a second look at that along with the Net::ISC::DHCPd::OMAPI perl stuff. In a failover environment, would I need to connect to each server in the pair and set a given lease  as 'reserved', or would the failover communication handle that for me?   Is there a compiled cookbook for common dhcpd configurations and/or omapi-related functions?

Thanks again!
Chris


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