<div dir="ltr">If you mean, does the server stop serving clients while it's doing this, AFAIK it continues as normal. ---><div>Yes Simon, I mean this scenario Thanks for that clarification</div><div> Looking at the above, are you running failover ? If so, then I suspect one of the records is from the partner server making an offer to a client at the same time as this server does.----><br></div><div>Yes I am running failover. but when the entry is shared from the failover generally the binding state will be like <b>backup</b> right? but here in my case i see both the entries as </div><div><b>binding state active;</b> thus I got a doubt about this duplicate. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 27, 2019 at 10:51 PM Simon Hobson <<a href="mailto:dhcp1@thehobsons.co.uk">dhcp1@thehobsons.co.uk</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">Surya Teja <<a href="mailto:suryateja042@gmail.com" target="_blank">suryateja042@gmail.com</a>> wrote:<br>
> <br>
> Hi Simon Thanks for reply,<br>
> Periodically, default is every hour, the server will write out a fresh leases file from it's internal structures ---><br>
> I have a doubt when the server write out a fresh leases file from it's internal structures will the dhcpd service be in off state at this duration?<br>
<br>
The question is a little ambiguous.<br>
If you mean, will this happen while the server is stopped, no it won't.<br>
If you mean, does the server stop serving clients while it's doing this, AFAIK it continues as normal.<br>
<br>
>> this file will contain no duplicate entries ---><br>
> Hi I have seen the duplicate entry in my server lease file<br>
> sample snippet:<br>
> ==============<br>
> lease 192.168.2.52 {<br>
> starts 5 2019/09/27 07:21:32;<br>
> ends 5 2019/09/27 08:21:32;<br>
> tstp 5 2019/09/27 08:51:32;<br>
> tsfp 5 2019/09/27 08:21:32;<br>
> cltt 5 2019/09/27 07:21:32;<br>
> binding state active;<br>
> next binding state expired;<br>
> hardware ethernet 70:bb:e9:37:d9:9e;<br>
> uid "\001p\273\3517\331\236";<br>
> set vendor-class-identifier = "android-dhcp-9";<br>
> client-hostname "RedmiNote6Pro";<br>
> }<br>
> lease 192.168.2.52 {<br>
> starts 5 2019/09/27 07:21:32;<br>
> ends 5 2019/09/27 08:21:32;<br>
> tstp 5 2019/09/27 08:51:32;<br>
> tsfp 5 2019/09/27 08:51:32;<br>
> atsfp 5 2019/09/27 08:51:32;<br>
> cltt 5 2019/09/27 07:21:32;<br>
> binding state active;<br>
> next binding state expired;<br>
> hardware ethernet 70:bb:e9:37:d9:9e;<br>
> uid "\001p\273\3517\331\236";<br>
> set vendor-class-identifier = "android-dhcp-9";<br>
> client-hostname "RedmiNote6Pro";<br>
> }<br>
> Yes It has same data, I don't see any issue on client side but want to make sure that, Is this acceptable in lease file ?<br>
<br>
The lease file will be clean **immediately** after it's been re-written. Once clients are served, then new records will be appended and there is likely to be more than one record for some clients.<br>
Looking at the above, are you running failover ? If so, then I suspect one of the records is from the partner server making an offer to a client at the same time as this server does.<br>
<br>
_______________________________________________<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>