76 lines
4.7 KiB
HTML
76 lines
4.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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-10-17" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<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))' />
|
||
|
|
<title>Use the TCP/IP interfaces for OptiConnect</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="tcpipuse"></a>
|
||
|
|
<h3 id="tcpipuse">Use the TCP/IP interfaces for OptiConnect</h3>
|
||
|
|
<p>You can configure the TCP/IP interfaces for OptiConnect in either of two
|
||
|
|
ways. In the first configuration, the OptiConnect bus is viewed similar to
|
||
|
|
a LAN, and has a single subnet address. Each *OPC interface is assigned a
|
||
|
|
unique IP address within the subnet, thus defining the host's connection to
|
||
|
|
that subnet. An example of this configuration is: </p>
|
||
|
|
<pre class="xmp">System A:
|
||
|
|
ADDTCPIFC INTNETADR('10.1.1.1') LIND(*OPC) SUBNETMASK('255.255.255.0')
|
||
|
|
System B:
|
||
|
|
ADDTCPIFC INTNETADR('10.1.1.2') LIND(*OPC) SUBNETMASK('255.255.255.0')
|
||
|
|
System C:
|
||
|
|
ADDTCPIFC INTNETADR('10.1.1.3') LIND(*OPC) SUBNETMASK('255.255.255.0')</pre>
|
||
|
|
<p>In the second configuration, you can use the associated local interface
|
||
|
|
parameter (<span class="italic">local-interface</span>). Using this method, you
|
||
|
|
can configure the OptiConnect interfaces as part of existing local subnets
|
||
|
|
to which the iSeries™ server is attached via other local interfaces (for
|
||
|
|
example, token ring or ethernet interfaces). Each OptiConnect interface would
|
||
|
|
define an endpoint of a point-to-point OptiConnect connection between two iSeries servers. The existing local interface would then be specified as the
|
||
|
|
associated local interface for the OptiConnect interface. An example of this
|
||
|
|
configuration is:</p>
|
||
|
|
<pre class="xmp">System A:
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.1') LIND(TRNLINE) SUBNETMASK('255.255.255.0')
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.2') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.1)
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.3') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.1)
|
||
|
|
System B:
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.2') LIND(TRNLINE) SUBNETMASK('255.255.255.0')
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.1') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.2)
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.3') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.2)
|
||
|
|
System C:
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.3') LIND(TRNLINE) SUBNETMASK('255.255.255.0')
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.1') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.3)
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.2') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.3)</pre>
|
||
|
|
<p>To use the associated local interface, you must configure an interface
|
||
|
|
on each system, and both must be active. Using the example above, the following
|
||
|
|
two lines represent a point-to-point configuration from System B to System
|
||
|
|
C.</p>
|
||
|
|
<pre class="xmp">ADDTCPIFC INTNETADR('9.1.1.3') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.2)
|
||
|
|
ADDTCPIFC INTNETADR('9.1.1.2') LIND(*OPC) SUBNETMASK('255.255.255.255') LCLIFC(9.1.1.3)</pre>
|
||
|
|
<p>The advantage of the associated local interface technique is that there
|
||
|
|
is no need to define new subnets for the OptiConnect bus. Subsequently, no
|
||
|
|
external route tables need to be updated to provide connectivity between the
|
||
|
|
OptiConnect interfaces and the rest of the TCP/IP network. Moreover, if one
|
||
|
|
of the OptiConnect paths goes inactive, packets will automatically be routed
|
||
|
|
over the backup interface. In the case of the second example above, the TRNLINE.
|
||
|
|
One disadvantage of this type of configuration is that an interface must be
|
||
|
|
defined for every destination on the OptiConnect bus.</p>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|