92 lines
6.3 KiB
HTML
92 lines
6.3 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="task" />
|
||
|
|
<meta name="DC.Title" content="Step 2: Configure a L2TP originator profile on 10.1.1.74" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyscenariodetails.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyscenariodetailsterminator.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyscenariodetailsremote2.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="rzaiyscenariodetailsremote" />
|
||
|
|
<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>Step 2: Configure a L2TP originator profile on 10.1.1.74</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiyscenariodetailsremote"><a name="rzaiyscenariodetailsremote"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Step 2: Configure a L2TP originator profile on 10.1.1.74</h1>
|
||
|
|
<div><div class="section"><p>Follow these steps to create a L2TP originator profile:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>In iSeries™ Navigator,
|
||
|
|
expand <span class="menucascade"><span class="uicontrol">10.1.1.74</span> > <span class="uicontrol">Network</span> > <span class="uicontrol">Remote Access Services</span></span>.</span></li>
|
||
|
|
<li class="stepexpand"><span>Right-click <span class="uicontrol">Originator Connection Profiles</span>,
|
||
|
|
and select <span class="uicontrol">New Profile</span>.</span></li>
|
||
|
|
<li class="stepexpand"><span>Select the following options on the Setup page and click <span class="uicontrol">OK</span>: </span><ul><li><strong>Protocol type</strong>: PPP</li>
|
||
|
|
<li><strong>Connection type</strong>: L2TP (virtual line)</li>
|
||
|
|
<li><strong>Operating mode</strong>: Remote dial</li>
|
||
|
|
<li><strong>Type of line service</strong>: Single line</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>On the <span class="uicontrol">General</span> tab, complete the following
|
||
|
|
fields: </span><ul><li><strong>Name</strong>: toModem</li>
|
||
|
|
<li><strong>Description</strong>: originator connection going to partition owning
|
||
|
|
modem</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>On the <span class="uicontrol">Connection</span> tab, complete the following
|
||
|
|
fields: </span> <p><strong>Virtual line name</strong>: toModemThis line has no associated
|
||
|
|
physical interface. The virtual line describes various characteristics of
|
||
|
|
this PPP profile. The L2TP Line Properties window opens.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>On the <span class="uicontrol">General</span> tab, enter a description
|
||
|
|
for the virtual line.</span></li>
|
||
|
|
<li class="stepexpand"><span>On the <span class="uicontrol">Authentication</span> tab, enter the local
|
||
|
|
host name of the partition and click <span class="uicontrol">OK</span> to return to
|
||
|
|
the Connection page.</span></li>
|
||
|
|
<li class="stepexpand"><span>In the <strong>Remote telephone numbers</strong> field, add <kbd class="userinput">*PRIMARY</kbd> and <kbd class="userinput">*BACKUP</kbd>.
|
||
|
|
This allows the profile to use the same telephone numbers as the terminator
|
||
|
|
profile on the partition owning the modems.</span></li>
|
||
|
|
<li class="stepexpand"><span>In the <span class="uicontrol">Remote tunnel endpoint host name or IP address</span> field,
|
||
|
|
enter the remote tunnel endpoint IP address (<kbd class="userinput">10.1.1.73</kbd>).</span></li>
|
||
|
|
<li class="stepexpand"><span>On the <span class="uicontrol">Authentication</span> tab, select <span class="uicontrol">Allow
|
||
|
|
the remote system to verify the identity of this iSeries server</span>.</span></li>
|
||
|
|
<li class="stepexpand"><span>Under Authentication protocol to use, select <span class="uicontrol">Require
|
||
|
|
encrypted password (CHAP-MD5)</span>. By default, <span class="uicontrol">Allow extensible
|
||
|
|
authentication protocol</span> is also selected.</span> <div class="note"><span class="notetitle">Note:</span> The
|
||
|
|
protocol should match whatever protocol the server you are dialing also uses. </div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Enter your user name and password.</span> <div class="note"><span class="notetitle">Note:</span> The user name
|
||
|
|
and password needs to match whatever user name and password is valid on the
|
||
|
|
server to which you are dialing.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Go to the <span class="uicontrol">TCP/IP Settings</span> tab and verify
|
||
|
|
the required fields: </span><ul><li><strong>Local IP address</strong>: Assigned by remote system</li>
|
||
|
|
<li><strong>Remote IP address</strong>: Assigned by remote system</li>
|
||
|
|
<li><strong>Routing</strong>: No additional routing is required</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to save the PPP profile.</span></li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiyscenariodetails.htm" title="After you complete the prerequisites, you are ready to begin configuring the L2TP profiles.">Scenario details: Share a modem between logical partitions using L2TP</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzaiyscenariodetailsterminator.htm">Step 1: Configure L2TP terminator profile for any interface on the partition, which owns the modems</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzaiyscenariodetailsremote2.htm">Step 3: Configure a L2TP remote dial profile for 192.168.1.2</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|