ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzai2_5.4.0.1/rzai2virtethconsider.htm

81 lines
5.7 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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 considerations" />
<meta name="abstract" content="You can use virtual Ethernet as an alternative to using a network card for interpartition communication." />
<meta name="description" content="You can use virtual Ethernet as an alternative to using a network card for interpartition communication." />
<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="rzai2routing.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="virtethconsider" />
<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 considerations</title>
</head>
<body id="virtethconsider"><a name="virtethconsider"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Virtual Ethernet considerations</h1>
<div><p>You can use virtual Ethernet as an alternative to using a network
card for interpartition communication.</p>
<p>Virtual Ethernet enables you to establish high-speed communication between
logical partitions without purchasing additional hardware. For each of the
16 ports enabled, the system creates a virtual Ethernet communications port,
such as CMN<em>xx</em> with a resource type of 268C. Logical partitions assigned
to the same local area network (LAN) then become available to communicate
through that link. A physical system allows you to configure up to 16 different
virtual local area networks. Virtual Ethernet provides the same function as
using a 1 Gb Ethernet adapter. Token Ring or Ethernet 10 Mbps and 100 Mbps
local area networks are not supported with virtual Ethernet.</p>
<div class="p">Virtual Ethernet is an economical networking solution that provides substantial
benefits: <ul><li>Economical: Potentially no extra networking hardware is required. You
can add partitions to the server and communicate with an external LAN without
installing extra physical LAN cards. If the current server has limited available
card slots in which to install additional LAN cards, then using the virtual
Ethernet offers the capability to operate LAN-attached partitions without
the requirement to upgrade the server.</li>
<li>Flexible: It is possible to configure a maximum of 16 distinctive connections
enabling the configuration of selective communication paths between partitions.
For added flexibility, the configuration model allows logical partitions to
implement both a virtual Ethernet and physical LAN connection. This is a desirable
feature when using the Linux<sup>®</sup> partition to host a firewall application.</li>
<li>Fast: The virtual Ethernet emulates a 1 GB Ethernet connection and provides
a fast and convenient communication method between partitions. This enhances
the opportunity to integrate separate applications that run on different logical
partitions.</li>
<li>Versatile: Regardless of whether your partitions are running on i5/OS™ or Linux,
they can all be connected to the same virtual Ethernet.</li>
<li>Reduced congestion: By using the virtual Ethernet for interpartition communication,
communication traffic is reduced on the external LAN. In the case of Ethernet,
which is a collision-based standard, this will certainly help prevent a degradation
of service for other LAN users.</li>
</ul>
</div>
</div>
<div>
<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="rzai2routing.htm" title="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.">TCP/IP routing method</a></div>
</div>
</div>
</body>
</html>