86 lines
5.9 KiB
HTML
86 lines
5.9 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="task" />
|
||
|
|
<meta name="DC.Title" content="TCP/IP Routing" />
|
||
|
|
<meta name="abstract" content="You can also route traffic to your logical partitions through your iSeries server with various routing techniques." />
|
||
|
|
<meta name="description" content="You can also route traffic to your logical partitions through your iSeries server with various routing techniques." />
|
||
|
|
<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="rzalmtcprouting" />
|
||
|
|
<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</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalmtcprouting"><a name="rzalmtcprouting"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">TCP/IP Routing</h1>
|
||
|
|
<div><p>You can also route traffic to your logical partitions through your iSeries™ server
|
||
|
|
with various routing techniques. </p>
|
||
|
|
<div class="p"><p>This solution is not difficult to configure on your iSeries but
|
||
|
|
depending on the topology of your network, it may not be practical to implement.
|
||
|
|
Consider the following pre-V5R3 figure:</p>
|
||
|
|
<br /><img src="rzalm501.gif" alt="Illustrated example of TCP/IP Routing." /><br /><p>The existing TCP/IP interface
|
||
|
|
(10.1.1.2) connects to the LAN. The LAN is connected to remote networks with
|
||
|
|
a router. The Linux TCP/IP interface is addressed as 10.1.10.2 and the virtual
|
||
|
|
Ethernet TCP/IP interface as 10.1.10.1. In i5/OS<sup>®</sup>, if you turn on IP Datagram Forwarding,
|
||
|
|
the iSeries will
|
||
|
|
route the IP packets to and from the logical partition. When you define your
|
||
|
|
Linux TCP/IP connection, the router address must be 10.1.10.1.</p>
|
||
|
|
<p>The difficulty
|
||
|
|
of this type of routing is getting the IP packets to the iSeries. In
|
||
|
|
this scenario, you could define a route on the router so that it passes packets
|
||
|
|
destined to the 10.1.10.0 network to the 10.1.1.2 interface. That works great
|
||
|
|
for remote network clients. It would also work 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 10.1.10.0 traffic to the iSeries 10.1.1.2 interface; therein starts
|
||
|
|
the impracticability of this method. If you have hundreds of LAN clients,
|
||
|
|
then you have to define hundreds of routes.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section">To configure a setup similar to this, use the following instructions:</div>
|
||
|
|
<ol><li class="stepexpand"><span>During the configuration of your logical partition, make sure you
|
||
|
|
selected to create virtual Ethernet. </span> See <a href="rzalmconfig.htm">Configure a logical partition</a>for more information.</li>
|
||
|
|
<li class="stepexpand"><span><a href="rzalmconfigvirtuallan.htm">Create an Ethernet line description for virtual Ethernet</a>. </span> Note the port of the hardware resource, because you will need it when
|
||
|
|
you set up TCP/IP in your logical partition. In the case of the above example,
|
||
|
|
assume the hardware resource is CMN05 with a port of 0 and although arbitrary,
|
||
|
|
the line description name is VETH0. <kbd class="userinput">CRTLINETH LIND(VETH0) RSRCNAME(CMN05)
|
||
|
|
LINESPEED(1G) DUPLEX(*FULL)</kbd></li>
|
||
|
|
<li class="stepexpand"><span>Add a TCP/IP Interface for your virtual line description. </span> Following the example, you could use: <kbd class="userinput">ADDTCPIFC INTNETADR('10.1.10.1')
|
||
|
|
LIND('VETH0') SUBNETMASK ('255.255.255.0')</kbd><p>Start your new TCP/IP
|
||
|
|
interface using the command <kbd class="userinput">STRTCPIFC INTNETADR (<var class="varname">yourIPaddress</var>)</kbd> or <kbd class="userinput">STRTCPIFC
|
||
|
|
INTNETADR('10.1.10.1')</kbd> for the example.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>On your logical partition, set up networking using the instructions
|
||
|
|
or tools provided by your Linux distribution. </span> Be sure to use the
|
||
|
|
correct IP address, subnet mask, port, and gateway IP address.<p>During the
|
||
|
|
TCP/IP setup in Linux, you will need to know your net or network device. If
|
||
|
|
you are running a 32-bit kernel version of 2.4.9 or less, the network device
|
||
|
|
is VETH plus the port number from when you configured an Ethernet line description.
|
||
|
|
If you are running a 64-bit kernel or a 32-bit kernel greater than or equal
|
||
|
|
to 2.4.10, the network device is ETH plus the port number. See <a href="rzalmconfigvirtuallan.htm">Create an Ethernet line description for virtual Ethernet</a> for more information. In the example:</p>
|
||
|
|
<ul class="simple"><li>the interface IP address is 10.1.10.2</li>
|
||
|
|
<li>the subnet mask is 255.255.255.0</li>
|
||
|
|
<li>the gateway IP address is 10.1.10.1</li>
|
||
|
|
<li>the network device is VETH0 or ETH0 depending on the kernel version.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Turn on IP datagram forwarding. </span> This allows the i5/OS TCP/IP
|
||
|
|
interfaces to pass IP packets between each other. <kbd class="userinput">CHGTCPA IPDTGFWD(*YES)</kbd></li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|