87 lines
6.3 KiB
HTML
87 lines
6.3 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 routing method" />
|
|
<meta name="abstract" content="Standard TCP/IP routing is used to route traffic to the virtual Ethernet network in the same way you define routing to any other LAN. This requires that you update routing information throughout your network." />
|
|
<meta name="description" content="Standard TCP/IP routing is used to route traffic to the virtual Ethernet network in the same way you define routing to any other LAN. This requires that you update routing information throughout your network." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2virtethernet.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2proxyarp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2nat.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2virtethconsider.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2iproutenableveth.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2iproutcreatevethlind.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2iproutdataforward.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzai2iproutcreatevethifcs.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="routing" />
|
|
<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 routing method</title>
|
|
</head>
|
|
<body id="routing"><a name="routing"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">TCP/IP routing method</h1>
|
|
<div><p>Standard TCP/IP routing is used to route traffic to the virtual
|
|
Ethernet network in the same way you define routing to any other LAN. This
|
|
requires that you update routing information throughout your network.</p>
|
|
<p>You can also route traffic to your partitions through your iSeries™ server
|
|
with various routing techniques. This solution is not difficult to configure
|
|
on the server but, depending on the topology of your network, it may not be
|
|
practical to implement. Consider the following figure.</p>
|
|
<br /><img src="rzai2507.gif" alt="Shows route IP packets take from partition A and B. Packets go to virtual TCP/IP interface by going to external i5/OS interface on partition A." /><br /><p>The existing TCP/IP interface (<samp class="codeph">10.1.1.2</samp>) connects to the
|
|
LAN. The LAN is connected to remote networks with a router. The virtual
|
|
TCP/IP interface on partition B is addressed as <samp class="codeph">10.1.10.2</samp> and
|
|
the virtual TCP/IP interface on partition A as <samp class="codeph">10.1.10.1</samp>.
|
|
In i5/OS™,
|
|
if you turn on IP datagram forwarding, i5/OS will route the IP packets to and
|
|
from partition B. When you define your TCP/IP connection for partition B,
|
|
the router address must be <samp class="codeph">10.1.10.1</samp>.</p>
|
|
<p>The difficulty of this type of routing is getting the IP packets to the iSeries.
|
|
In this scenario, you can define a route on the router so that it passes
|
|
packets destined to the <samp class="codeph">10.1.10.0</samp> network to the <samp class="codeph">10.1.1.2</samp> interface.
|
|
That works for remote network clients. It also works for the local LAN clients
|
|
(clients connected to the same LAN as the iSeries) if they recognize that same
|
|
router as their next hop. If they do not, then each client must have a route
|
|
that directs <samp class="codeph">10.1.10.0</samp> traffic to the i5/OS <samp class="codeph">10.1.1.2</samp> interface;
|
|
therein starts the impracticability of this method. If you have many LAN
|
|
clients, then you must define many routes.</p>
|
|
<p>To configure virtual Ethernet to use the TCP/IP routing method, use the
|
|
following instructions:</p>
|
|
</div>
|
|
<div>
|
|
<ol>
|
|
<li class="olchildlink"><a href="rzai2iproutenableveth.htm">Step 1: Enable the logical partitions to participate in a virtual Ethernet</a><br />
|
|
</li>
|
|
<li class="olchildlink"><a href="rzai2iproutcreatevethlind.htm">Step 2: Create the Ethernet line descriptions</a><br />
|
|
</li>
|
|
<li class="olchildlink"><a href="rzai2iproutdataforward.htm">Step 3: Turn on IP datagram forwarding</a><br />
|
|
</li>
|
|
<li class="olchildlink"><a href="rzai2iproutcreatevethifcs.htm">Step 4: Create the interfaces</a><br />
|
|
</li>
|
|
</ol>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzai2virtethernet.htm" title="You can take advantage of virtual Ethernet on i5/OS.">TCP/IP techniques connecting virtual Ethernet to external LANs</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzai2proxyarp.htm" title="This proxy Address Resolution Protocol (ARP) method uses transparent subnetting to associate a partition's virtual interface with an external interface. Proxy ARP function is built into the TCP/IP stack. If you have the necessary IP addresses, this approach is recommended.">Proxy Address Resolution Protocol method</a></div>
|
|
<div><a href="rzai2nat.htm" title="You can use i5/OS packet filtering to route traffic between a partition and the outside network.">Network address translation method</a></div>
|
|
<div><a href="rzai2virtethconsider.htm" title="You can use virtual Ethernet as an alternative to using a network card for interpartition communication.">Virtual Ethernet considerations</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |