65 lines
4.5 KiB
HTML
65 lines
4.5 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="Data link connection identifiers" />
|
||
|
|
<meta name="abstract" content="The IBM eServer iSeries system uses data link connection identifiers (DLCIs) to identify the logical connections between nodes." />
|
||
|
|
<meta name="description" content="The IBM eServer iSeries system uses data link connection identifiers (DLCIs) to identify the logical connections between nodes." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3addconsid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak3rzak3lmi.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="rzak3dlci" />
|
||
|
|
<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>Data link connection identifiers</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak3dlci"><a name="rzak3dlci"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Data link connection identifiers</h1>
|
||
|
|
<div><p>The IBM<sup>®</sup> <span><img src="eserver.gif" alt="eServer" /></span> iSeries™ system uses data link connection
|
||
|
|
identifiers (DLCIs) to identify the logical connections between nodes.</p>
|
||
|
|
<p>A single physical connection to the frame-relay network
|
||
|
|
is used to support multiple logical, or virtual, connections. The frame-relay
|
||
|
|
network assigns a DLCI number that identifies each virtual connection, called <em>permanent
|
||
|
|
virtual circuit (PVC)</em>. The iSeries system supports up to 256 virtual
|
||
|
|
circuits for each physical connection.</p>
|
||
|
|
<p>The frame-relay network provider assigns the DLCI number, typically at
|
||
|
|
subscription time, that is used to identify a virtual circuit. The DLCI number
|
||
|
|
applies only to the connection between nodes (TE-to-FH or FH-to-FH).</p>
|
||
|
|
<p><a href="#rzak3dlci__rzak3dlciexample">Figure 1</a> shows an example of DLCI
|
||
|
|
assignments for a frame-relay connection.</p>
|
||
|
|
<div class="fignone" id="rzak3dlci__rzak3dlciexample"><a name="rzak3dlci__rzak3dlciexample"><!-- --></a><span class="figcap">Figure 1. Example of DLCI assignments for PVC connections</span><br /><img src="rzak3503.gif" alt="Example of DLCI assignments
for PVC connections" /><br /></div>
|
||
|
|
<p>To configure DLCI values for frame-relay and bridged local
|
||
|
|
area network (LAN) line descriptions, specify the NWIDLCI parameter on the
|
||
|
|
line description command. You can also configure DLCI values by specifying
|
||
|
|
the DLCI number and line description name on the DLCI parameter of the Create
|
||
|
|
Network Interface (Frame Relay) (CRTNWIFR) command.</p>
|
||
|
|
<p>The iSeries system
|
||
|
|
uses DLCI 0 for the local management interface (LMI). This corresponds to
|
||
|
|
the ANSI Annex-D standard. The LMI manages the physical and virtual connections
|
||
|
|
between the terminal equipment (TE) and the frame handler (FH). Use DLCIs
|
||
|
|
1 through 1018 to identify logical connections to remote TEs.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak3rzak3addconsid.htm" title="This topic provides information about addressing for direct and bridged connections.">Frame-relay addressing</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak3rzak3lmi.htm" title="This topic provides information about parameters specifying how status information is exchanged between the frame-relay network and the systems attached to it.">Local management interface</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|