65 lines
4.0 KiB
HTML
65 lines
4.0 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
<meta name="dc.date" scheme="iso8601" content="2005-10-03" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<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))' />
|
||
|
<title>Connection network configuration considerations</title>
|
||
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
</head>
|
||
|
<body>
|
||
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
||
|
|
||
|
<a name="rzahjconf-con"></a>
|
||
|
<h4 id="rzahjconf-con">Connection network configuration considerations</h4>
|
||
|
<p>Following are two examples showing incorrect configuration of a connection
|
||
|
network. The correct configuration of the same example follows: </p>
|
||
|
<ul>
|
||
|
<li>Parallel TGs to the same connection network are not allowed. Only one
|
||
|
LAN line description may be associated with a connection name.
|
||
|
<a name="invc1"></a>
|
||
|
<div class="fignone" id="invc1"><span class="figcap">Figure 1. Incorrect configuration showing parallel TGs to a connection network</span>
|
||
|
<div class="mmobj">
|
||
|
<img src="rv3s128.gif" alt="Incorrect configuration showing parallel TGs to a connection network" /></div></div></li>
|
||
|
<li>There can be only one connection network name that is associated with
|
||
|
a LAN line description at any given time.
|
||
|
<p><img src="delta.gif" alt="Start of change" />One iSeries system (SYSA)
|
||
|
has two LAN line descriptions (with a separate connection network that is
|
||
|
defined on each), and another iSeries system (SYSB) has two connection network
|
||
|
names defined on one LAN line. If SYSA were to request multiple sessions to
|
||
|
SYSB, the first session may go over CN1. Another session initiation request
|
||
|
might choose CN2. However, the destination address is the same, so the second
|
||
|
controller description can not be varied on.<img src="deltaend.gif" alt="End of change" /></p>
|
||
|
<a name="invc2"></a>
|
||
|
<div class="fignone" id="invc2"><span class="figcap">Figure 2. Incorrect configuration showing two connection networks on the same line</span>
|
||
|
<div class="mmobj">
|
||
|
<img src="rv3s129.gif" alt="Incorrect configuration showing two connection networks on the same line" /></div></div></li>
|
||
|
<li>Multiple connection networks (that have different connection network names)
|
||
|
may be defined on separate LAN lines.
|
||
|
<a name="corcn"></a>
|
||
|
<div class="fignone" id="corcn"><span class="figcap">Figure 3. Correct configuration showing two connection networks and two LAN lines</span>
|
||
|
<div class="mmobj">
|
||
|
<img src="rv3s130.gif" alt="Correct configuration with two connection networks and two LAN lines" /></div></div></li></ul>
|
||
|
<a name="wq28"></a>
|
||
|
<div class="notetitle" id="wq28">Note:</div>
|
||
|
<div class="notebody">The name of a virtual node cannot be the same as the control-point
|
||
|
name of any network node, or end node. That is, the CNNNETID and CNNCPNAME
|
||
|
parameters cannot be the same as the RMTNETID and RMTCPNAME parameters in
|
||
|
any controller descriptions in the entire APPN network.</div>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|