63 lines
3.9 KiB
HTML
63 lines
3.9 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="Scenario details: Configuration for the iSeries system in Minneapolis" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3sna2scenario.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="rzak3minneapolisscenario" />
|
||
|
|
<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 details: Configuration for the iSeries system in Minneapolis</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak3minneapolisscenario"><a name="rzak3minneapolisscenario"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario details: Configuration for the iSeries™ system in Minneapolis</h1>
|
||
|
|
<div><div class="section"> <p>Use the prompt display for the Create Network
|
||
|
|
Interface (Frame Relay) (CRTNWIFR) command to create the network
|
||
|
|
interface (NWI) description on the Minneapolis system. The INTERFACE and LINESPEED
|
||
|
|
parameter values must match the network subscription, and you must specify
|
||
|
|
a LMIMODE value when communicating over a frame-relay network. The LMIMODE
|
||
|
|
value must match the network subscription and can be *TE, *ANNEXA, or *NONE.
|
||
|
|
The local management interface (LMI) uses data link connection identifier
|
||
|
|
0 (DLCI 0) for both *ANNEXA and *TE, but it does not use a DLCI for *NONE.</p>
|
||
|
|
<p>Use the prompt display for the Create Line Description (Frame
|
||
|
|
Relay) (CRTLINFR) command to create the frame-relay line description on the
|
||
|
|
Minneapolis system. The DLCI that you specify for the line must match the
|
||
|
|
network subscription. Because frame-relay Systems Network Architecture (SNA)
|
||
|
|
direct addressing requires 10 bytes of overhead, a frame size of 1590 is configured
|
||
|
|
for the MAXFRAME parameter. In other words, you need to use a frame size that
|
||
|
|
is at least 10 bytes less than the network subscription. You also need to
|
||
|
|
know the frame size at the other side of the network. For example, if one
|
||
|
|
side is 1600 and the other is 2100, then both sides need to be set to 1600.</p>
|
||
|
|
<p>Use
|
||
|
|
the prompt display for the Create Controller Description (APPC) (CRTCTLAPPC)
|
||
|
|
command to create the APPC controller description on the Minneapolis system.
|
||
|
|
You must specify LINKTYPE(*FR) for SNA direct connections.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The default
|
||
|
|
values for SSAP and DSAP are both 04. These values must match the values specified
|
||
|
|
for the remote system. If you create more controllers using the same line
|
||
|
|
description (DLCI), you must specify a unique SSAP and DSAP pair. This might
|
||
|
|
require you to configure more SAPs on the frame-relay line description.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak3rzak3sna2scenario.htm">Scenario: SNA direct connection of two iSeries systems</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|