156 lines
7.8 KiB
HTML
156 lines
7.8 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="reference" />
|
||
<meta name="DC.Title" content="Example: Simple DHCP subnet" />
|
||
<meta name="abstract" content="You can learn how to set up the iSeries server as a DHCP server in a simple LAN with four PC clients and a LAN-based printer." />
|
||
<meta name="description" content="You can learn how to set up the iSeries server as a DHCP server in a simple LAN with four PC clients and a LAN-based printer." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakgexampleparent.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakgscenario2.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakgscenario3.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="rzakgscenario1" />
|
||
<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>Example: Simple DHCP subnet</title>
|
||
</head>
|
||
<body id="rzakgscenario1"><a name="rzakgscenario1"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Example: Simple DHCP subnet</h1>
|
||
<div><p>You can learn how to set up the iSeries™ server as a DHCP server in a
|
||
simple LAN with four PC clients and a LAN-based printer.</p>
|
||
<div class="section"><p>The following figure illustrates a simple LAN with a iSeries server,
|
||
four PC clients, and a LAN based printer. In this example, the iSeries server
|
||
acts as a DHCP server for the 10.1.1.0 IP subnet. It is connected to the LAN
|
||
with its 10.1.1.1 interface.</p>
|
||
<div class="fignone"><span class="figcap">Figure 1. Simple LAN setup for iSeries server</span><br /><img src="rzakg501.gif" alt="Simple LAN setup for iSeries server." /><br /></div>
|
||
<p>With so few PC clients, administrators can easily type in each PC's
|
||
IP information statically. They only need to visit four PCs in this case.
|
||
Now imagine that the four PCs became 200 PCs. Setting up each PC's IP information
|
||
now become a time consuming task that might result in accuracy errors too.
|
||
DHCP can simplify the process of assigning IP information to clients. If the
|
||
subnet 10.1.1.0 had hundreds of clients, an administrator only have to create
|
||
a single DHCP policy on the iSeries server. This policy will distribute IP information
|
||
to each client.</p>
|
||
<p>When the PC clients send out their DHCP
|
||
DISCOVER signals, the iSeries server will respond with the appropriate
|
||
IP information. In this example, the company also has a LAN based printer
|
||
that obtains its IP information with DHCP too. But because the PC clients
|
||
depend on the printer's IP address remaining the same, the network administrator
|
||
should account for that in the DHCP policy. One solution will assign a constant
|
||
IP address to the printer. The DHCP server allows you to define a client in
|
||
the DHCP policy like the LAN printer by its MAC address. In the DHCP client
|
||
definition, you can then assign specific values, such as IP addresses and
|
||
router addresses, to the intended client.</p>
|
||
<p>For a client to communicate
|
||
with a TCP/IP network, it requires at least an IP address and subnet mask.
|
||
The clients will get their IP address from the DHCP server, and the DHCP server
|
||
passes additional configuration information (for example, their subnet mask)
|
||
using the configuration options.</p>
|
||
</div>
|
||
<div class="section"><h4 class="sectiontitle">Planning the DHCP setup for a simple LAN</h4>
|
||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Global
|
||
configuration options (applies to all clients served by the DHCP server)</caption><thead align="left"><tr><th valign="top" id="d0e60">Object</th>
|
||
<th valign="top" id="d0e62">Value</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody><tr><td valign="top" headers="d0e60 "><p>Configuration options<br />
|
||
<br />
|
||
option 1: Subnet mask<br />
|
||
option 6: Domain name server<br />
|
||
option 15: Domain name</p>
|
||
</td>
|
||
<td valign="top" headers="d0e62 "> <p><br />
|
||
<br />
|
||
255.255.255.0<br />
|
||
10.1.1.1<br />
|
||
mycompany.com</p>
|
||
</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e60 ">Subnet addresses not assigned by server</td>
|
||
<td valign="top" headers="d0e62 ">10.1.1.1 (Domain name server)</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e60 ">Is the server performing DNS updates?</td>
|
||
<td valign="top" headers="d0e62 ">No</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e60 ">Is the server supporting BOOTP clients?</td>
|
||
<td valign="top" headers="d0e62 ">No</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
|
||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 2. Subnet for PCs</caption><thead align="left"><tr><th valign="top" id="d0e98">Object</th>
|
||
<th valign="top" id="d0e100">Value</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody><tr><td valign="top" headers="d0e98 ">Subnet name</td>
|
||
<td valign="top" headers="d0e100 ">SimpleSubnet</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e98 ">Addresses to manage</td>
|
||
<td valign="top" headers="d0e100 ">10.1.1.2 - 10.1.1.150</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e98 ">Lease time</td>
|
||
<td valign="top" headers="d0e100 ">24 hours (default)</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e98 "><p>Configuration options<br />
|
||
<br />
|
||
Inherited options</p>
|
||
</td>
|
||
<td valign="top" headers="d0e100 "><p><br />
|
||
<br />
|
||
Options from Global configuration</p>
|
||
</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
|
||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 3. Client for Printer</caption><thead align="left"><tr><th valign="top" id="d0e133">Object</th>
|
||
<th valign="top" id="d0e135">Value</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody><tr><td valign="top" headers="d0e133 ">Client Name</td>
|
||
<td valign="top" headers="d0e135 ">LANPrinter</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e133 ">Client Address</td>
|
||
<td valign="top" headers="d0e135 ">10.1.1.5</td>
|
||
</tr>
|
||
<tr><td valign="top" headers="d0e133 "><p>Configuration options <br />
|
||
<br />
|
||
Inherited options</p>
|
||
</td>
|
||
<td valign="top" headers="d0e135 "> <p><br />
|
||
<br />
|
||
Options from Global configuration</p>
|
||
</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgexampleparent.htm" title="By reviewing diagrams and examples of how different networks are set up, you can determine which is the best choice for your installation.">DHCP examples</a></div>
|
||
</div>
|
||
<div class="relref"><strong>Related reference</strong><br />
|
||
<div><a href="rzakgscenario2.htm" title="You can learn how to set up the iSeries server as a DHCP server with two LANs connected by a DHCP-enabled router.">Example: Multiple TCP/IP subnets</a></div>
|
||
<div><a href="rzakgscenario3.htm" title="You can learn how to set up the iSeries server as a DHCP server for a LAN that is connected to the Internet by an Internet router.">Example: DHCP and multihoming</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |