DHCP restart with bulk lease data
Surya Teja
suryateja042 at gmail.com
Sun Sep 29 10:07:37 UTC 2019
If you mean, does the server stop serving clients while it's doing this,
AFAIK it continues as normal. --->
Yes Simon, I mean this scenario Thanks for that clarification
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.---->
Yes I am running failover. but when the entry is shared from the failover
generally the binding state will be like *backup* right? but here in my
case i see both the entries as
*binding state active;* thus I got a doubt about this duplicate.
On Fri, Sep 27, 2019 at 10:51 PM Simon Hobson <dhcp1 at thehobsons.co.uk>
wrote:
> Surya Teja <suryateja042 at gmail.com> wrote:
> >
> > Hi Simon Thanks for reply,
> > Periodically, default is every hour, the server will write out a fresh
> leases file from it's internal structures --->
> > 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?
>
> The question is a little ambiguous.
> If you mean, will this happen while the server is stopped, no it won't.
> If you mean, does the server stop serving clients while it's doing this,
> AFAIK it continues as normal.
>
> >> this file will contain no duplicate entries --->
> > Hi I have seen the duplicate entry in my server lease file
> > sample snippet:
> > ==============
> > lease 192.168.2.52 {
> > starts 5 2019/09/27 07:21:32;
> > ends 5 2019/09/27 08:21:32;
> > tstp 5 2019/09/27 08:51:32;
> > tsfp 5 2019/09/27 08:21:32;
> > cltt 5 2019/09/27 07:21:32;
> > binding state active;
> > next binding state expired;
> > hardware ethernet 70:bb:e9:37:d9:9e;
> > uid "\001p\273\3517\331\236";
> > set vendor-class-identifier = "android-dhcp-9";
> > client-hostname "RedmiNote6Pro";
> > }
> > lease 192.168.2.52 {
> > starts 5 2019/09/27 07:21:32;
> > ends 5 2019/09/27 08:21:32;
> > tstp 5 2019/09/27 08:51:32;
> > tsfp 5 2019/09/27 08:51:32;
> > atsfp 5 2019/09/27 08:51:32;
> > cltt 5 2019/09/27 07:21:32;
> > binding state active;
> > next binding state expired;
> > hardware ethernet 70:bb:e9:37:d9:9e;
> > uid "\001p\273\3517\331\236";
> > set vendor-class-identifier = "android-dhcp-9";
> > client-hostname "RedmiNote6Pro";
> > }
> > 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 ?
>
> 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.
> 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.
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at 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/20190929/59188aff/attachment.html>
More information about the dhcp-users
mailing list