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 dhcpd pair stuck in partner-down/shutdown state
(Bob Harold)
2. Re: Failover dhcpd pair stuck in partner-down/shutdown state
(Eugene Grosbein)
3. Re: Failover dhcpd pair stuck in partner-down/shutdown state
(Bob Harold)
4. Re: Failover dhcpd pair stuck in partner-down/shutdown state
(Thomas Markwalder)
5. clients internet issue because of different lease time in
dhcp failover (Usman Ahmad)
----------------------------------------------------------------------
Message: 1
Date: Wed, 2 Jan 2019 10:24:20 -0500
From: Bob Harold <rharo...@umich.edu>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Failover dhcpd pair stuck in partner-down/shutdown state
Message-ID:
<ca+nkc8bbyfltfj1d1pthqz0jce502qzc5jpl53u4is3d3uq...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Tue, Dec 25, 2018 at 4:24 AM Eugene Grosbein <eu...@grosbein.net> wrote:
> Hi!
>
> I run two ISC DHCP Servers version 4.3.5 in failover mode.
>
> They have been running just fine for several years being upgraded from
> time to time
> until recently I found that first one runs in "partner-down" state
> and second in "shutdown" state despite of tcp/647 control connection
> in perfectly working state and data running over it according to tcpdump.
>
> They were running in such state for very long time (over a year) and
> I have no old logs to check due to log rotation. At the moment,
> second server added "not responding (shut down)" to
> DHCPDISCOVER/DHCPREQUEST
> lines written to its log.
>
> I tried to resolve the issue by stopping second dhcpd completely
> and starting it again. At start, it wrote to the log:
>
> dhcpd: failover peer default: I move from shutdown to startup
>
> Then it connected its control connection tcp/647 to second server,
> exchanged some data over the connection, appended to dhcpd.leases file:
>
> failover peer "default" state {
> my state shutdown at 4 2017/03/30 02:17:13;
> partner state partner-down at 4 2017/03/30 02:17:13;
> mclt 60;
> }
>
> Then it wrote to the log:
>
> dhcpd: failover peer default: I move from startup to shutdown
>
> And things settle again in same state.
>
> Restart of first server did not help either.
>
> I was forced to stop both of servers for short time, manually delete all
> "failover" records quoted above from both dhcpd.leases files
> and start servers again. Only then both servers got to "normal" state
> (editing only one of dhcpd.leases files did not help).
>
> My question: why did servers stuck in partner-down/shutdown state "forever"
> and could not get from it without manual intervention despite of perfectly
> working
> control TCP connection? Is this problem fixed in recent versions?
>
> Here is dhcpd.conf of first server:
>
> # default ports tcp/647
>
> failover peer "default" {
> primary;
> address 62.231.191.161;
> peer address 62.231.191.174;
> max-response-delay 60;
> max-unacked-updates 10;
> mclt 60;
> split 128;
> auto-partner-down 60;
> load balance max seconds 3;
> }
>
> subnet 62.231.191.160 netmask 255.255.255.252 {}
> include "/usr/local/etc/dhcpd.master";
>
> Second server uses same configuraton except of IP addresses
> and it uses identical dhcpd.master file containin rest of configuration.
>
>
When you say " Second server uses same configuraton ", I hope you did not
accidentally mark both as "primary".
Here is the config on one of my pairs, for comparision:
-------- first server ------------
failover peer "mydhcppair1"
{
primary;
address 141.211.147.232;
port 847;
peer address 141.211.147.248;
peer port 647;
max-response-delay 60;
max-unacked-updates 10;
mclt 1800;
split 128;
load balance max seconds 3;
}
-------- second server ------------
failover peer "mydhcppair1"
{
secondary;
address X.X.X.248;
port 647;
peer address X.X.X.232;
peer port 847;
max-response-delay 60;
max-unacked-updates 10;
load balance max seconds 3;
}
Note that "mclt" and "split" can only be specified on the primary.
--
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20190102/d7815b5e/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 2 Jan 2019 23:26:09 +0700
From: Eugene Grosbein <eu...@grosbein.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Failover dhcpd pair stuck in partner-down/shutdown state
Message-ID: <7a13c439-7b0a-a62f-9b6b-0be4ddf35...@grosbein.net>
Content-Type: text/plain; charset=windows-1252
02.01.2019 22:24, Bob Harold wrote:
> When you say " Second server uses same configuraton ", I hope you did not
> accidentally mark both as "primary".
No, second is secondary just like in your configuration.
> Here is the config on one of my pairs, for comparision:
>
> -------- first server ------------
>
> failover peer "mydhcppair1"
> {
> primary;
> address 141.211.147.232;
> port 847;
> peer address 141.211.147.248;
> peer port 647;
> max-response-delay 60;
> max-unacked-updates 10;
> mclt 1800;
> split 128;
> load balance max seconds 3;
> }
>
>
> -------- second server ------------
>
> failover peer "mydhcppair1"
> {
> secondary;
> address X.X.X.248;
> port 647;
> peer address X.X.X.232;
> peer port 847;
> max-response-delay 60;
> max-unacked-updates 10;
> load balance max seconds 3;
> }
>
> Note that "mclt" and "split" can only be specified on the primary.
Hmm, I have "mclt" in the config of secondary server by accident
and it does not complain... Can it be a culprit?
Also, both of my servers use same default control port.
# default ports tcp/647
failover peer "default" {
secondary;
address 62.231.191.174;
peer address 62.231.191.161;
max-response-delay 60;
max-unacked-updates 10;
mclt 60;
auto-partner-down 60;
load balance max seconds 3;
}
subnet 62.231.191.172 netmask 255.255.255.252 {}
include "/usr/local/etc/dhcpd.master";
------------------------------
Message: 3
Date: Wed, 2 Jan 2019 11:33:05 -0500
From: Bob Harold <rharo...@umich.edu>
To: Eugene Grosbein <eu...@grosbein.net>
Cc: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Failover dhcpd pair stuck in partner-down/shutdown state
Message-ID:
<ca+nkc8b+ouu1ezb3vvc3ox4gk-r8spysjy_ivl_b4l-itc4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Wed, Jan 2, 2019 at 11:26 AM Eugene Grosbein <eu...@grosbein.net> wrote:
> 02.01.2019 22:24, Bob Harold wrote:
>
> > When you say " Second server uses same configuraton ", I hope you did
> not accidentally mark both as "primary".
>
> No, second is secondary just like in your configuration.
>
> > Here is the config on one of my pairs, for comparision:
> >
> > -------- first server ------------
> >
> > failover peer "mydhcppair1"
> > {
> > primary;
> > address 141.211.147.232;
> > port 847;
> > peer address 141.211.147.248;
> > peer port 647;
> > max-response-delay 60;
> > max-unacked-updates 10;
> > mclt 1800;
> > split 128;
> > load balance max seconds 3;
> > }
> >
> >
> > -------- second server ------------
> >
> > failover peer "mydhcppair1"
> > {
> > secondary;
> > address X.X.X.248;
> > port 647;
> > peer address X.X.X.232;
> > peer port 847;
> > max-response-delay 60;
> > max-unacked-updates 10;
> > load balance max seconds 3;
> > }
> >
> > Note that "mclt" and "split" can only be specified on the primary.
>
> Hmm, I have "mclt" in the config of secondary server by accident
> and it does not complain... Can it be a culprit?
>
> Also, both of my servers use same default control port.
>
> # default ports tcp/647
> failover peer "default" {
> secondary;
> address 62.231.191.174;
> peer address 62.231.191.161;
> max-response-delay 60;
> max-unacked-updates 10;
> mclt 60;
> auto-partner-down 60;
> load balance max seconds 3;
> }
>
> subnet 62.231.191.172 netmask 255.255.255.252 {}
> include "/usr/local/etc/dhcpd.master";
>
>
Your config looks correct to me. I don't have any other clues.
--
Bob Harold
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20190102/b301ca36/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 2 Jan 2019 15:08:38 -0500
From: Thomas Markwalder <tm...@isc.org>
To: dhcp-users@lists.isc.org
Subject: Re: Failover dhcpd pair stuck in partner-down/shutdown state
Message-ID: <ad571c1c-7efa-9e5c-4d73-3e17a2c34...@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Hello:
I suspect that at some point in the past one of the servers was put into
the shutdown state by setting it's state to shutdown (8) via omshell.?
This caused the other server to toggle to partner-down (4).? They
servers will stay that way until you take them through recovery by
setting the partner-down peer's state to recover (6).? When a server is
set to shutdown state it remains that until you intervene.? This is
intended to allow you to do maintenance and what not with minimal issues.
Regards,
Thomas Markwalder
ISC Software Engineering
On 12/25/18 4:23 AM, Eugene Grosbein wrote:
> Hi!
>
> I run two ISC DHCP Servers version 4.3.5 in failover mode.
>
> They have been running just fine for several years being upgraded from time
> to time
> until recently I found that first one runs in "partner-down" state
> and second in "shutdown" state despite of tcp/647 control connection
> in perfectly working state and data running over it according to tcpdump.
>
> They were running in such state for very long time (over a year) and
> I have no old logs to check due to log rotation. At the moment,
> second server added "not responding (shut down)" to DHCPDISCOVER/DHCPREQUEST
> lines written to its log.
>
> I tried to resolve the issue by stopping second dhcpd completely
> and starting it again. At start, it wrote to the log:
>
> dhcpd: failover peer default: I move from shutdown to startup
>
> Then it connected its control connection tcp/647 to second server,
> exchanged some data over the connection, appended to dhcpd.leases file:
>
> failover peer "default" state {
> my state shutdown at 4 2017/03/30 02:17:13;
> partner state partner-down at 4 2017/03/30 02:17:13;
> mclt 60;
> }
>
> Then it wrote to the log:
>
> dhcpd: failover peer default: I move from startup to shutdown
>
> And things settle again in same state.
>
> Restart of first server did not help either.
>
> I was forced to stop both of servers for short time, manually delete all
> "failover" records quoted above from both dhcpd.leases files
> and start servers again. Only then both servers got to "normal" state
> (editing only one of dhcpd.leases files did not help).
>
> My question: why did servers stuck in partner-down/shutdown state "forever"
> and could not get from it without manual intervention despite of perfectly
> working
> control TCP connection? Is this problem fixed in recent versions?
>
> Here is dhcpd.conf of first server:
>
> # default ports tcp/647
>
> failover peer "default" {
> primary;
> address 62.231.191.161;
> peer address 62.231.191.174;
> max-response-delay 60;
> max-unacked-updates 10;
> mclt 60;
> split 128;
> auto-partner-down 60;
> load balance max seconds 3;
> }
>
> subnet 62.231.191.160 netmask 255.255.255.252 {}
> include "/usr/local/etc/dhcpd.master";
>
> Second server uses same configuraton except of IP addresses
> and it uses identical dhcpd.master file containin rest of configuration.
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
Message: 5
Date: Thu, 3 Jan 2019 03:16:19 +0400
From: Usman Ahmad <usman....@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: clients internet issue because of different lease time in
dhcp failover
Message-ID:
<CALE1tGpuUqDXr-gG7YoN52-35TC=n1dqo4yjhxf85mhk2yk...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Dear Users,
Today it was mentioned mistakenly a different value of lease time on my two
dhcp server which are configured in failover. Customers gets the IP address
normally but the internet stops working for them.
Could you please explain me that is that a normal behavior or unexpected?
because as per my understanding; if customerA is sending DHCP request to
both DHCP servers and accepts the IP address from single server then
configuration mentioned in that DHCP server should work normally.
please confirm
*--*
*Regards,*
Usman Ahmad
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20190103/0e2b5921/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 123, Issue 2
******************************************
