[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dhcp-server
Subject:    Re: merging two dhcpd.leases
From:       "Francois" <d.tremblay () globetrotter ! net>
Date:       2002-05-28 15:08:15
[Download RAW message or body]

   *** From dhcp-server -- To unsubscribe, see the end of this message. ***


ok thanks, I will go ahead

----- Original Message -----
From: "Simon Hobson" <shobson@colony.com>
To: <dhcp-server@isc.org>
Sent: Tuesday, May 28, 2002 9:45 AM
Subject: Re: merging two dhcpd.leases


>    *** From dhcp-server -- To unsubscribe, see the end of this message.
***
>
>
> >> Alexander Harrington wrote:
> >>
> >> >I'm no expert but couldn't you just turn the second DHCP server off.
> >> >
> >> >Add the range it used to serve to the first DHCP server.
> >> >
> >> >The first server won't hand out DHCP leases to addresses previously
> >> >assigned to the second server unless they fail a ping test - so over
1x
> >> >your maximum lease time, the whole system should sort itself out.
>
>
> >> This would be a bad way to do it, you will end up with MANY abandoned
> >leases.
> >>
> >> If (and only IF) you have enough addresses available you could just
turn
> >> off the second server, and make sure that the single server has enough
> >> addresses to serve all the clients WITHOUT any overlap with the range
> >> served by the defunct server. After the max lease time of the defunct
> >> server, all it's addresses should be free for re-use and can be added
to
> >> the single server.
>
>
> >I don't think you understood what I want to do.
> >
> >First of all, I have no failover.  I have two servers in split pool.  So
the
> >first one has the beginning of the address range and second one has the
end
> >(let's say Server A and Server B).  Now I want to have just the <Server
A>
> >with full range in dhcpd.conf.  So if I merge Server B dhcpd.leases at
the
> >end of Server A dhcpd.leases, the Server A will know about every leases.
> >
> >what do you think?
>
>
> I understand exactly what you want, and as someone else replied, I believe
> you could just append the two leases files with a big proviso : the
servers
> must have the same leases file format ! If they are both the same software
> then this won't be an issue, but different dhcp servers (I'm moderately
> familiar with the SCO one) have different lease file formats.
>
>
> I was replying more to Alexander Harrington, explaining why his suggestion
> of just turning one server off and giving it's range to the other is a bad
> idea (lots of abandoned leases). The technique I outlined is a generic
> means of migrating clients from one dhcpd server to another (without the
> luxury of enough spare addresses to make the switch in one go) and will
> work whatever the dhcp servers are.
>
>
> Simon
>
>
>
> --
> Simon Hobson, Technical Services Engineer
> Colony Gift Corporation Limited
> Lindal in Furness, Ulverston, Cumbria, LA12 0LD
> Tel 01229 461100, Fax 01229 461101
>
> Registered in England No. 1499611
> Regd. Office : 100 New Bridge Street, London, EC4V 6JA.
>
>
>
> -----------------------------------------------------------------------
> List Archives : http://www.isc.org/ml-archives/dhcp-server/
> Unsubscribe   : http://www.isc.org/dhcp-lists.html
> -or-          : mailto:dhcp-server-request@isc.org?Subject=unsubscribe
> -----------------------------------------------------------------------
>
>


-----------------------------------------------------------------------
List Archives : http://www.isc.org/ml-archives/dhcp-server/
Unsubscribe   : http://www.isc.org/dhcp-lists.html    
-or-          : mailto:dhcp-server-request@isc.org?Subject=unsubscribe  
-----------------------------------------------------------------------

[prev in list] [next in list] [prev in thread] [next in thread]