113 lines
6.6 KiB
HTML
113 lines
6.6 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: Bridged connection to an Ethernet network" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3bridgedscenario.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="rzak3bridgedethernetscenario" />
|
||
|
|
<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: Bridged connection to an Ethernet network</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak3bridgedethernetscenario"><a name="rzak3bridgedethernetscenario"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: Bridged connection to an Ethernet network</h1>
|
||
|
|
<div><div class="section"><p>This scenario involves connecting an IBM<sup>®</sup> <span><img src="eserver.gif" alt="eServer" /></span> iSeries™ system
|
||
|
|
to an Ethernet local area network (LAN) using a 6611 Network Processor. The
|
||
|
|
6611 is used as both the frame-relay frame handler and a bridge.</p>
|
||
|
|
<p><a href="#rzak3bridgedethernetscenario__rzak3bridgedethfig">Figure 1</a> shows the
|
||
|
|
configuration of an iSeries system for frame-relay communications with
|
||
|
|
devices on an Ethernet network.</p>
|
||
|
|
<div class="fignone" id="rzak3bridgedethernetscenario__rzak3bridgedethfig"><a name="rzak3bridgedethernetscenario__rzak3bridgedethfig"><!-- --></a><span class="figcap">Figure 1. Bridged
|
||
|
|
configuration to the Ethernet network</span><br /><img src="rzak3508.gif" alt="Bridged configuration to
the Ethernet network" /><br /></div>
|
||
|
|
<p>The Ethernet LAN is connected by using a 6611 bridge
|
||
|
|
and transparent bridging. The bridge is connected to the iSeries system
|
||
|
|
by using a T1 link.</p>
|
||
|
|
<p>As seen in <a href="#rzak3bridgedethernetscenario__rzak3bridgedethfig">Figure 1</a>,
|
||
|
|
there is no frame-relay network in the connection between the iSeries system
|
||
|
|
and the 6611. In this scenario, the iSeries provides the frame handler (FH),
|
||
|
|
or DCE function, and the 6611 bridge is the terminal equipment (TE). Both
|
||
|
|
SNA APPC/APPN and TCP/IP traffic are possible in this configuration.
|
||
|
|
The TCP/IP configuration for line ETHER6611 is done similarly to the way all
|
||
|
|
Ethernet lines are configured for TCP/IP on the iSeries.</p>
|
||
|
|
<p>Use the following commands
|
||
|
|
to configure the iSeries connection
|
||
|
|
to the Ethernet network through a 6611 Network Processor.</p>
|
||
|
|
<pre>CRTNWIFR NWID(FT1) RSRCNAME(LIN231) NRZI(*YES)<sup>1</sup>
|
||
|
|
INTERFACE(*RS449V36)<sup>2</sup> LINESPEED(1536000)<sup>2</sup> +
|
||
|
|
LMIMODE(*FH)<sup>3</sup> +
|
||
|
|
TEXT('Network Interface for T1 link to Ethernet Bridge')
|
||
|
|
|
||
|
|
CRTLINETH<sup>4</sup> LIND(ETHER6611) RSRCNAME(*NWID) NWI(FRT1)
|
||
|
|
NWIDLCI(20)<sup>5</sup> ADPTADR(020000036759)<sup>6</sup> +
|
||
|
|
EXCHID(05636759) LINKSPEED(1536000) AUTOCRTCTL(*YES)<sup>7</sup> +
|
||
|
|
TEXT('DLCI to the 6611 Ethernet LAN')
|
||
|
|
|
||
|
|
ADDTCPIFC<sup>8</sup> INTNETADR('59.1.2.222') LIND(ETHER6611)
|
||
|
|
|
||
|
|
CRTCTLAPPC CTLD(PC5) LINKTYPE(*LAN) SWTLINLST(ETHER6611) +
|
||
|
|
RMTNETID(RPC) RMTCPNAME(PC5) ADPTADR(020000043405) +
|
||
|
|
TEXT('PC5 on 6611 Ethernet Network')
|
||
|
|
|
||
|
|
CRTDEVAPPC DEVD(PC5) RMTLOCNAME(PC5) LCLLOCNAME(SYS320) CTL(PC5) +
|
||
|
|
TEXT('PC5 on 6611 Ethernet Network')
|
||
|
|
|
||
|
|
CRTCTLAPPC CTLD(PC6) LINKTYPE(*LAN) SWTLINLST(ETHERNET6611) +
|
||
|
|
RMTNETID(RPC) RMTCPNAME(PC6) ADPTADR(400000455405) +
|
||
|
|
TEXT('PC6 on 6611 Ethernet Network')
|
||
|
|
|
||
|
|
CRTDEVAPPC DEVD(PC6) RMTLOCNAME(PC6) LCLLOCNAME(SYS320) CTL(PC6) +
|
||
|
|
TEXT('PC6 on 6611 Ethernet Network')</pre>
|
||
|
|
<div class="note"><span class="notetitle">Notes:</span> <ol><li>You must configure NRZI(*YES) when communicating directly with a 6611
|
||
|
|
without a frame-relay network, such as on a T1 link. You must also configure
|
||
|
|
the 6611 to use NRZI.</li>
|
||
|
|
<li>The INTERFACE and LINESPEED parameters must match the characteristics
|
||
|
|
of the T1 line that you use.</li>
|
||
|
|
<li>The local management interface (LMI) mode is *FH, which means the iSeries acts
|
||
|
|
as the frame handler and the 6611 acts as the terminal equipment (TE). LMI
|
||
|
|
is exchanged on data link connection identifier 0 (DLCI 0).</li>
|
||
|
|
<li>By creating an Ethernet line (CRTLINETH), you are indicating that the
|
||
|
|
DLCI connects to an Ethernet bridge. The Ethernet bridge carries out RFC 1490
|
||
|
|
bridging and performs transparent bridging.</li>
|
||
|
|
<li>The iSeries system
|
||
|
|
communicates with the 6611 bridge on DLCI 20. <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>
|
||
|
|
</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 the Automatically Create Controller Description (AUTOCRTCTL)
|
||
|
|
command so that any devices that dial in to the iSeries have controller and device descriptions
|
||
|
|
automatically created.</li>
|
||
|
|
<li>Use the Add TCP/IP Interface (ADDTCPIFC) command to define a new interface
|
||
|
|
to the TCP/IP configuration.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<p>Use this configuration to communicate by using either SNA
|
||
|
|
or TCP/IP data.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak3rzak3bridgedscenario.htm" title="This topic provides example scenarios of bridged configurations.">Scenarios: Bridged configuration for frame relay</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|