121 lines
8.7 KiB
HTML
121 lines
8.7 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="Frame relay" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3printingme.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3frnetconfig.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3physenviron.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3frconfigs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3configob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3addconsid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3formats.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3sizeconsid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3perftunparms.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3lmi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3scenarios.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3related.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="overview" />
|
||
|
|
<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>Frame relay</title>
|
||
|
|
</head>
|
||
|
|
<body id="overview"><a name="overview"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Frame relay</h1>
|
||
|
|
<div><p><em>Frame relay</em> is a communications networking protocol
|
||
|
|
that defines how frames are routed through a fast-packet network based on
|
||
|
|
the address field in the frame. Frame relay takes advantage of the reliability
|
||
|
|
of data communications networks to minimize the error checking done by the
|
||
|
|
network nodes. This provides a packet-switching protocol similar to but much
|
||
|
|
faster than the X.25 standard.</p>
|
||
|
|
<p>The high speed that you can obtain through frame-relay networks makes them
|
||
|
|
well suited for wide area network (WAN) connectivity. Administrators commonly
|
||
|
|
use frame relay to connect two or more local area network (LAN) bridges over
|
||
|
|
large distances.</p>
|
||
|
|
<p>The following figure shows the frame format that frame-relay networks use.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. Frame format that frame-relay networks use</span><br /><img src="rzak3510.gif" alt="Frame format that frame-relay
networks use" /><br /></div>
|
||
|
|
<p>Frame-relay network architecture is based on the integrated systems digital
|
||
|
|
network (ISDN) packet-mode bearer services. <a href="#overview__rzak3standard">Table 1</a> shows
|
||
|
|
the standards, either pending or approved, that define the services and the
|
||
|
|
user-to-network interface of frame-relay networks.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><a name="overview__rzak3standard"><!-- --></a><table cellpadding="4" cellspacing="0" summary="" id="overview__rzak3standard" class="singleborder" frame="border" border="1" rules="all"><caption>Table 1. ANSI and equivalent ITU-T standards</caption><thead align="left"><tr valign="bottom"><th align="left" valign="bottom" width="50%" id="d0e37">ANSI standard</th>
|
||
|
|
<th align="left" valign="bottom" width="50%" id="d0e39">Equivalent ITU-T standard</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr valign="bottom"><td align="left" valign="bottom" width="50%" headers="d0e37 ">T1.606, Frame Relay Bearer Services (FRBS) Architectural
|
||
|
|
Framework</td>
|
||
|
|
<td align="left" valign="bottom" width="50%" headers="d0e39 ">I.233, ISDN Frame Mode Bearer Service</td>
|
||
|
|
</tr>
|
||
|
|
<tr valign="bottom"><td align="left" valign="bottom" width="50%" headers="d0e37 ">T1.618, FRBS Core Aspects</td>
|
||
|
|
<td align="left" valign="bottom" width="50%" headers="d0e39 ">Q.922, ISDN Extended Data Link (LAP-E)</td>
|
||
|
|
</tr>
|
||
|
|
<tr valign="bottom"><td align="left" valign="bottom" width="50%" headers="d0e37 ">T1.617, FRBS Signaling</td>
|
||
|
|
<td align="left" valign="bottom" width="50%" headers="d0e39 ">Q.933, Frame Mode Bearer Services (FMBS) Signaling</td>
|
||
|
|
</tr>
|
||
|
|
<tr valign="bottom"><td align="left" valign="bottom" width="50%" headers="d0e37 ">T1.606 Addendum 1, FRBS Congestion Management</td>
|
||
|
|
<td align="left" valign="bottom" width="50%" headers="d0e39 ">I.370, ISDN FMBS Congestion Management</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>The IBM<sup>®</sup> <span><img src="eserver.gif" alt="eServer" /></span> iSeries™ system
|
||
|
|
implementation of frame-relay network support uses protocol headers as defined
|
||
|
|
in the TCP/IP Request for Comment 1490 (RFC 1490).</p>
|
||
|
|
<p>Frame-relay networks achieve their greater efficiency by
|
||
|
|
minimizing the error checking done by nodes within the network. For Systems
|
||
|
|
Network Architecture (SNA), iSeries frame-relay support uses IEEE 802.2 logical
|
||
|
|
link control to provide flow control and error recovery functions (see <a href="#overview__rzak3implement">Figure 2</a>).</p>
|
||
|
|
<div class="fignone" id="overview__rzak3implement"><a name="overview__rzak3implement"><!-- --></a><span class="figcap">Figure 2. iSeries implementation of frame-relay
|
||
|
|
networking</span><br /><img src="rzak3511.gif" alt="iSeries implementation of
frame-relay networking" /><br /></div>
|
||
|
|
<p>As indicated above, you can make the connection between
|
||
|
|
the iSeries system
|
||
|
|
and the frame-relay network by using X.21, V.35, or RS-449 physical interfaces.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3printingme.htm">Printable PDF</a></strong><br />
|
||
|
|
Use this to view and print a PDF of this topic.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3frnetconfig.htm">Network connections for frame relay</a></strong><br />
|
||
|
|
The IBM <span><img src="eserver.gif" alt="eServer" /></span> iSeries system provides support for direct
|
||
|
|
and bridged frame-relay network connections.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3physenviron.htm">Physical environment for frame relay</a></strong><br />
|
||
|
|
This topic provides information about interface options for connecting equipment to a frame-relay network.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3frconfigs.htm">Configurations for frame relay</a></strong><br />
|
||
|
|
This topic provides information about options for the frame-relay network configuration.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3configob.htm">Configuration objects for frame relay</a></strong><br />
|
||
|
|
There are several options for network interface description, line description, and controller description.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3addconsid.htm">Frame-relay addressing</a></strong><br />
|
||
|
|
This topic provides information about addressing for direct and bridged connections.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3formats.htm">Routing characteristics for frame relay</a></strong><br />
|
||
|
|
This topic provides information about how data is routed through a frame-relay network.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3sizeconsid.htm">Maximum frame-size parameter requirements for frame relay</a></strong><br />
|
||
|
|
This topic helps you determine the value of the maximum frame size.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3perftunparms.htm">Tune frame-relay performance</a></strong><br />
|
||
|
|
<span>This topic provides information about adjusting
|
||
|
|
parameters for greater network performance.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3lmi.htm">Local management interface</a></strong><br />
|
||
|
|
This topic provides information about parameters specifying how status information is exchanged between the frame-relay network and the systems attached to it.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3scenarios.htm">Scenarios: Frame-relay configuration</a></strong><br />
|
||
|
|
<span>This topic provides examples of frame-relay configurations.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzak3rzak3related.htm">Related information for frame relay</a></strong><br />
|
||
|
|
Listed here is a manual that relates to the Frame relay topic. You can view or print the PDF.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|