72 lines
4.7 KiB
HTML
72 lines
4.7 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="BOOTP" />
|
||
|
|
<meta name="abstract" content="This topic describes what BOOTP is, and gives some history about BOOTP and DHCP." />
|
||
|
|
<meta name="description" content="This topic describes what BOOTP is, and gives some history about BOOTP and DHCP." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptsupport.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzal4/rzal4overview.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="rzakgconceptbootp" />
|
||
|
|
<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>BOOTP</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgconceptbootp"><a name="rzakgconceptbootp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">BOOTP</h1>
|
||
|
|
<div><p>This topic describes what BOOTP is, and gives some history about
|
||
|
|
BOOTP and DHCP.</p>
|
||
|
|
<p>The Bootstrap protocol (BOOTP) is a host configuration protocol that was
|
||
|
|
used before DHCP was developed. BOOTP support is a slimmed down version of
|
||
|
|
DHCP. In BOOTP, clients are identified by their MAC address and are assigned
|
||
|
|
a specific IP address. Essentially, each client in your network is mapped
|
||
|
|
to an IP address. There is no dynamic address assignment, each network client
|
||
|
|
must be identified in the BOOTP configuration, and the clients can only receive
|
||
|
|
a limited amount of configuration information from the BOOTP server.</p>
|
||
|
|
<p>Because DHCP is based on BOOTP, the DHCP server can support BOOTP clients.
|
||
|
|
If you are currently using BOOTP, you can set up and use DHCP
|
||
|
|
without any impacts to your BOOTP clients. To support BOOTP clients successfully,
|
||
|
|
you must specify the IP address of the bootstrap server and the boot file
|
||
|
|
name option (option 67), and BOOTP support must be turned on for the entire
|
||
|
|
server or various subnets.</p>
|
||
|
|
<p>Using DHCP to support BOOTP clients is preferred over using a BOOTP server.
|
||
|
|
Even when you use DHCP to support your BOOTP clients, each BOOTP client is
|
||
|
|
essentially being mapped to a single IP address, and that address is therefore
|
||
|
|
not re-usable by another client. The advantage, however, of using DHCP in
|
||
|
|
this case is that there is no need to configure a one-to-one mapping of BOOTP
|
||
|
|
clients to IP addresses. The DHCP server will still dynamically assign an
|
||
|
|
IP addresses to the BOOTP client from the address pool. After the IP address
|
||
|
|
is assigned to the BOOTP client, it is permanently reserved for use by that
|
||
|
|
client until you explicitly delete the address reservation. Eventually, you
|
||
|
|
might want to consider converting your BOOTP clients to DHCP for easier host
|
||
|
|
configuration management.</p>
|
||
|
|
</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="rzakgconceptsupport.htm" title="Using DHCP, you can manage each client in your network individually, rather than managing all of the clients as a large group (subnet).">DHCP client support</a></div>
|
||
|
|
<div><a href="../rzal4/rzal4overview.htm">BOOTP</a></div>
|
||
|
|
<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>
|
||
|
|
</body>
|
||
|
|
</html>
|