<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 06/25/2015 01:39 PM, Gregory Sloop wrote:<br>
<blockquote cite="mid:1472904894.20150625133959@sloop.net"
type="cite">
<title>Re: Failback causes lost lease</title>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<table bgcolor="#ffffff">
<tbody>
<tr>
<td width="2" bgcolor="#0000ff"><br>
</td>
<td><span style=" font-family:'courier new'; font-size:
9pt;">Gregory,<br>
<br>
Thanks for your reply.<br>
<br>
On 06/25/2015 12:47 PM, Gregory Sloop wrote:<br>
Re: Failback causes lost lease <span style=" color:
#800000;"><b>SM> In testing my dhcp failover, I
pulled the ethernet cable on the primary<br>
SM> server.<br>
<br>
SM> The secondary server acknowleged renewal
requests as expected.<br>
<br>
SM> Then I plugged the cable back in. After both
the primary and secondary<br>
SM> had moved from communications-interrupted to
normal, the secondary logs<br>
SM> multiple dhcp requests from a client whose
lease is owned by the primary<br>
SM> server. The primary server does not log any
of these but the last <br>
SM> request, reporting that "lease in transition
state expired".<br>
<br>
SM> Then the secondary server logs a DHCPDISCOVER
from that client and <br>
SM> records it load balancing to the primary
server.<br>
<br>
SM> The primary server also sees the DHCPDISCOVER
and offers a new lease <br>
SM> that is not the same number as the previous
lease. This despite the old<br>
SM> number not having been reassigned.<br>
<br>
SM> The end result is that failback causes my
clients to change their ip <br>
SM> address.<br>
<br>
SM> Why does this happen and how can I prevent
it?<br>
<br>
SM>
_______________________________________________<br>
SM> dhcp-users mailing list<br>
</b></span></span><a moz-do-not-send="true" style="
font-family:'courier new'; font-size: 9pt;"
href="mailto:dhcp-users@lists.isc.org">SM>
dhcp-users@lists.isc.org</a><br>
<a moz-do-not-send="true" style=" font-family:'courier
new'; font-size: 9pt;"
href="https://lists.isc.org/mailman/listinfo/dhcp-users">SM>
https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
<br>
<span style=" font-family:'courier new'; font-size: 9pt;">1)
Logs would be good.<br>
</span></td>
</tr>
</tbody>
</table>
</blockquote>
Primary Server:<br>
=========<br>
<br>
Jun 25 11:33:00 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:33:00 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:36:23 dhcpd: timeout waiting for failover peer partner<br>
Jun 25 11:36:23 dhcpd: peer partner: disconnected<br>
Jun 25 11:36:23 dhcpd: failover peer partner: I move from normal to
communications-interrupted<br>
Jun 25 11:42:38 dhcpd: failover peer partner: peer moves from normal
to communications-interrupted<br>
Jun 25 11:42:38 dhcpd: failover peer partner: I move from
communications-interrupted to normal<br>
Jun 25 11:42:38 dhcpd: balancing pool 7f4c9a14cb80 10.112.0.0/13
total 1024 free 511 backup 512 lts 0 max-own (+/-)102<br>
Jun 25 11:42:38 dhcpd: balanced pool 7f4c9a14cb80 10.112.0.0/13
total 1024 free 511 backup 512 lts 0 max-misbal 153<br>
Jun 25 11:42:38 dhcpd: balancing pool 7f4c9a143260 10.104.0.0/13
total 1024 free 512 backup 512 lts 0 max-own (+/-)102<br>
Jun 25 11:42:38 dhcpd: balanced pool 7f4c9a143260 10.104.0.0/13
total 1024 free 512 backup 512 lts 0 max-misbal 154<br>
Jun 25 11:42:38 dhcpd: balancing pool 7f4c9a13a930 10.96.0.0/13
total 1024 free 512 backup 512 lts 0 max-own (+/-)102<br>
Jun 25 11:42:38 dhcpd: balanced pool 7f4c9a13a930 10.96.0.0/13
total 1024 free 512 backup 512 lts 0 max-misbal 154<br>
Jun 25 11:42:38 dhcpd: failover peer partner: peer moves from
communications-interrupted to normal<br>
Jun 25 11:43:38 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112: lease in transition state expired<br>
Jun 25 11:43:39 dhcpd: DHCPDISCOVER from 00:19:d1:4d:03:f8 via
em2.112<br>
Jun 25 11:43:40 dhcpd: DHCPOFFER on 10.112.2.201 to
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:43:40 dhcpd: uid lease 10.112.1.1 for client
00:19:d1:4d:03:f8 is duplicate on 10.112.0.0/13<br>
Jun 25 11:43:40 dhcpd: DHCPREQUEST for 10.112.2.201 (10.112.0.104)
from 00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:43:40 dhcpd: DHCPACK on 10.112.2.201 to 00:19:d1:4d:03:f8
via em2.112<br>
<br>
Secondary Server:<br>
===========<br>
Jun 25 11:36:21 dhcpd: timeout waiting for failover peer partner<br>
Jun 25 11:36:21 dhcpd: peer partner: disconnected<br>
Jun 25 11:36:21 dhcpd: failover peer partner: I move from normal to
communications-interrupted<br>
Jun 25 11:37:34 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:37:34 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:39:10 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:39:10 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:40:11 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:40:11 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:40:44 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:40:44 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:41:16 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:41:16 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:41:47 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:41:47 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:42:12 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:42:12 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:42:37 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112<br>
Jun 25 11:42:37 dhcpd: DHCPACK on 10.112.1.1 to 00:19:d1:4d:03:f8
via em2.112<br>
Jun 25 11:42:38 dhcpd: failover peer partner: peer moves from normal
to communications-interrupted<br>
Jun 25 11:42:38 dhcpd: failover peer partner: I move from
communications-interrupted to normal<br>
Jun 25 11:42:38 dhcpd: balancing pool 7f325dbfdb30 10.112.0.0/13
total 1024 free 511 backup 512 lts 0 max-own (+/-)102<br>
Jun 25 11:42:38 dhcpd: balanced pool 7f325dbfdb30 10.112.0.0/13
total 1024 free 511 backup 512 lts 0 max-misbal 153<br>
Jun 25 11:42:38 dhcpd: balancing pool 7f325dbf4210 10.104.0.0/13
total 1024 free 512 backup 512 lts 0 max-own (+/-)102<br>
Jun 25 11:42:38 dhcpd: balanced pool 7f325dbf4210 10.104.0.0/13
total 1024 free 512 backup 512 lts 0 max-misbal 154<br>
Jun 25 11:42:38 dhcpd: balancing pool 7f325dbeb8e0 10.96.0.0/13
total 1024 free 512 backup 512 lts 0 max-own (+/-)102<br>
Jun 25 11:42:38 dhcpd: balanced pool 7f325dbeb8e0 10.96.0.0/13
total 1024 free 512 backup 512 lts 0 max-misbal 154<br>
Jun 25 11:42:38 dhcpd: failover peer partner: peer moves from
communications-interrupted to normal<br>
Jun 25 11:43:06 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112: lease owned by peer<br>
Jun 25 11:43:13 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112: lease owned by peer<br>
Jun 25 11:43:24 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112: lease owned by peer<br>
Jun 25 11:43:38 dhcpd: DHCPREQUEST for 10.112.1.1 from
00:19:d1:4d:03:f8 via em2.112: lease owned by peer<br>
Jun 25 11:43:39 dhcpd: DHCPDISCOVER from 00:19:d1:4d:03:f8 via
em2.112: load balance to peer partner<br>
Jun 25 11:43:40 dhcpd: DHCPREQUEST for 10.112.2.201 (10.112.0.104)
from 00:19:d1:4d:03:f8 via em2.112: lease owned by peer<br>
<br>
<blockquote cite="mid:1472904894.20150625133959@sloop.net"
type="cite">
<table bgcolor="#ffffff">
<tbody>
<tr>
<td><span style=" font-family:'courier new'; font-size:
9pt;">
2) I think something with your config is broken. If I
were to [wildly] guess, it's a physical/network layer
issue.<br>
3) I have a very small setup with 100+ clients, and it
certainly doesn't work this way for me. <br>
<br>
There are some issues when a single server is up and in
"communications interrupted" mode and you've got a tight
IP pool and the leases were fairly evenly balanced
against both servers. [I've posted, in the past, about
an event that was kinda ugly for this client while
running a 4.1 version [IIRC]. *However* those problems
should be vastly less of a problem with 4.2+ - and
you're not having an issue with communications
interrupted anyway.<br>
</span></td>
</tr>
</tbody>
</table>
</blockquote>
<br>
<blockquote cite="mid:1472904894.20150625133959@sloop.net"
type="cite">
<table bgcolor="#ffffff">
<tbody>
<tr>
<td><span style=" font-family:'courier new'; font-size:
9pt;">
I am having an issue with communications interrupted.
When I pull the ethernet cable, both the primary and
secondary servers move from normal to
communications-interrupted.</span></td>
</tr>
</tbody>
</table>
<span style=" font-family:'courier new'; font-size: 9pt;">But in
your initial post on this thread you said: <br>
<br>
> "<span style=" color: #800000;"><b>After both the primary
and secondary<br>
> had moved from communications-interrupted to normal"<br>
<br>
</b><span style=" color: #000000;">It can't be both ways.
Either they are CI, or in a Normal state. It can't be both.<br>
Like I said, logs would probably be helpful. [Unless someone
else has a lightening bolt moment and can tell you exactly
what's wrong without them - but I doubt that.<br>
</span></span></span></blockquote>
I hope the logs above help.<br>
</body>
</html>