147 lines
8.8 KiB
HTML
147 lines
8.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: Multiple TCP/IP subnets" />
|
||
|
|
<meta name="abstract" content="You can learn how to set up the iSeries server as a DHCP server with two LANs connected by a DHCP-enabled router." />
|
||
|
|
<meta name="description" content="You can learn how to set up the iSeries server as a DHCP server with two LANs connected by a DHCP-enabled router." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgexampleparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgscenario1.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="rzakgscenario2" />
|
||
|
|
<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: Multiple TCP/IP subnets</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgscenario2"><a name="rzakgscenario2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Multiple TCP/IP subnets</h1>
|
||
|
|
<div><p>You can learn how to set up the iSeries™ server as a DHCP server with
|
||
|
|
two LANs connected by a DHCP-enabled router.</p>
|
||
|
|
<div class="section"><p>This example is similar to the previous example, Simple DHCP subnet,
|
||
|
|
except that there is now an additional TCP/IP subnet. Suppose that the office
|
||
|
|
and data entry clients are on different floors of a office building and separated
|
||
|
|
with a router. If the network administrator wants all of the clients to receive
|
||
|
|
their IP information through DHCP, this situation presents some unique differences
|
||
|
|
from a simple DHCP subnet. The following figure shows an example network layout
|
||
|
|
for an iSeries DHCP
|
||
|
|
server connected to two LANs using a router between the networks. The figure
|
||
|
|
intentionally has a limited number of clients as not to become cluttered.
|
||
|
|
A real world situation has considerably more clients on each subnet.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. Multiple LANs connected through a router</span><br /><img src="rzakg502.gif" alt="Multiple LANs connected through a router." /><br /></div>
|
||
|
|
<p>The router that connects the two networks must be enabled to pass
|
||
|
|
DHCP DISCOVER packets. If it is not, the data entry clients will not be able
|
||
|
|
to receive their IP information and access the network. Also, the DHCP policy
|
||
|
|
needs two subnet definitions--one for the data entry and office subnets. At
|
||
|
|
a minimum, the differences between the subnets are their IP subnets and router
|
||
|
|
addresses. The data entry subnet needs to receive a router address of 10.1.2.2
|
||
|
|
to communicate with the office subnet.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Planning the DHCP setup for multiple LANs</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" 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 colspan="2" valign="top" id="d0e42">Object</th>
|
||
|
|
<th valign="top" width="43.389830508474574%" id="d0e44">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td rowspan="3" valign="top" width="13.220338983050848%" headers="d0e42 ">Configuration options </td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e42 "> option 1: Subnet mask </td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e44 "> 255.255.255.0 </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.389830508474574%" headers="d0e42 "> option 6: Domain name server </td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e44 "> 10.1.1.1 </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.389830508474574%" headers="d0e42 "> option 15: Domain name</td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e44 "> mycompany.com </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e42 ">Subnet addresses not assigned by server</td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e44 ">10.1.1.1 (Domain name server)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e42 ">Is the server performing DNS updates?</td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e44 ">No</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e42 ">Is the server supporting BOOTP clients?</td>
|
||
|
|
<td valign="top" width="43.389830508474574%" headers="d0e44 ">No</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 2. Subnet for Office clients</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e88">Object</th>
|
||
|
|
<th valign="top" width="43.09764309764309%" id="d0e90">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td colspan="2" valign="top" headers="d0e88 ">Subnet name</td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e90 ">Office</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e88 ">Addresses to manage</td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e90 ">10.1.1.3 - 10.1.1.150</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e88 ">Lease time</td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e90 ">24 hours (default)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td rowspan="2" valign="top" width="13.804713804713806%" headers="d0e88 ">Configuration options </td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e88 ">option 3: Router </td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e90 ">10.1.1.2 </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.09764309764309%" headers="d0e88 ">inherited options</td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e90 ">Options from Global configuration </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e88 ">Subnet addresses not assigned by server</td>
|
||
|
|
<td valign="top" width="43.09764309764309%" headers="d0e90 ">10.1.1.2 (Router)</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 3. Subnet for Data Entry clients</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e134">Object</th>
|
||
|
|
<th valign="top" width="42.95302013422819%" id="d0e136">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td colspan="2" valign="top" headers="d0e134 ">Subnet name</td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e136 ">DataEntry</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e134 ">Addresses to manage</td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e136 ">10.1.2.3 - 10.1.2.150</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e134 ">Lease time</td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e136 ">24 hours (default)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td rowspan="2" valign="top" width="14.093959731543624%" headers="d0e134 ">Configuration options </td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e134 ">option 3: Router </td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e136 ">10.1.2.2</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="42.95302013422819%" headers="d0e134 ">Inherited options</td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e136 ">Options from Global configuration</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e134 ">Subnet addresses not assigned
|
||
|
|
by server</td>
|
||
|
|
<td valign="top" width="42.95302013422819%" headers="d0e136 ">10.1.2.2 (Router)</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="rzakgscenario1.htm" title="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.">Example: Simple DHCP subnet</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|