180 lines
11 KiB
HTML
180 lines
11 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: DHCP and PPP profile on different iSeries servers" />
|
|
<meta name="abstract" content="You can learn how to set up two iSeries servers as the network DHCP server and a DHCP/BOOTP relay agent for two LANs and remote dial-in clients." />
|
|
<meta name="description" content="You can learn how to set up two iSeries servers as the network DHCP server and a DHCP/BOOTP relay agent for two LANs and remote dial-in clients." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyscenarios.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzakgscenario6" />
|
|
<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: DHCP and PPP profile on different iSeries servers</title>
|
|
</head>
|
|
<body id="rzakgscenario6"><a name="rzakgscenario6"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Example: DHCP and PPP profile on different iSeries servers</h1>
|
|
<div><p>You can learn how to set up two iSeries™ servers as the network DHCP server
|
|
and a DHCP/BOOTP relay agent for two LANs and remote dial-in clients.</p>
|
|
<div class="section"><p>The previous example, PPP and DHCP on a single iSeries server,
|
|
shows how to use PPP and DHCP on a single iSeries server to permit dial-in clients
|
|
access to a network. Whether it is the physical layout of your network or
|
|
security concerns, it might be more desirable to have the PPP and DHCP servers
|
|
separated or to have a dedicated PPP server without DHCP services. The following
|
|
figure represents a network that has dial-in clients but the PPP and DHCP
|
|
policies are on different servers.</p>
|
|
<div class="fignone"><span class="figcap">Figure 1. DHCP and PPP profile on
|
|
different iSeries servers</span><br /><img src="rzakg506.gif" alt="DHCP and PPP profile on different iSeries servers." /><br /></div>
|
|
<p>The Remote Data Entry clients dial into the iSeries PPP server. The PPP profile on
|
|
that server must have a remote IP address method of DHCP like in the previous
|
|
example as well as IP Forwarding in the PPP profile and the TCP/IP stack properties.
|
|
Furthermore, because this server is acting as a DHCP relay agent, the BOOTP/DHCP
|
|
relay agent TCP/IP server must be on. This allows the iSeries Remote Access server to pass
|
|
on DHCP DISCOVER packets to the DHCP server. The DHCP server will then respond
|
|
and distribute TCP/IP information to the dial-in clients through the PPP server.</p>
|
|
<p>The
|
|
DHCP server is responsible for distributing IP addresses to both the 10.1.1.0
|
|
and 10.1.2.0 networks. In the Data Entry network, it will give out IP addresses
|
|
from 10.1.2.10 to 10.1.2.40 to either dial-in or directly-attached network
|
|
clients. The data entry clients also need a router address (option 3) of 10.1.2.1
|
|
to communicate with the Work network and the iSeries DHCP server must also have IP
|
|
forwarding enabled.</p>
|
|
<p>Also, the Local Interface IP address in the PPP
|
|
profile must be an IP address that falls within the subnet definition in the
|
|
DHCP server. In this example, the PPP profile Local Interface address should
|
|
be 10.1.2.2. This address should also be excluded from the DHCP server's address
|
|
pool so that it is not assigned to a DHCP client. The Local Interface IP address
|
|
must be an address to which the DHCP server can send reply packets to.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Planning the DHCP setup for DHCP with a DHCP relay agent</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="d0e61">Object</th>
|
|
<th valign="top" width="43.95973154362416%" id="d0e63">Value</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td rowspan="3" valign="top" width="12.416107382550337%" headers="d0e61 ">Configuration options </td>
|
|
<td valign="top" width="43.624161073825505%" headers="d0e61 ">option 1: Subnet mask </td>
|
|
<td valign="top" width="43.95973154362416%" headers="d0e63 ">255.255.255.0 </td>
|
|
</tr>
|
|
<tr><td valign="top" width="43.624161073825505%" headers="d0e61 ">option 6: Domain name server </td>
|
|
<td valign="top" width="43.95973154362416%" headers="d0e63 ">10.1.1.1 </td>
|
|
</tr>
|
|
<tr><td valign="top" width="43.624161073825505%" headers="d0e61 ">option 15: Domain name</td>
|
|
<td valign="top" width="43.95973154362416%" headers="d0e63 ">mycompany.com </td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e61 ">Is the server performing DNS updates?</td>
|
|
<td valign="top" width="43.95973154362416%" headers="d0e63 ">No</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e61 ">Is the server supporting BOOTP clients?</td>
|
|
<td valign="top" width="43.95973154362416%" headers="d0e63 ">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 Work Network</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e102">Object</th>
|
|
<th valign="top" width="44.25675675675676%" id="d0e104">Value</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td colspan="2" valign="top" headers="d0e102 ">Subnet name</td>
|
|
<td valign="top" width="44.25675675675676%" headers="d0e104 ">WorkNetwork</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e102 ">Addresses to manage</td>
|
|
<td valign="top" width="44.25675675675676%" headers="d0e104 ">10.1.1.3 - 10.1.1.150</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e102 ">Lease time</td>
|
|
<td valign="top" width="44.25675675675676%" headers="d0e104 ">24 hours (default)</td>
|
|
</tr>
|
|
<tr><td valign="top" width="12.162162162162163%" headers="d0e102 ">Configuration options </td>
|
|
<td valign="top" width="43.58108108108108%" headers="d0e102 ">Inherited options</td>
|
|
<td valign="top" width="44.25675675675676%" headers="d0e104 ">Options from Global configuration</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e102 ">Subnet addresses not assigned by server</td>
|
|
<td valign="top" width="44.25675675675676%" headers="d0e104 ">none</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 Network</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e143">Object</th>
|
|
<th valign="top" width="44.41624365482234%" id="d0e145">Value</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td colspan="2" valign="top" headers="d0e143 ">Subnet Name</td>
|
|
<td valign="top" width="44.41624365482234%" headers="d0e145 ">DataEntry</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e143 ">Addresses to manage</td>
|
|
<td valign="top" width="44.41624365482234%" headers="d0e145 ">10.1.2.10 - 10.1.2.40</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e143 ">Lease time</td>
|
|
<td valign="top" width="44.41624365482234%" headers="d0e145 ">24 hours (default)</td>
|
|
</tr>
|
|
<tr><td rowspan="2" valign="top" width="11.928934010152284%" headers="d0e143 ">Configuration options </td>
|
|
<td valign="top" width="43.65482233502538%" headers="d0e143 ">option 3: Router </td>
|
|
<td valign="top" width="44.41624365482234%" headers="d0e145 ">10.1.2.1 </td>
|
|
</tr>
|
|
<tr><td valign="top" width="43.65482233502538%" headers="d0e143 ">Inherited options</td>
|
|
<td valign="top" width="44.41624365482234%" headers="d0e145 ">Options from Global configuration</td>
|
|
</tr>
|
|
<tr><td colspan="2" valign="top" headers="d0e143 ">Subnet addresses not assigned by server</td>
|
|
<td valign="top" width="44.41624365482234%" headers="d0e145 "><p>10.1.2.1 (Router)<br />
|
|
10.1.2.15 (Remote Data Entry client's local interface IP address)<br />
|
|
10.1.2.14 (Remote Data Entry client's local interface IP address)</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Other setup on the iSeries server running PPP</h4><ul><li>Set up the BOOTP/DHCP relay agent TCP/IP server
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="90%" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="55.778894472361806%" id="d0e196">Object</th>
|
|
<th valign="top" width="44.221105527638194%" id="d0e198">Value</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="55.778894472361806%" headers="d0e196 ">Interface address</td>
|
|
<td valign="top" width="44.221105527638194%" headers="d0e198 ">10.1.2.2</td>
|
|
</tr>
|
|
<tr><td valign="top" width="55.778894472361806%" headers="d0e196 ">Relay packets to Server IP address</td>
|
|
<td valign="top" width="44.221105527638194%" headers="d0e198 ">10.1.2.1</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</li>
|
|
<li>Set the Remote IP address method to DHCP in the PPP receiver connection
|
|
profile <ol><li>Enable DHCP WAN client connection with a DHCP server or relay connection
|
|
using the Services menu item for Remote Access Services in iSeries Navigator</li>
|
|
<li>Select to Use DHCP for the IP address assignment method under the TCP/IP
|
|
Settings Properties of the Receiver Connection Profile in iSeries Navigator</li>
|
|
</ol>
|
|
</li>
|
|
<li>Allow remote system to access other networks (IP forwarding) under the
|
|
TCP/IP Settings Properties of the Receiver Connection Profile in iSeries Navigator
|
|
(to allow the remote clients to communicate with the Data Entry Network)</li>
|
|
<li>Enable IP datagram forwarding under the Settings Properties of the TCP/IP
|
|
Configuration in iSeries Navigator
|
|
(to allow the remote clients to communicate with the Data Entry Network)</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiyscenarios.htm" title="The scenarios in this topic help you understand how PPP works, and how you can implement a PPP environment in your network. These scenarios introduce fundamental PPP concepts from which beginners and experienced users can benefit before they proceed to the planning and configuration tasks.">Scenarios</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |