<div dir="ltr">Hi Bill <div>I non-failover DHCP server doesn't have any "failover peer" stanza in the /var/log/dhcpd/dhcpd.leases file ----> <br><div>Sorry for typo in my previous email </div><div><div dir="auto">The environment became most problematic none of the servers are granting leases to devices On the primary lease file it says </div><div dir="auto">my state partner-down</div><div dir="auto">peer state recovery <div>----> Its not peer it is partner state </div><div><br></div><div> A working failover lease file has at the top -----><br>I can see at multiple places in the dhcpd.lease file specifying about these states appended with time stamp saying like <br>failover peer "dhcp-peer-workspace1" state {<br> my state recover at <b>3 2019/10/09 14:23:41;</b><br> partner state unknown-state <b>at 3 2019/10/09 14:23:41;</b><br>}<br><br>failover peer "dhcp-peer-
workspace1
" state {<br> my state recover at <b>3 2019/10/09 14:23:41;</b><br> partner state unknown-state at <b>3 2019/10/09 14:23:41</b>;<br>}<br>server-duid "\000\001\000\001%0\251\355\000PV\207D\342";<br>failover peer "dhcp-peer-
workspace1
" state {<br> my state recover at 3 2019/10/09 14:23:41;<br> partner state unknown-state at 3 2019/10/09 14:23:41;<br>}<br> Try shutting down both the primary and secondary servers, remove the "failover peer" stanza----></div><div>Yes I tried this,I shut down the failover and on primary, I removed the failover config part totally from the config file</div><div>Stopped the dhcpd and deleted the lease file and again touch the lease file then restarted the DHCP it worked as expected,</div><div><br></div><div>The moment I bring the failover appliances up and add the failover section to the primary config file and restart the dhcpd on the primary the issue starts.</div><div>First the failover logs says it is in recovery mode ok, So i thought as it has to sync the primary it is in recovery mode. After some span of </div><div>time on the primary appliance lease file I see </div><div>my state partner-down</div><div dir="auto">partner state recovery</div><div>Thus comes the issues, and these are running in for ever condition the status are not getting updated in any of the appliance lease file</div><div> Is it ok if I edit the lease file manually and make it normal ?<br></div><div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 10, 2019 at 9:35 PM Bill Shirley <<a href="mailto:bill@c3po.polymerindustries.biz">bill@c3po.polymerindustries.biz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>I non-failover DHCP server doesn't have any "failover peer"
stanza in the /var/log/dhcpd/dhcpd.leases<br>
file. A working failover lease file has at the top:<br>
<font color="#993300"><tt>failover peer "dhcp-failover" state {</tt><tt><br>
</tt><tt> my state normal at 4 2019/10/10 05:05:04;</tt><tt><br>
</tt><tt> partner state normal at 5 2011/09/02 23:51:25;</tt><tt><br>
</tt><tt>}</tt><tt><br>
</tt></font><br>
Try shutting down both the primary and secondary servers, remove
the "failover peer" stanza from<br>
both of their lease files, and then bring up the primary <b>with
the failover configuration</b>. Ensure it is<br>
handing out leases, then bring up the secondary <b>with the
failover configuration</b>. Then check that<br>
all is working correctly.<br>
<br>
Bill<br>
</p>
<div>On 10/9/2019 1:32 PM, Surya Teja wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">I am facing weird situation with fail over setup
on my lab environment. I am facing issue when the failover dhcp
appliance is added to my existing server.
<div dir="auto">For the first time when i add failover to
primary appliance, On primary appliance lease file i see the
partner state as unknown and in the failover the messages are
printing not responding recovery, so i shutdown the failover
appliance and removed the failover config section from primary
and restarted primary then it was working fine.
<div dir="auto">As a trial of second attempt i increased mclt
value to 3600 and added the failover section back to primary
config and bring up the failover server now.</div>
<div dir="auto">The environment became most problematic none
of the servers are granting leases to devices On the primary
lease file it says </div>
<div dir="auto">my state partner-down</div>
<div dir="auto">peer state recovery
<div dir="auto"><br>
</div>
<div dir="auto">Why do we get these recovery,partner down,
unknown status when i add the failover to my environment?</div>
<div dir="auto">Or do we have any best practice steps how to
add failover to existing server without causing any
outages?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Any help would be appreciated </div>
<div dir="auto">Thanks </div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, 6 Oct 2019, 21:04
Surya Teja, <<a href="mailto:suryateja042@gmail.com" target="_blank">suryateja042@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">Hi Bill Thanks for your reply,
<div dir="auto">Yes I see traffic on the peer ports which i
mentioned in the fail over section of my configuration
file. </div>
<div dir="auto">My mclt value is 1800(30 min).</div>
<div dir="auto">I am seeing these issues on the failover
server and some times I see the logs saying peer hold all
free leases, but that scope is not completely full with
active entries in the dhcpd.lease file of that specified
server</div>
<div dir="auto"><br>
</div>
<div dir="auto">And one more strange thing I observerd in
the lease file. In the file I have statements like my
status and peer status. In that peer status is saying <b>unknown</b> </div>
<div dir="auto">When will this happen? In general scenario
it should be normal that is what i got from internet, but
the state is not getting updated in the lease file.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, 5 Oct 2019, 21:16
Bill Shirley, <<a href="mailto:bill@c3po.polymerindustries.biz" rel="noreferrer" target="_blank">bill@c3po.polymerindustries.biz</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Assuming you're referring to DHCP failover, is there
any traffic flow on the<br>
<font color="#993300">port</font> and <font color="#993300">peer port</font> in the failover
stanza?<br>
<br>
What is your value for <font color="#993300">mclt</font>?<br>
<br>
Which server, primary or secondary, is giving the
recovering message?</p>
<p>Bill<br>
</p>
<div>On 10/5/2019 9:33 AM, Surya Teja wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi I have an issue in the lease flow
with isc dhcp service. In the logs it is printing <b>
<span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif;font-size:13px">eth0:
not responding (recovering) </span></b>
<div><font face="Roboto, Arial, sans-serif" color="#263238">My local is set up with
active-active mode(splt value as 50-50%) and
because of some reason one of the appliance
went down for some duration. </font><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif">I
observed this and i bring it up, and duration of
down is nearly 15hr.</span></div>
<div><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif">After
i bring it up. </span><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif">I
am seeing the logs saying not responding
(recovering). Its been more than two hours still
I am getting the same logs </span></div>
<div><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif">Does
any one have any idea</span><span style="color:rgb(38,50,56);font-family:Roboto,Arial,sans-serif;font-size:13px"> about this
scenario and how to get the environment stable</span></div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
dhcp-users mailing list
<a href="mailto:dhcp-users@lists.isc.org" rel="noreferrer noreferrer" target="_blank">dhcp-users@lists.isc.org</a>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" rel="noreferrer
noreferrer" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote>
</div>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
dhcp-users mailing list
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote></div>