115 lines
7.3 KiB
HTML
115 lines
7.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="reference" />
|
||
|
|
<meta name="DC.Title" content="Multiple-connection profile support" />
|
||
|
|
<meta name="abstract" content="Point-to-point connection profiles that support multiple connections allow you to have one connection profile that handles many digital, analog, or L2TP calls." />
|
||
|
|
<meta name="description" content="Point-to-point connection profiles that support multiple connections allow you to have one connection profile that handles many digital, analog, or L2TP calls." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiylinkcfg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyremotepool.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="rzaiymultcon" />
|
||
|
|
<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>Multiple-connection profile support</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiymultcon"><a name="rzaiymultcon"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Multiple-connection profile support</h1>
|
||
|
|
<div><p>Point-to-point connection profiles that support multiple connections
|
||
|
|
allow you to have one connection profile that handles many digital, analog,
|
||
|
|
or L2TP calls.</p>
|
||
|
|
<div class="section"><p>This is useful when you want multiple users to connect to your iSeries™ server
|
||
|
|
but do not want to specify a separate point-to-point connection profile to
|
||
|
|
handle each PPP line. This feature is especially useful for the 2805 4-port
|
||
|
|
integrated modem where four lines are for use from one adapter. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>For analog lines with multiple-connection profile support, all
|
||
|
|
lines in the specified line pool are used up to the maximum number of connections.
|
||
|
|
Basically, a separate connection profile job is started for each line that
|
||
|
|
is defined in the line pool. All connection profile jobs wait for incoming
|
||
|
|
calls on their respective lines.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Local IP address for multiple-connection profiles:</h4><p>You
|
||
|
|
can use the local IP address with multiple-connection profiles, but it must
|
||
|
|
be an existing IP address that is defined on your iSeries server. You can use the Local
|
||
|
|
IP address pull down list to select the existing IP address. Remote users
|
||
|
|
can access the resources that are on your local network if you choose the
|
||
|
|
local iSeries server
|
||
|
|
IP address as the local IP address for your PPP profile. Also, you must define
|
||
|
|
the IP addresses that are in the remote IP address pool to be in the same
|
||
|
|
network as the local IP address.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>If you do not have a local iSeries server IP address or do not want
|
||
|
|
the remote users to access the LAN, you must define a virtual IP address for
|
||
|
|
your iSeries server.
|
||
|
|
A Virtual IP address is also known as a circuitless interface. Your point-to-point
|
||
|
|
profiles can use this IP address as their local IP address. Since this IP
|
||
|
|
address is not tied to a physical network, it will not automatically forward
|
||
|
|
traffic to other networks that are attached to your iSeries server.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>To create a Virtual IP address, follow these steps:</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"> <ol><li>In iSeries Navigator,
|
||
|
|
expand your server, and access <span class="menucascade"><span class="uicontrol">Network</span> > <span class="uicontrol">TCP/IP configuration</span> > <span class="uicontrol">IPV4</span> > <span class="uicontrol">Interfaces</span></span>.</li>
|
||
|
|
<li>Right-click <span class="uicontrol">Interfaces</span> and select <span class="menucascade"><span class="uicontrol">New Interface</span> > <span class="uicontrol">Virtual IP</span></span>.</li>
|
||
|
|
<li>Follow the Interface Wizard instructions to create your Virtual IP interface.
|
||
|
|
Your point-to-point connection profiles can use the Virtual IP address once
|
||
|
|
it is created. You can use the pull down list from the Local IP address field
|
||
|
|
that is on the TCP/IP Settings page to use the IP address with your profile. <div class="note"><span class="notetitle">Note:</span> The
|
||
|
|
Virtual IP address must be active prior to starting your multiple-connection
|
||
|
|
profile; otherwise, the profile will not start. To activate the IP address
|
||
|
|
after creating the interface, you select the option to start the IP address
|
||
|
|
when using the Interface Wizard. </div>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Remote IP address pools for multiple-connection profiles:</h4><p>You
|
||
|
|
can also use remote IP address pools with multiple-connection profiles. A
|
||
|
|
typical one-connection point-to-point profile only allows you to specify one
|
||
|
|
remote IP address, which is given to the calling system when the connection
|
||
|
|
is made. Because multiple callers can now connect simultaneously, a remote
|
||
|
|
IP address pool is used to define a starting remote IP address as well as
|
||
|
|
a range of additional IP addresses that are given to the calling system.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Line pool restrictions:</h4><p>These restrictions apply
|
||
|
|
when using line pools for multiple connections: </p>
|
||
|
|
<ul><li>A specific line can only exist in one line pool at a time. If you remove
|
||
|
|
a line from a line pool, it can be used in another line pool.</li>
|
||
|
|
<li>When starting a multiple connection profile that uses a line pool, all
|
||
|
|
lines in the line pool are used up to the maximum number of connections value
|
||
|
|
in the profile. When there are no lines, all new connections will fail. Also,
|
||
|
|
if there are no lines in the line pool, and another profile starts, it will
|
||
|
|
end.</li>
|
||
|
|
<li>When you start a single connection profile that has a line pool, the system
|
||
|
|
uses only one line from the line pool. If you start a multiple connection
|
||
|
|
profile that uses the same line pool, any remaining lines in the line pool
|
||
|
|
are for use.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaiyremotepool.htm">Remote IP address pools</a></strong><br />
|
||
|
|
The system can use remote IP address pools for any answering or stopping point-to-point connection profile that is used with multiple incoming connections.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiylinkcfg.htm" title="Link configuration defines the type of line service that your PPP connection profile uses to establish a connection.">Link configuration</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|