61 lines
4.1 KiB
HTML
61 lines
4.1 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<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))' />
|
||
|
|
<title>Point to point virtual Ethernet</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="rzahqprivatelan"></a>
|
||
|
|
<h3 id="rzahqprivatelan">Point to point virtual Ethernet</h3>
|
||
|
|
<p><img src="delta.gif" alt="Start of change" />i5/OS™ needs a way to communicate with its integrated Windows
|
||
|
|
servers. This communication takes place over a point to point virtual Ethernet
|
||
|
|
network. When an integrated server is installed a special virtual network
|
||
|
|
is created between it and a controlling i5/OS partition. This network is called point
|
||
|
|
to point because it has only two endpoints, the integrated server and the iSeries™, and also because, like a virtual Ethernet network, it is emulated within
|
||
|
|
the iSeries and no additional physical network adapters or cables are used.
|
||
|
|
In i5/OS, it is configured as an Ethernet line description with Port Number
|
||
|
|
value *VRTETHPTP.<img src="deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change" />When you run the Install Windows server (INSWNTSVR) command
|
||
|
|
it will configure a point to point virtual Ethernet.<img src="deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>You may wonder what makes a point to point virtual Ethernet connection
|
||
|
|
different from a virtual Ethernet network. The answer is that point to point
|
||
|
|
virtual Ethernet is configured differently and can only have two endpoints:
|
||
|
|
the iSeries and an integrated server. Point to point virtual Ethernet only
|
||
|
|
supports the TCP/IP protocol, and by default uses restricted IP addresses
|
||
|
|
in private domains, so the addresses are not passed through gateways or routers.</p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change" />For Integrated xSeries® Server (IXS) and Integrated xSeries Adapter
|
||
|
|
(IXA) attached xSeries servers, these addresses take the form of 192.168.xxx.yyy,
|
||
|
|
where (xxx and yyy can be from 1 to 2 digits.) For example, for an IXS that
|
||
|
|
is defined with hardware resource number LIN0<span class="bold">3</span>, the
|
||
|
|
IP address will be 192.168.<span class="bold">3</span>.yyy.<img src="deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change" />For iSCSI hardware, these addresses take the form of 192.168.xxx.yyy,
|
||
|
|
where xxx ranges from 100 to 254 and results in a unique class C network.
|
||
|
|
In our example, the i5/OS side of the point to point network will be given
|
||
|
|
the IP address 192.168.100.1, and the Windows side has 192.168.100.2. As
|
||
|
|
you define multiple line descriptions for the same hardware resource, yyy
|
||
|
|
is incremented.<img src="deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>You can allow the INSWNTSVR command to automatically assign these IP addresses
|
||
|
|
or manually configure them to prevent TCP/IP address collisions with other
|
||
|
|
hosts on the system.</p>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|