move lease file?
alexis.lameire at gmail.com
Tue Feb 7 15:51:59 UTC 2017
We have similar use case (update of DHCP server).
According to the DHCPD documentation, I strongly suggest you to not import
leases files. When you see the manual, you have no guarenties that the
lease file is consistent between two version.
In addition, when your leases are attributed, a precheck is made to verify
if the ip is in use, if the ip is used it's marked as abandonned lease and
never checked again. When you are near to the full usage of your pool, the
abandonned leases are recheck and reallowed if ip is free of use. So you
can migrate with an empty lease file.
2017-02-07 15:41 GMT+01:00 Bob Harold <rharolde at umich.edu>:
> On Tue, Feb 7, 2017 at 5:35 AM, Bernd Nachtigall <bnacht at web.de> wrote:
>> Am Dienstag, 7. Februar 2017, 10:08:15 CET schrieb Simon Hobson:
>> > Bernd Nachtigall <bnacht at web.de> wrote:
>> > > I plan to setup a new DHCP hardware. (Configuration is not changed)
>> > > It is necessary to copy the old dhcpd.leases to the new server to
>> get an
>> > > noiseless move?
>> > Yes, if you are replacing the DHCP server, then you should copy the
>> > file from the old server to it.
>> is up and running :-)
> Just for completeness - If you have a pair of DHCP servers with failover,
> then you can just move one server at a time and give it time to sync the
> leases file from the other server.
> Bob Harold
> dhcp-users mailing list
> dhcp-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users