Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. combining lease files (project722)
2. Re: combining lease files (Sten Carlsen)
3. Re: combining lease files (Bob Harold)
4. Re: combining lease files (project722)
----------------------------------------------------------------------
Message: 1
Date: Wed, 29 Aug 2018 07:28:27 -0500
From: project722 <project...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: combining lease files
Message-ID:
<capbqmzcv-y4ghuihjq2j7tayo68_gdb3fam5xxyyuxtosol...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hey All,
We are consolidating all subnets on server B and moving to an exisitng
failover pair we have, In order to decom server B. I'll need to take the
leases file from server B and combine whats there with the leases file on
both servers in the failover pair. (doing this to make the failover pair
aware of what leases are already out there that were assigned by server B)
I'm thinking just a simple cat on both files should be fine to combine the
data. And, all 3 servers are running the same verison of dhcp (4.1.1.61)
and RHEL so I don't expect and formatting problems.
However, since failover pairs have more transitional states with the
"binding state" variable, is it possible I will run into any issues doing
this? Is there a better, more preferred way of doing this instead of
merging the leases file?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180829/d24b8852/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 29 Aug 2018 15:33:40 +0200
From: Sten Carlsen <st...@s-carlsen.dk>
To: dhcp-users@lists.isc.org
Subject: Re: combining lease files
Message-ID: <acab9a92-28d5-104a-fd9f-83d311cae...@s-carlsen.dk>
Content-Type: text/plain; charset="utf-8"
On 29/08/2018 14.28, project722 wrote:
> Hey All,
>
> We are consolidating all subnets on server B and moving to an exisitng
> failover pair we have, In order to decom server B. I'll need to take
> the leases file from server B and combine whats there with the leases
> file on both servers in the failover pair. (doing this to make the
> failover pair aware of what leases are already out there that were
> assigned by server B)
I am not sure, but I think one other way could be to make server B part
of a failover pair with one of the existing failover servers for a
period of time. That way the remaining server will have all the
information transferred from server B. Later that configuration could be
changed to have the other remaining failover server act as the peer,
that way the servers would transfer the data, probably with less risk.
Others should confirm or reject this idea.
>
> I'm thinking just a simple cat on both files should be fine to combine
> the data. And, all 3 servers are running the same verison of dhcp
> (4.1.1.61) and RHEL so I don't expect and formatting problems.
>
> However, since failover pairs have more transitional states with the
> "binding state" variable, is it possible I will run into any issues
> doing this? Is there a better, more preferred way of doing this
> instead of merging the leases file?
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180829/22c5e847/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 29 Aug 2018 09:36:16 -0400
From: Bob Harold <rharo...@umich.edu>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: combining lease files
Message-ID:
<ca+nkc8dnha+yed+o+mouemoh8gfgo1koi80drfh716uzaw7...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Wed, Aug 29, 2018 at 9:33 AM Sten Carlsen <st...@s-carlsen.dk> wrote:
>
>
> On 29/08/2018 14.28, project722 wrote:
>
> Hey All,
>
> We are consolidating all subnets on server B and moving to an exisitng
> failover pair we have, In order to decom server B. I'll need to take the
> leases file from server B and combine whats there with the leases file on
> both servers in the failover pair. (doing this to make the failover pair
> aware of what leases are already out there that were assigned by server B)
>
> I am not sure, but I think one other way could be to make server B part of
> a failover pair with one of the existing failover servers for a period of
> time. That way the remaining server will have all the information
> transferred from server B. Later that configuration could be changed to
> have the other remaining failover server act as the peer, that way the
> servers would transfer the data, probably with less risk.
>
> Others should confirm or reject this idea.
>
>
> I'm thinking just a simple cat on both files should be fine to combine the
> data. And, all 3 servers are running the same verison of dhcp (4.1.1.61)
> and RHEL so I don't expect and formatting problems.
>
> However, since failover pairs have more transitional states with the
> "binding state" variable, is it possible I will run into any issues doing
> this? Is there a better, more preferred way of doing this instead of
> merging the leases file?
>
>
The benefit of a failover pair is that we can upgrade/repair/replace one
server at a time without any interruption in service.
Let's call the failover pair A-master and A-failover.
The recommended method is to configure server B as master and the
A-failover server as failover for server B's subnets also. Give it some
time (watch the failover messages in the logs) to sync the data from B to
A-failover. Then move the subnets from B to A-master, and A-master will
sync the data from A-failover.
--
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180829/9720edd0/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 29 Aug 2018 09:13:51 -0500
From: project722 <project...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: combining lease files
Message-ID:
<capbqmzaqdc1jzd8r8m0j9qjfvdhyu1+66bnsxvuuztq6w7r...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks for the feedback guys!
So, in this scenario I'll have 2 masters temporarily - B will become a new
master and sync to A-failover, and A-master will still be in the picture as
well? If I try this approach, then, I will have to add the subnets for
server B to A-failover, then enable failover between B and A-failover?
Wouldn't A-master have a problem with A-failover having subnets in its conf
file that A-master doesn't?
Also, I'm starting to think aboout ip helper addresses. Seems like the flow
would be:
Add an IP helper address on the router for server B's subnets to also point
to A-failover
Once they are completely in sync then remove the IP helper for server B
altogether and add another for A-master
Does that sound about right?
On Wed, Aug 29, 2018 at 8:36 AM Bob Harold <rharo...@umich.edu> wrote:
>
> On Wed, Aug 29, 2018 at 9:33 AM Sten Carlsen <st...@s-carlsen.dk> wrote:
>
>>
>>
>> On 29/08/2018 14.28, project722 wrote:
>>
>> Hey All,
>>
>> We are consolidating all subnets on server B and moving to an exisitng
>> failover pair we have, In order to decom server B. I'll need to take the
>> leases file from server B and combine whats there with the leases file on
>> both servers in the failover pair. (doing this to make the failover pair
>> aware of what leases are already out there that were assigned by server B)
>>
>> I am not sure, but I think one other way could be to make server B part
>> of a failover pair with one of the existing failover servers for a period
>> of time. That way the remaining server will have all the information
>> transferred from server B. Later that configuration could be changed to
>> have the other remaining failover server act as the peer, that way the
>> servers would transfer the data, probably with less risk.
>>
>> Others should confirm or reject this idea.
>>
>>
>> I'm thinking just a simple cat on both files should be fine to combine
>> the data. And, all 3 servers are running the same verison of dhcp
>> (4.1.1.61) and RHEL so I don't expect and formatting problems.
>>
>> However, since failover pairs have more transitional states with the
>> "binding state" variable, is it possible I will run into any issues doing
>> this? Is there a better, more preferred way of doing this instead of
>> merging the leases file?
>>
>>
> The benefit of a failover pair is that we can upgrade/repair/replace one
> server at a time without any interruption in service.
> Let's call the failover pair A-master and A-failover.
> The recommended method is to configure server B as master and the
> A-failover server as failover for server B's subnets also. Give it some
> time (watch the failover messages in the logs) to sync the data from B to
> A-failover. Then move the subnets from B to A-master, and A-master will
> sync the data from A-failover.
>
> --
> Bob Harold
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180829/67ecd3b1/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 118, Issue 23
*******************************************
