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. DHCP Failover - initial Configuration (Philippe Maechler)
2. not getting same ip for same MAC (Christopher Barry)
3. Re: not getting same ip for same MAC (Pavel Zhukov)
----------------------------------------------------------------------
Message: 1
Date: Wed, 8 Aug 2018 15:45:19 +0200
From: Philippe Maechler <plcmaech...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: DHCP Failover - initial Configuration
Message-ID:
<caphukgavxijqvebeoaqi8qhcipwk57e-cdlvbb3vzfr-5yj...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello dhcp-users
Yesterday I wrote the same mail to the list, but it never appeared in the
arrchives or in my inbox. Therefor i resend the mail from another address.
sorry if the messaged is now sent multiple times
One of our dhcp 4.3 servers for DOCSIS died last week ? and we?re now in
the process to set up two new servers with version 4.4 ?.
I?d like to introduce failover for some important pools, but still have
open questions
The configuration is split into a few pieces.
The static configuration part is rsynce?d once a day to the secondary node.
Both servers have a .local config, which contains next-server,
time-servers, server-name, the subnet declaration for the management net
and our omapi configuration
The dynamic part comes from another system and is uploaded by ftp two both
servers.
A script runs every 5 minutes and if we have new files from ftp, we build
the configuration and restart the server. The secondary server does the
same, but the daemon is not enabled, so the server won?t serve any requests.
If we have a planned maintenance, we stop both server, rsync the lease.db
and start the secondary node
Further the lease.db from the primary node is fetched every 10 minutes to
another system. So that when the primary server dies, we have a ~10minute
old lease db (depends on the last reload) that we can put on the second node
If we wanna go for failover, what are the right steps to start?
1. Configure failover on the primary node (in the local confg)
2. Choose which we wanna do failover and configure them
3. Restart the primary node and put it into partner down state
4. Configure the second server (failover and pools)
5. Start the second server
6. Put the primary server into partner-up? Mode
Does this sound right?
*/30 networks*
We have about ~240 pools, ~50 pools only contain one single ip address.
Does failover makes sense here?
We can?t use hosts definitions because we only know the option-82. Some
customers have more than one device connected but we can only serve the
single ip address to one of them. If we use failover, can it happen, that
server-1 hands out the ip address to device-1 and server two hand out the
ip to device-2?
*Heavily used pools*
The bigger part is our /24 pools. These are all in a shared network config.
I guess the failover part works pretty fine for the individual pools here.
The shared network is sometimes at 95% usage. Can this lead to problems?
*Server restarts*
Currently we restart the service every 5minutes if something changed. When
we go for failover, we should reload server one and if it synced to his
partner, we can reload the server two. How does server two know, that the
server one is up to date and everything is synced?
The ISC Knowledge Base contains an article about failover setup (
https://kb.isc.org/article/AA-00502/0/A-Basic-Guide-to-Configuring-DHCP-Failover.html)
and part 7 is configuring OMAPI access? Who uses that? Is this for the
communication between primary and secondary or only for putting one server
into partner down mode?
We actually do use omapi to check and expire active leases.
I?m sure that as soon as I hit send, more questions come to my mind ? e.g
good mctl and split values for lease times of 1h
TIA for all your inputs and recommendations
Philippe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180808/5e733d2e/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 8 Aug 2018 11:02:17 -0400
From: Christopher Barry <christopher.r.ba...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: not getting same ip for same MAC
Message-ID: <20180808110217.280af...@obelisk.infinux.org>
Content-Type: text/plain; charset=US-ASCII
configs and leases file here:
https://pastebin.com/Fp7e8378
Problem:
I'm booting an embedded device via u-boot over tftp, and I am getting
one IP during boot, and another IP once Linux comes up. This has not
always done this, and I am struggling to find a solution.
Scenario:
I have a pool with 2 IPs in it, and I boot 2 devices in a test fixture.
Each device position (regardless of physical device) always gets the
same IP, as I am deleting the leases file / restarting dhcpd between
invocations of the test, and I power on the devices in the same order.
Now, device1 boots the tftp image, gets 172.19.0.2 (as it should), then
when Linux boots and requests an IP, it is getting 172.19.0.3 (which it
should NOT do). I have the lease time and max lease time set to 1 (but
I have set these values to many other values up to a couple minutes
with no change).
To be clear, this has worked for over a year, and suddenly is not
working. The Linux platform running dhcpd is centos 7. The dhcpd
version is in the pastebin link above.
NOTE:
In the leases file it can be seen that the uid value is different
between u-boot and linux, even though the MAC is the same. I'm
suspicious that this is what is confusing dhcpd.
How can I MAKE it only use MAC?
Thanks!
--
Regards,
Christopher
------------------------------
Message: 3
Date: Wed, 8 Aug 2018 17:38:49 +0200
From: Pavel Zhukov <pzhu...@redhat.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: not getting same ip for same MAC
Message-ID:
<CAHPvjJLYRm_NHqJWZ6Sc=5zuPJ=boit3nqeb1zdhunkj8ft...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
You can add into your dhclient.conf following statement:
send dhcp-client-identifier = hardware;
On Wed, Aug 8, 2018 at 5:05 PM Christopher Barry
<christopher.r.ba...@gmail.com> wrote:
>
>
> configs and leases file here:
> https://pastebin.com/Fp7e8378
>
> Problem:
> I'm booting an embedded device via u-boot over tftp, and I am getting
> one IP during boot, and another IP once Linux comes up. This has not
> always done this, and I am struggling to find a solution.
>
>
> Scenario:
> I have a pool with 2 IPs in it, and I boot 2 devices in a test fixture.
> Each device position (regardless of physical device) always gets the
> same IP, as I am deleting the leases file / restarting dhcpd between
> invocations of the test, and I power on the devices in the same order.
>
> Now, device1 boots the tftp image, gets 172.19.0.2 (as it should), then
> when Linux boots and requests an IP, it is getting 172.19.0.3 (which it
> should NOT do). I have the lease time and max lease time set to 1 (but
> I have set these values to many other values up to a couple minutes
> with no change).
>
> To be clear, this has worked for over a year, and suddenly is not
> working. The Linux platform running dhcpd is centos 7. The dhcpd
> version is in the pastebin link above.
>
> NOTE:
> In the leases file it can be seen that the uid value is different
> between u-boot and linux, even though the MAC is the same. I'm
> suspicious that this is what is confusing dhcpd.
>
> How can I MAKE it only use MAC?
>
>
> Thanks!
>
> --
> Regards,
> Christopher
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
--
Pavel Zhukov
Software Engineer
IRC: landgraf
------------------------------
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 4
******************************************
