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. Re: Failover state changes (Steven Carr)
2. Re: Host definitions in lease file (Simon Hobson)
3. Re: Failover state changes (kraishak)
4. Re: Host definitions in lease file (Surya Teja)
----------------------------------------------------------------------
Message: 1
Date: Fri, 29 Nov 2019 16:56:59 +0000
From: Steven Carr <sjc...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Failover state changes
Message-ID:
<CALMep063_2G9HgpWo2ou=h4rkerfo32_yyugg0w5jmsnxaa...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Why are you putting the system into partner-down? You only need to do
this if the partner is actually down.
30 minutes recovery time (RECOVER-WAIT) is because your MCLT value is
1800. This is normal. This is how failover works when recovering from
partner-down (hence why you should avoid using partner-down unless
absolutely necessary).
If you're updating the configuration then just update the config on
both systems and restart them. If you're using canned init scripts
then make sure they aren't doing anything stupid like causing the
systems to go into partner-down.
Highly recommend getting a copy of the DHCP Handbook and reading the
section on DHCP Failover.
Steve
On Fri, 29 Nov 2019 at 07:09, Kraishak Mahtha <kraishak....@gmail.com> wrote:
>
>
> Hi
> I am using the isc dhcp in standalone and it is working fine with that mode,
> I added the dhcp failover to my existing setup which caused the issue to my
> setup
>
> The server is in partner down state for so long time which made me panic.
> How can I reduce this time and make them in to normal normal state
> FYI: I did some reading and found one param max-unacked-updates which was
> configured to 10 when i tried for the first time thought it would be the
> cause and I increased its value to 5000 because my config contains nearly
> 800 subnets data which is large but no luck
> Does any one face same issue while adding the failover or any idea or
> suggestion how to decrease the time taking to recover the failover states
> into normal normal
>
> on Primary state changes
> cat dhcpd.leases | egrep "my state|partner state"
> my state partner-down at 5 2019/11/29 06:23:00;
> partner state recover-done at 5 2019/11/29 06:52:59;
> my state normal at 5 2019/11/29 06:52:59;
> partner state recover-done at 5 2019/11/29 06:52:59;
> my state normal at 5 2019/11/29 06:52:59;
> partner state normal at 5 2019/11/29 06:53:00;
> On failover state changes
> cat dhcpd.leases | egrep "my state|partner state"
> my state recover at 5 2019/11/29 06:22:59;
> partner state communications-interrupted at 5 2019/11/29 06:23:00;
> my state recover at 5 2019/11/29 06:22:59;
> partner state communications-interrupted at 5 2019/11/29 06:23:00;
> my state recover at 5 2019/11/29 06:22:59;
> partner state partner-down at 5 2019/11/29 06:23:00;
> my state recover-wait at 5 2019/11/29 06:22:59;
> partner state partner-down at 5 2019/11/29 06:23:00;
> my state recover-done at 5 2019/11/29 06:52:59;
> partner state partner-down at 5 2019/11/29 06:23:00;
> my state recover-done at 5 2019/11/29 06:52:59;
> partner state normal at 5 2019/11/29 06:53:00;
> my state normal at 5 2019/11/29 06:53:00;
> partner state normal at 5 2019/11/29 06:53:00;
>
> on Primary Server
> ========================================
> failover peer "peer5" {
> primary;
> address YYY.YYY.YY.YYY;
> port 647;
> peer address YYY.YYY.YY.YYY;
> peer port 647;
> max-response-delay 30;
> max-unacked-updates 5000;
> load balance max seconds 3;
> mclt 1800;
> split 128;
> }
> on failover server
> ==========================================
> failover peer "peer5" {
> secondary;
> address YYY.YYY.YY.YYY;
> port 647;
> peer address YYY.YYY.YY.YYY;
> peer port 647;
> max-response-delay 30;
> max-unacked-updates 5000;
> load balance max seconds 3;
> }
>
> It took nearly 30 minutes which makes issue for my environment, Do we have
> any tunable parameters
>
> Thanks in Advance
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
Message: 2
Date: Fri, 29 Nov 2019 22:31:44 +0000
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Host definitions in lease file
Message-ID: <3d88bcc9-e8e9-4ac4-b238-7974e4e1e...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii
Surya Teja <suryateja...@gmail.com> wrote:
> I have the host reservation data in the configuration file and it is working
> fine, the host is getting the same IP which has been configured in the conf
> file But I don't see the lease entry of the host IP in the
> lease files, Does the ISC dhcpd doesn't store the lease data of the host
> entries in the lease file?
> if not do we have a way to get the info of active hosts list from the
> specified DHCP server?
If you use a host declaration then no lease record is stored. Basically,
there's no need since all the information the server needs to service the
client is in the host declaration. The server doesn't keep track of these
non-leases, and nothing is stored in the leases file.
The server now supports reserved leases. By setting the reserved flag, a lease
will be reserved for only that client (so fixed address much like with a host
statement & fixed-address statement) - but as it's a "real" lease it goes
through the normal lease lifecycle.
------------------------------
Message: 3
Date: Fri, 29 Nov 2019 21:55:56 -0600 (CST)
From: kraishak <kraishak....@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: Failover state changes
Message-ID: <1575086156213-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii
Steven Thanks for response
This is what exactly happened, When I add the failover to my production
system the peer went into to recovery, recover-wait state for so long time
and peer is not offering the leases which made me panic and I restore the
old config which is standalone config(no failover) which worked fine for
that time, So I want to do the failover in my sand box environment with
similar config and check the duration
So I got these doubts
Does DHCP Offer IP when the server is in recover, recover-wait state?
How can the time duration be reduced to make them normal -normal in order
not face same issue, If MClt is the deciding parameter can we reduce it to 5
or 10 min will it be suggestible param value
Why are you putting the system into partner-down? You only need to do
this if the partner is actually down. ------>
No the steps I am doing on my test environment is as follows, Added failover
to the primary which is taking so long time, so trying with changing the
parameter value by stopping the dhcpd on failover, delete the lease file and
touch it back and restart dhcpd on the failover, I didn't put any peer into
partner-down state manually I just stop dhcpd on failover and start it back
by deleting and recreating the lease file, not sure whether this process
triggered to make it partner-down
--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/
------------------------------
Message: 4
Date: Sat, 30 Nov 2019 09:37:08 +0530
From: Surya Teja <suryateja...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Host definitions in lease file
Message-ID:
<CA+0Ac3xG9mEX==_g8UWWoNWzuqV4LKJJ0_V=fybjlb-ent8...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks for reply Simon,
I just want to know how many of the active lease of the dhcp server, So
from the lease file I am getting the info of all scope IP's but reserved is
missing just curios to know if there is way to get the info of the active
host objects
I have one more doubt I am putting all my host declaration statements in
there respective subnet section just to maintain my conf easy readable to
know this host IP belongs to this subnet like that, when i restart the
dhcpd it gives me warning
saying warning that host declarations should be global , yes the
functionality is working fine but just want to know will it impact any
server performance?
On Sat, Nov 30, 2019 at 4:02 AM Simon Hobson <dh...@thehobsons.co.uk> wrote:
> Surya Teja <suryateja...@gmail.com> wrote:
>
> > I have the host reservation data in the configuration file and it is
> working fine, the host is getting the same IP which has been configured in
> the conf file But I don't see the lease entry of the host IP in the
> > lease files, Does the ISC dhcpd doesn't store the lease data of the
> host entries in the lease file?
> > if not do we have a way to get the info of active hosts list from the
> specified DHCP server?
>
> If you use a host declaration then no lease record is stored. Basically,
> there's no need since all the information the server needs to service the
> client is in the host declaration. The server doesn't keep track of these
> non-leases, and nothing is stored in the leases file.
>
> The server now supports reserved leases. By setting the reserved flag, a
> lease will be reserved for only that client (so fixed address much like
> with a host statement & fixed-address statement) - but as it's a "real"
> lease it goes through the normal lease lifecycle.
>
> _______________________________________________
> 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/20191130/f07541ca/attachment-0001.htm>
------------------------------
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 133, Issue 11
*******************************************
