65 lines
4.4 KiB
HTML
65 lines
4.4 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="Network connections for frame relay" />
|
||
|
|
<meta name="abstract" content="The IBM eServer iSeries system provides support for direct and bridged frame-relay network connections." />
|
||
|
|
<meta name="description" content="The IBM eServer iSeries system provides support for direct and bridged frame-relay network connections." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3overview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3bridged.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="rzak3frnetconfig" />
|
||
|
|
<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>Network connections for frame relay</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak3frnetconfig"><a name="rzak3frnetconfig"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Network connections for frame relay</h1>
|
||
|
|
<div><p>The IBM<sup>®</sup> <span><img src="eserver.gif" alt="eServer" /></span> iSeries™ system provides support for direct
|
||
|
|
and bridged frame-relay network connections.</p>
|
||
|
|
<dl><dt class="dlterm">Direct frame-relay network</dt>
|
||
|
|
<dd>The direct frame-relay network allows communications using
|
||
|
|
Systems Network Architecture (SNA) or TCP/IP data over a frame-relay network
|
||
|
|
at speeds of up to 2.048 Mbps. This support allows a network of systems to
|
||
|
|
communicate using the frame-relay network as a backbone without the need for
|
||
|
|
multiple-leased T1 lines. This function is also known as <em>boundary network
|
||
|
|
node (BNN)</em> support.</dd>
|
||
|
|
<dt class="dlterm">Bridged frame-relay network</dt>
|
||
|
|
<dd>The bridged frame-relay network allows the iSeries system
|
||
|
|
to communicate over a frame-relay network. This communication takes place
|
||
|
|
through a remote bridge that is attached to a token-ring, Ethernet, or distributed
|
||
|
|
data interface (DDI) network. Bridged frame-relay connections allow the iSeries system
|
||
|
|
to communicate with stations on the remote local area network (LAN) as if
|
||
|
|
they were attached locally to the LAN. This function is also known as <em>boundary
|
||
|
|
access node (BAN)</em> support. <a href="#rzak3frnetconfig__rzak3bridgedexample">Figure 1</a> shows
|
||
|
|
an example of a bridged frame-relay connection. <div class="fignone" id="rzak3frnetconfig__rzak3bridgedexample"><a name="rzak3frnetconfig__rzak3bridgedexample"><!-- --></a><span class="figcap">Figure 1. Example of a bridged frame-relay network connection</span><br /><img src="rzak3520.gif" alt="Example of a bridged frame-relay
network connection" /><br /></div>
|
||
|
|
<p>In this example, iSeries System A communicates through the frame-relay
|
||
|
|
network and the bridge to iSeries System B. Bridged frame-relay connections
|
||
|
|
support SNA and TCP/IP data communications.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak3overview.htm">Frame relay</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak3rzak3bridged.htm" title="The iSeries system allows frame-relay connections to remote local area networks (LANs) that support the bridged frame-relay formats defined by the Frame-Relay Forum IA 3.1. Most bridges, routers, and communication controllers support these formats.">Bridged connections for frame relay</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|