148 lines
9.6 KiB
HTML
148 lines
9.6 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Leases" />
|
||
|
|
<meta name="abstract" content="You can find what DHCP leases are and some questions are provided for you to consider when determining the lease time for your DHCP clients." />
|
||
|
|
<meta name="description" content="You can find what DHCP leases are and some questions are provided for you to consider when determining the lease time for your DHCP clients." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptinteract.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgplanningdemands.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakgconceptleases" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Leases</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgconceptleases"><a name="rzakgconceptleases"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Leases</h1>
|
||
|
|
<div><p>You can find what DHCP leases are and some questions are provided
|
||
|
|
for you to consider when determining the lease time for your DHCP clients.</p>
|
||
|
|
<p>When DHCP sends configuration information to a client, the information
|
||
|
|
is sent with a lease time. This is the length of time that the client can
|
||
|
|
use the IP address it has been assigned. During the lease time, the DHCP server
|
||
|
|
cannot assign that IP address to any other clients. The purpose of a lease
|
||
|
|
is to limit the length of time that a client can use an IP address. A lease
|
||
|
|
prevents unused clients from taking up IP addresses when there are more clients
|
||
|
|
than addresses. It also allows the administrator to make configuration changes
|
||
|
|
to all of the clients on the network in a limited amount of time. When the
|
||
|
|
lease expires, the client will request a new lease from DHCP. If the configuration
|
||
|
|
data has changed, the new data will be sent to the client at that time.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Lease renewal</h4><p>The client starts
|
||
|
|
to renew a lease when half of the lease time has passed. For example, for
|
||
|
|
a 24 hour lease, the client will attempt to renew the lease after 12 hours.
|
||
|
|
The client requests the renewal by sending a DHCPREQUEST message to the server.
|
||
|
|
The renewal request contains the current IP address and configuration information
|
||
|
|
of the client.</p>
|
||
|
|
<p>If the server accepts the request, it will send an DHCPACK
|
||
|
|
message back to the client. If the server does not respond to the request,
|
||
|
|
the client can continue to use the IP address and configuration information
|
||
|
|
until the lease expires. If the lease is still active, the client
|
||
|
|
and server do not need to go through the DHCPDISCOVER and DHCPREQUEST process.
|
||
|
|
When the lease has expired, the client must start over with the DHCPDISCOVER
|
||
|
|
process.</p>
|
||
|
|
<p>If the server is unreachable, the client can continue to use
|
||
|
|
the assigned address until the lease expires. In the previous example, the
|
||
|
|
client has 12 hours from when it first tries to renew the lease until the
|
||
|
|
lease expires. During a 12-hour outage, new users cannot get new leases, but
|
||
|
|
no leases will expire for any computer turned on at the time that the outage
|
||
|
|
starts.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Determine lease duration</h4><p>The default
|
||
|
|
lease time for the DHCP server is 24 hours. The duration for which you set
|
||
|
|
the lease time on your DHCP server depends on several factors. You will need
|
||
|
|
to consider your goals, your site's usage patterns, and service arrangements
|
||
|
|
for your DHCP server. The following questions can help you to decide on an
|
||
|
|
appropriate lease time:</p>
|
||
|
|
<dl><dt class="dlterm">Do you have more users than addresses?</dt>
|
||
|
|
<dd>If so, the lease time should be short so that clients do not need to wait
|
||
|
|
for unused leases to expire.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Do you have a minimum amount of time that you need to support?</dt>
|
||
|
|
<dd>If your typical user is on for an hour at minimum, that suggests an hour
|
||
|
|
lease at minimum.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">How much DHCP message traffic can your network handle?</dt>
|
||
|
|
<dd>If you have a large number of clients or slow communication lines over
|
||
|
|
which the DHCP packets will run, network traffic might cause problems. The
|
||
|
|
shorter the lease, the higher traffic the server and network load from the
|
||
|
|
renewal request on your network.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">What kind of service plan do you have in place, and to what extent can
|
||
|
|
your network handle an outage?</dt>
|
||
|
|
<dd>Consider any routine maintenance, and the potential impact of an outage.
|
||
|
|
If the lease time is at least double the server outage, then running clients
|
||
|
|
who already have leases will not lose them. If you have a good idea of your
|
||
|
|
longest likely server outage, you can avoid such problems.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">What type of network environment is the DHCP server in? What does a typical
|
||
|
|
client do?</dt>
|
||
|
|
<dd>Consider what the clients do on the network that the DHCP server is servicing.
|
||
|
|
For example, if you have an environment where the clients are primarily mobile,
|
||
|
|
connecting to the network at varying times, typically only once or twice a
|
||
|
|
day to check their e-mail, you might want a relatively short lease time. In
|
||
|
|
this case, it might not be necessary to have a single IP address set aside
|
||
|
|
for each and every client. By limiting the lease time, you can use fewer IP
|
||
|
|
addresses to support the mobile clients.</dd>
|
||
|
|
<dd class="ddexpand">Alternatively, if you have an office environment where most of the employees
|
||
|
|
have primary workstations in a fixed location, a lease time of 24 hours might
|
||
|
|
be more appropriate. It might also be necessary in this environment to have
|
||
|
|
an IP address available for each client that connects to the network during
|
||
|
|
business hours. In this case, if you specify a shorter lease time, the DHCP
|
||
|
|
server negotiates the lease renewal much more frequently with the client,
|
||
|
|
causing excess network traffic.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">How much does your network configuration change?</dt>
|
||
|
|
<dd>If your network topology changes quite frequently, you might want to stay
|
||
|
|
away from longer leases. Long leases can be disadvantageous in cases where
|
||
|
|
you need to change a configuration parameter. The length of the lease can
|
||
|
|
mean the difference between having to go to every affected client and restarting
|
||
|
|
it, or merely waiting a certain amount of time for the leases to be renewed.</dd>
|
||
|
|
<dd class="ddexpand">If your network topology rarely changes and you have enough IP addresses
|
||
|
|
in your address pool, you can configure DHCP to use infinite leases -- leases
|
||
|
|
that never expire. However, infinite leases are not recommended. If you use
|
||
|
|
an infinite lease, the IP address is leased to the client indefinitely. These
|
||
|
|
clients do not need to go through any lease renewal process after they receive
|
||
|
|
the infinite lease. After an infinite lease is assigned to a client, that
|
||
|
|
address cannot be assigned to another client. Therefore, there can be problems
|
||
|
|
with infinite leases if you want to assign that client a new IP address or
|
||
|
|
lease the client's IP address to another client later.</dd>
|
||
|
|
<dd class="ddexpand">You might have clients in your network, such as a file server, that will
|
||
|
|
always receive the same IP address. Rather than using an infinite lease, you
|
||
|
|
should assign a specific address for the client and give it a long lease time.
|
||
|
|
The client still has to lease it for a given amount of time and renew the
|
||
|
|
lease, but the server will reserve the IP address for that client only. Then,
|
||
|
|
if you get a new file server, for example, you can just change the client
|
||
|
|
identifier (MAC address) and the server will give the new file server that
|
||
|
|
same address. If you had given it an infinite lease, then the DHCP server
|
||
|
|
cannot give out the address again unless the lease is explicitly deleted.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgconceptparent.htm" title="DHCP interacts with clients and works in a network.">DHCP concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakgplanningdemands.htm" title="You can plan for most of the DHCP setup by looking at your network topology, the devices on the network (for example, routers), and how you want to support your clients in DHCP.">Network topology considerations</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzakgconceptinteract.htm" title="A client gets the DHCP information from the server, and specific messages are sent between the client and the server. DHCP obtains and returns leases.">DHCP client-server interaction</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|