59 lines
3.8 KiB
HTML
59 lines
3.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="LAN IOA addresses" />
|
||
|
<meta name="abstract" content="In a Systems Network Architecture (SNA) environment, you can determine the address for each input/output adapter (IOA)." />
|
||
|
<meta name="description" content="In a Systems Network Architecture (SNA) environment, you can determine the address for each input/output adapter (IOA)." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzajuplanningtokenringsupport.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="choosing_lan_physical_address" />
|
||
|
<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>LAN IOA addresses</title>
|
||
|
</head>
|
||
|
<body id="choosing_lan_physical_address"><a name="choosing_lan_physical_address"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">LAN IOA addresses</h1>
|
||
|
<div><p>In a Systems Network Architecture (SNA) environment, you can determine
|
||
|
the address for each input/output adapter (IOA).</p>
|
||
|
<p>You can use one of two addresses:</p>
|
||
|
<ul><li>The manufacturer-assigned address that is otherwise known as the burned-in
|
||
|
address, preset address, or universally-administered address.</li>
|
||
|
<li>The locally administered address.</li>
|
||
|
</ul>
|
||
|
<p>You define the locally administered address, and the system associates
|
||
|
it with the adapter. Using a locally administered address minimizes the reconfiguration
|
||
|
work when you replace the adapter.</p>
|
||
|
<p>For example, if you use the burned-in address of the adapter, you must
|
||
|
configure this address into every device that communicates with the adapter.
|
||
|
When you replace the adapter, you must go back to each device and reconfigure
|
||
|
them with the burned-in address of the new adapter. You cannot assign the
|
||
|
burned-in address of the replaced adapter to the new adapter.</p>
|
||
|
<p>You can avoid the reconfiguration work by associating a locally administered
|
||
|
address with the adapter and using this address in all devices that communicate
|
||
|
with the adapter. When you replace the adapter, associate the locally administered
|
||
|
address with the new adapter. Because the devices already have the locally
|
||
|
administered address, you do not need to re-configure them.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> No two adapters can have the same address in the same network.</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajuplanningtokenringsupport.htm" title="To make the configuration of token-ring support easier, you need to make some decisions about how to configure your connections.">Plan for token-ring support</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|