91 lines
5.2 KiB
HTML
91 lines
5.2 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: Configure the iSeries connection to a remote token-ring network through the 6611 Network Processor" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3bridgedtrscenario.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="rzak3bridged6611" />
|
||
|
|
<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: Configure the iSeries connection to a remote token-ring
|
||
|
|
network through the 6611 Network Processor</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak3bridged6611"><a name="rzak3bridged6611"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario details: Configure the iSeries connection to a remote token-ring
|
||
|
|
network through the 6611 Network Processor</h1>
|
||
|
|
<div><div class="section"> <p>Use the following commands to configure the iSeries™ connection
|
||
|
|
to a remote token-ring network through a 6611 Network Processor:</p>
|
||
|
|
<pre>CRTLINTRN<sup>1</sup> LIND(ROUTE6611) RSRCNAME(*NWID) NWI(FRMRLY) +
|
||
|
|
NWIDLCI(33)<sup>2</sup> LINESPEED(*NWI) MAXFRAME(8148)<sup>3</sup> +
|
||
|
|
ADPTADR(400000036760)<sup>4</sup> EXCHID(05636760) +
|
||
|
|
AUTOCRTCTL(*YES)<sup>5</sup> TEXT('DLCI to the 6611')
|
||
|
|
|
||
|
|
ADDTCPIFC<sup>6</sup> INTNETADR('59.1.2.222') LIND(ROUTE6611)
|
||
|
|
|
||
|
|
CRTCTLAPPC CTLD(PC3) LINKTYPE(*LAN) SWTLINLST(ROUTE6611) +
|
||
|
|
RMTNETID(APPN) RMTCPNAME(PC3) ADPTADR(400000051718) +
|
||
|
|
TEXT('PC3 on 6611 Token-ring Network')
|
||
|
|
|
||
|
|
CRTDEVAPPC DEVD(PC3) RMTLOCNAME(PC3) LCLLOCNAME(SYS320) CTL(PC3) +
|
||
|
|
TEXT('PC3 on 6611 Token-ring Network')
|
||
|
|
|
||
|
|
CRTCTLAPPC CTLD(PC4) LINKTYPE(*LAN) SWTLINLST(ROUTE6611) +
|
||
|
|
RMTNETID(APPN) RMTCPNAME(PC4) ADPTADR(400000564318) +
|
||
|
|
TEXT('PC4 on 6611 Token-ring Network')
|
||
|
|
|
||
|
|
CRTDEVAPPC DEVD(PC4) RMTLOCNAME(PC4) LCLLOCNAME(SYS320) CTL(PC4) +
|
||
|
|
TEXT('PC4 on 6611 Token-ring Network')</pre>
|
||
|
|
<div class="note"><span class="notetitle">Notes:</span> <ol><li>By creating a token-ring line (CRTLINTRN), you indicate that the data
|
||
|
|
link connection identifier (DLCI) for which you are configuring connects to
|
||
|
|
a token-ring bridge. The bridge provides RFC 1490 bridging and performs source-route
|
||
|
|
bridging.</li>
|
||
|
|
<li>The DLCI configured for the line must match the DLCI that
|
||
|
|
is supplied by the network provider. At administration time, the network provider
|
||
|
|
must establish a permanent virtual circuit (PVC) connection to the location
|
||
|
|
of the bridge. If you connect more than one bridge, you need to configure
|
||
|
|
multiple DLCIs and token-ring line descriptions.</li>
|
||
|
|
<li>The MAXFRAME values for each line might be different. When selecting values,
|
||
|
|
you must take into account the maximum sizes that the network
|
||
|
|
and bridge support. For information about determining a frame size to configure
|
||
|
|
in your line descriptions, see <a href="rzak3rzak3sizeconsid.htm#rzak3sizeconsid">maximum
|
||
|
|
frame size parameter requirements for frame relay</a>.</li>
|
||
|
|
<li>You must generate an adapter address (ADPTADR) for each line description
|
||
|
|
that you configure for bridging over frame relay. The frame-relay adapter
|
||
|
|
does not have a preset address.</li>
|
||
|
|
<li>Configure AUTOCRTCTL so that any devices that dial in
|
||
|
|
to the iSeries system
|
||
|
|
have controller and device descriptions automatically created.</li>
|
||
|
|
<li>Use the ADDTCPIFC command to define a new interface to the TCP/IP configuration.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<p>This configuration lets you communicate by
|
||
|
|
using either Systems Network Architecture (SNA) or TCP/IP data.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If the 6611 Network Processor passes TCP/IP data from a frame-relay
|
||
|
|
network to a token-ring or Ethernet network, you must ensure that the 6611
|
||
|
|
does not filter data for service access point (SAP) AA. You must turn off
|
||
|
|
filtering for SAP AA on both the frame-relay port and the token-ring or Ethernet
|
||
|
|
port.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak3rzak3bridgedtrscenario.htm">Scenario: Bridged connections to remote token-ring networks</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|