72 lines
5.0 KiB
HTML
72 lines
5.0 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="TCP/IP and OptiConnect" />
|
||
|
|
<meta name="abstract" content="OptiConnect can give you the ability to define TCP/IP connections over an OptiConnect bus. This topic describes this feature and how it might be used." />
|
||
|
|
<meta name="description" content="OptiConnect can give you the ability to define TCP/IP connections over an OptiConnect bus. This topic describes this feature and how it might be used." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajwoptlpar.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzajwvipvolpar" />
|
||
|
|
<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>TCP/IP and OptiConnect</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajwvipvolpar"><a name="rzajwvipvolpar"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">TCP/IP and OptiConnect</h1>
|
||
|
|
<div><p>OptiConnect can give you the ability to define TCP/IP connections
|
||
|
|
over an OptiConnect bus. This topic describes this feature and
|
||
|
|
how it might be used.</p>
|
||
|
|
<p>TCP/IP over OptiConnect provides another method for the routing building
|
||
|
|
blocks such as proxy ARP, unnumbered point-to-point networks, and virtual
|
||
|
|
IP interfaces. You can configure this with an OptiConnect-emulated LAN configuration
|
||
|
|
and an OptiConnect point-to-point configuration.</p>
|
||
|
|
<p>With an <span class="uicontrol">OptiConnect-emulated LAN configuration</span>,
|
||
|
|
the OptiConnect bus appears as a LAN to TCP/IP. This is simple to configure,
|
||
|
|
but the LAN OptiConnect connectivity is not automatic because it requires
|
||
|
|
Routing Information Protocol (RIP) or static routes.</p>
|
||
|
|
<p>The <span class="uicontrol">OptiConnect point-to-point configuration</span> uses
|
||
|
|
point-to-point unnumbered interfaces that are configured for each pair of
|
||
|
|
OptiConnect hosts. No new networks are created and so the LAN OptiConnect
|
||
|
|
connectivity is automatic. One advantage to this configuration is that no
|
||
|
|
additional route definitions are required. Connectivity between a host on
|
||
|
|
one network to hosts on another network is automatic. Another advantage is
|
||
|
|
that if both networks are active, data sent between iSeries™ servers flows over the OptiConnect
|
||
|
|
bus because these routes have the most specific subnet mask. If the OptiConnect
|
||
|
|
bus goes down, traffic is automatically switched to the token-ring LAN.</p>
|
||
|
|
<p><span class="uicontrol">OptiConnect point-to-point configuration using virtual IP</span> is
|
||
|
|
a variation on the unnumbered point-to-point configuration. Remember that
|
||
|
|
whenever you use unnumbered, point-to-point interfaces, each interface has
|
||
|
|
to have an associated local interface specified. This is the IP address by
|
||
|
|
which the system on the remote end of the point-to-point link will know the
|
||
|
|
local iSeries server.
|
||
|
|
This associated local interface might be the iSeries server's primary LAN interface,
|
||
|
|
as shown in the following figure. Or you can use a virtual IP interface as
|
||
|
|
the associated local interface. In this configuration, you use the OptiConnect
|
||
|
|
bus as a collection of point-to-point connections. You define an unnumbered
|
||
|
|
connection for each pair of hosts. Like the previous configuration, no additional
|
||
|
|
route definitions are required, and connectivity between a host on one network
|
||
|
|
to hosts on the other network are automatic. An advantage of this configuration
|
||
|
|
is that if either network is active, a path will exist to reach any iSeries server.</p>
|
||
|
|
<br /><img src="rzajw517.gif" alt="OptiConnect emulated LAN configuration" /><br /></div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajwoptlpar.htm" title="OptiConnect can connect multiple iSeries servers by using a high-speed, fiber-optic bus. This information covers using OptiConnect with logical partitions and the advantages of using them.">Routing with OptiConnect and logical partitions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|