68 lines
4.3 KiB
HTML
68 lines
4.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Scenario: SNA direct connection of two iSeries systems" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3snadirscenario.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3minneapolisscenario.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3madisonscenario.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzak3sna2scenario" />
|
||
|
|
<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>Scenario: SNA direct connection of two iSeries systems</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak3sna2scenario"><a name="rzak3sna2scenario"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: SNA direct connection of two iSeries systems</h1>
|
||
|
|
<div><p><a href="#rzak3sna2scenario__rzak3snafig">Figure 1</a> shows
|
||
|
|
a connection between an IBM<sup>®</sup> <span><img src="eserver.gif" alt="eServer" /></span> iSeries™ system
|
||
|
|
in Minneapolis and an IBM <span><img src="eserver.gif" alt="eServer" /></span> iSeries system
|
||
|
|
in Madison over a frame-relay network.</p>
|
||
|
|
<div class="fignone" id="rzak3sna2scenario__rzak3snafig"><a name="rzak3sna2scenario__rzak3snafig"><!-- --></a><span class="figcap">Figure 1. SNA direct connection between Minneapolis and
|
||
|
|
Madison systems</span><br /><img src="rzak3505.gif" alt="SNA direct connection between
Minneapolis and Madison systems" /><br /></div>
|
||
|
|
<p>The two systems have an Advanced Peer-to-Peer Networking
|
||
|
|
(APPN) connection that is configured on the frame-relay data link connection
|
||
|
|
identifier (DLCI). Note that the frame-relay link in Minneapolis has much
|
||
|
|
more traffic and operates at 1 536 000 bps. The link in Madison operates at
|
||
|
|
64 000 bps. The frame-relay network allows for this difference in subscriptions
|
||
|
|
at the two sites.</p>
|
||
|
|
<p>The Minneapolis connection to the network uses DLCI 23.
|
||
|
|
In Madison, the DLCI number is 21. If the connection uses a frame-relay network,
|
||
|
|
the DLCI numbers have only local (terminal end (TE) to frame handler (FH))
|
||
|
|
significance and might be different on the two interfaces. The network is
|
||
|
|
responsible for setting up the connection between the DLCIs at administration
|
||
|
|
time.</p>
|
||
|
|
<p>If you require more than one Advanced Program-to-Program
|
||
|
|
Communication (APPC) connection between the two sites, you must define additional
|
||
|
|
source service access point (SSAP) and destination service access point (DSAP)
|
||
|
|
values on the lines, and the additional controllers need different SSAP and
|
||
|
|
DSAP combinations.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3minneapolisscenario.htm">Scenario details: Configuration for the iSeries system in Minneapolis</a></strong><br />
|
||
|
|
</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3madisonscenario.htm">Scenario details: Configuration for the iSeries system in Madison</a></strong><br />
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak3rzak3snadirscenario.htm" title="This topic provides example scenarios of Systems Network Architecture (SNA) direct configuration.">Scenarios: SNA direct configuration for frame relay</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|