69 lines
4.8 KiB
HTML
69 lines
4.8 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="Supported token-ring functions" />
|
||
|
|
<meta name="abstract" content="Your server supports a range of token-ring technologies that support speeds of 4 Mbps, 16 Mbps, and 100 Mbps." />
|
||
|
|
<meta name="description" content="Your server supports a range of token-ring technologies that support speeds of 4 Mbps, 16 Mbps, and 100 Mbps." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajuunderstandingtokenringsuppora.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="supported_token-ring_features" />
|
||
|
|
<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>Supported token-ring functions</title>
|
||
|
|
</head>
|
||
|
|
<body id="supported_token-ring_features"><a name="supported_token-ring_features"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Supported token-ring functions</h1>
|
||
|
|
<div><p>Your server supports a range of token-ring technologies that support
|
||
|
|
speeds of 4 Mbps, 16 Mbps, and 100 Mbps. </p>
|
||
|
|
<p>These technologies support the IEEE 802.5 standard. The
|
||
|
|
100 Mbps token-ring input/output adapter (IOA) supports the High-Speed Token-Ring
|
||
|
|
IEEE 802.5 standard that specifies 100 Mbps operation.</p>
|
||
|
|
<p id="supported_token-ring_features__the_100mb_token-ring"><a name="supported_token-ring_features__the_100mb_token-ring"><!-- --></a><strong>The 100 Mbps token ring IOA:</strong></p>
|
||
|
|
<p>Your system can use the PCI 100/16/4 MB Token-Ring Adapter to support faster
|
||
|
|
networking. The IOA supports many protocols including TCP/IP and Systems Network
|
||
|
|
Architecture (SNA). It is compatible with earlier devices, but
|
||
|
|
does not support token-pipes or multilink. The adapter is also known as the
|
||
|
|
2744 IOA. The IOA introduces these new functions:</p>
|
||
|
|
<ul><li id="supported_token-ring_features__autosense"><a name="supported_token-ring_features__autosense"><!-- --></a><strong>Automatic ring-speed sensing</strong> (automatic sense) enables
|
||
|
|
your system and the switch to find the highest common ring speed to use between
|
||
|
|
them. The destination does not need to match this speed, because the switch
|
||
|
|
manages the differences in speed.</li>
|
||
|
|
<li><strong id="supported_token-ring_features__duplex_mode_negotiations"><a name="supported_token-ring_features__duplex_mode_negotiations"><!-- --></a>Duplex mode negotiation</strong> enables your
|
||
|
|
system and the switch to agree on the duplex mode to use (half or full duplex).
|
||
|
|
The available duplexing modes are dependent on the ring speed that you use.
|
||
|
|
At 4 Mbps or 16 Mbps you can use either half-duplex or full-duplex mode. At
|
||
|
|
100 Mbps you must use full-duplex mode (the speed for each channel (transmitting
|
||
|
|
or receiving) is 100 Mbps).</li>
|
||
|
|
</ul>
|
||
|
|
<p id="supported_token-ring_features__early_token_release"><a name="supported_token-ring_features__early_token_release"><!-- --></a><strong>Early token release:</strong></p>
|
||
|
|
<p>Only 16 Mbps rings that use half-duplex mode can use the early token release
|
||
|
|
function. This function reduces the time the next device on the same ring
|
||
|
|
waits for a free token. Early token release enables the transmitting device
|
||
|
|
to release the free token right after sending a frame. Thus, the next device
|
||
|
|
receives the free token sooner and can thereby transmit a frame. This function
|
||
|
|
is beneficial only in rings where the time to transmit a frame is shorter
|
||
|
|
than the travel time of the frame. That is, the time for the frame to travel
|
||
|
|
completely around the ring.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajuunderstandingtokenringsuppora.htm" title="After you understand token-ring support, you can plan how to configure the system.">Understand token-ring support</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|