|
DHCP Lease Renewal and Rebinding Processes
(Page 3 of 3)
The Purpose of the Two-Step Rebinding/Renewal Process
One valid question is: why bother
with a two-step process, rebinding and renewal? The reason is that this
provides the best blend of efficiency and flexibility. We first try
to contact the server that granted the lease using a unicast request,
to avoid taking up the time of other DHCP servers and disrupting the
network as a whole with broadcast traffic. Usually this will work, because
DHCP servers don't change that often and are usually left on continuously.
If that fails, we then fall back on the broadcast, giving other servers
a chance to take over the client’s existing lease.
 Key Concept: Each client’s lease has associated with it a renewal timer (T1), normally set to 50% of the length of the lease, and a rebinding timer (T2), usually 87.5% of the lease length. When the T1 timer goes off the client will try to renew its lease by contacting the server that originally granted it. If the client cannot renew the lease by the time the T2 timer expires, it will broadcast a rebinding request to any available server. If the lease is not renewed or rebound by the time the lease expires, the client must start the lease allocation process over again.
|
| If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|
