52 lines
3.4 KiB
HTML
52 lines
3.4 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="Virtual Ethernet connectivity methods" />
|
||
|
|
<meta name="abstract" content="Virtual Ethernet creates a high speed virtual Ethernet segment that can be used to connect logical partitions in a physical iSeries server." />
|
||
|
|
<meta name="description" content="Virtual Ethernet creates a high speed virtual Ethernet segment that can be used to connect logical partitions in a physical iSeries server." />
|
||
|
|
<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="rzalmtcpip" />
|
||
|
|
<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>Virtual Ethernet connectivity methods</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalmtcpip"><a name="rzalmtcpip"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Virtual Ethernet connectivity methods</h1>
|
||
|
|
<div><p>Virtual Ethernet creates a high speed virtual Ethernet segment
|
||
|
|
that can be used to connect logical partitions in a physical iSeries™ server.</p>
|
||
|
|
<p>This LAN segment is separate from any real LAN that the server might have
|
||
|
|
a connection with. A virtual Ethernet is made up of a virtual line description
|
||
|
|
and i5/OS<sup>®</sup> TCP/IP
|
||
|
|
interface. The Linux TCP/IP interface then has its own IP address but uses
|
||
|
|
the virtual network device for its hardware. If a logical partition is connected
|
||
|
|
only to a virtual Ethernet segment, and you want your logical partition to
|
||
|
|
communicate with servers on an external LAN, you will need to bridge TCP/IP
|
||
|
|
traffic between the i5/OS external LAN and the virtual i5/OS LAN segment.
|
||
|
|
A logical flow of the IP packets would look something like this (Pre-V5R3
|
||
|
|
diagram):</p>
|
||
|
|
<br /><img src="rzalm504.gif" alt="Logical flow of the IP packets." /><br /><p>IP traffic initiated by the logical partition goes from the Linux network
|
||
|
|
interface to the virtual i5/OS interface. If the virtual interface is associated
|
||
|
|
with the external interface, the IP packets can continue on to the external
|
||
|
|
interface and towards its destination.</p>
|
||
|
|
<p>There are three methods for bridging the external and virtual Ethernet
|
||
|
|
segments. Each method has differences that make it useful based on your knowledge
|
||
|
|
of TCP/IP and your environment. Choose from one of the following methods: </p>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|