Re: Understanding the impact of a DHCP server outage

Great. Thanks very much for the response.

--
Hugh


"Jeremy" wrote:

You are correct.

At 50% of the lease time the DHCP client attempts to renew its lease from
the DHCP server that it leased the address from via unicast. If this is not
successful the DHCP client waits until 87.5% of the lease time has expired
and then re-attempts to renew it address, again via unicast to the DHCP
server. If this is unsuccessful the client attempts to obtain a new lease
from any DHCP server via the standard broadcast method (DHCP DISCOVER). If
no DHCP server responds the client falls back (assuming XP) to the alternate
configuration, which is APIPA by default.


"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FD888088-3673-48A9-8E02-289B399F0709@xxxxxxxxxxxxxxxx
We want to make sure we fully understand the impact to DHCP clients
whenever
we have a DHCP server outage. After doing to testing a tracing, it seems
the
breaking point for a DHCP client (at least in our environment) is
controlled
by the value of the Rebinding Time Value parameter in the DHCP Offer
packet.

If my testing was accurate, DHCP clients (Win XP SP2 clients,
specifically)
will continue to use their previously obtained IP address until they reach
the value of the Rebinding Time Value (which is set automatically to 87.5%
of
the lease value). So at 50% of the lease time (set to 14 days in our
environment), the client passes the renewal threshold. However, in my
testing, the client still used its IP address. However, once I reached
the
Rebinding Time Value, the client would send DHCP Discover packets and,
when
no response was received from a DHCP server, the client would then revert
to
an APIPA address.

The conclusion from our testing is that DHCP clients must meet two
criteria
before they will fail to obtain (or use an existing) IP address:

First, prior to or during the failure, the DHCP client exceeds its
Rebinding
Time Value.
Second, during the failure (and after exceeding the Rebinding Time Value),
the DHCP client is restarted.

So my question is simple: Are our conclusions correct? Thanks.
--
Hugh

.

Relevant Pages

  • Re: problem getting freebsd to connect to network
    ... > set up as a DHCP server, and my computers are DHCP enabled. ... By "modem" I am guessing that you mean some kind of cable or DSL router? ... Try enabling maximum debugging in your DHCP client. ... I'm guessing that the DHCP server is doing something non-standard, ...
    (comp.os.linux.networking)
  • Client ip address changed without notice
    ... That is IP lease time. ... DHCP server can I use the IP once again. ... >network connection. ...
    (microsoft.public.win2000.networking)
  • RE: [SLE] yast: how to set up static DHCP addresses
    ... not just set the lease time to, oh, a year or something? ... DHCP server will hand them the one they had before (since that MAC ... I'm not sure that a static config ...
    (SuSE)
  • Re: works on desk computer but not on wireless laptop
    ... RARP server, the DHCP server, or manually? ... So I chose that and now it wants to know the DHCP Client ID. ... And a 12 character number like a Mac ID. ... The OEM computer MAC address is the same as the DHCP ...
    (alt.internet.wireless)
  • Re: HELP ! ipfw et natd
    ... > think you were sent the new IP by your ISP via DHCP. ... Because I need to allow UDP packets, I'll want to specify the DHCP port ... These should be the bare minimum rules that will allow my DHCP client to ... renew its lease with the DHCP server 24.226.1.41. ...
    (comp.unix.bsd.freebsd.misc)