68 lines
5.2 KiB
HTML
68 lines
5.2 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="Routing with virtual OptiConnect and logical partitions" />
|
||
|
|
<meta name="abstract" content="Virtual OptiConnect TCP/IP interfaces are used as interpartition communication paths. A single iSeries server is logically partitioned in multiple virtual machines. Each partition has its own address space. To TCP/IP, each partition appears as a distinct iSeries server. This topic shows you how you can use this feature to your advantage." />
|
||
|
|
<meta name="description" content="Virtual OptiConnect TCP/IP interfaces are used as interpartition communication paths. A single iSeries server is logically partitioned in multiple virtual machines. Each partition has its own address space. To TCP/IP, each partition appears as a distinct iSeries server. This topic shows you how you can use this feature to your advantage." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajwoptlpar.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="rzajwvolpar" />
|
||
|
|
<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>Routing with virtual OptiConnect and logical partitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajwvolpar"><a name="rzajwvolpar"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Routing with virtual OptiConnect and logical partitions</h1>
|
||
|
|
<div><p>Virtual OptiConnect TCP/IP interfaces are used as interpartition
|
||
|
|
communication paths. A single iSeries™ server is logically partitioned
|
||
|
|
in multiple virtual machines. Each partition has its own address space. To
|
||
|
|
TCP/IP, each partition appears as a distinct iSeries server. This topic
|
||
|
|
shows you how you can use this feature to your advantage.</p>
|
||
|
|
<p>With logical partitions, a single iSeries server is logically partitioned
|
||
|
|
into multiple virtual machines. Virtual OptiConnect TCP/IP interfaces are
|
||
|
|
used as interpartition communication paths. Each partition has its own address
|
||
|
|
space, its own instance of TCP/IP, and might have its own dedicated I/O adapters.
|
||
|
|
To TCP/IP, each partition appears as a distinct iSeries server. TCP/IP communication
|
||
|
|
between the different partitions is done using a virtual OptiConnect bus.
|
||
|
|
The TCP/IP routing code uses the path to another partition no differently
|
||
|
|
than the path to another system connected by a physical OptiConnect bus.</p>
|
||
|
|
<br /><img src="rzajw515.gif" alt="LPAR" /><br /><p>In these examples, only one LAN adapter is installed in the system. It
|
||
|
|
is allocated to partition A. The clients in the LAN need to communicate with
|
||
|
|
the other partitions defined on the system. To do this, you define a transparent
|
||
|
|
subnet on the virtual OptiConnect bus. The LAN has a network address of 10.6.7.x.
|
||
|
|
You want to plan for additional partitions, so IP addresses are then needed.
|
||
|
|
To get 12 addresses, you must use a subnet mask of 255.255.255.240. This gives
|
||
|
|
you addresses 10.6.7.241 through 10.6.7.254, a total of 14 usable addresses.
|
||
|
|
You must ensure that these addresses are not already in use on the LAN. After
|
||
|
|
you get the addresses, you assign one to each partition. You add an interface
|
||
|
|
to each partition and define the address on the virtual OptiConnect bus.</p>
|
||
|
|
<br /><img src="rzajw516.gif" alt="Partition table" /><br /><p>Transparent subnetting is automatically enabled when the following statements
|
||
|
|
are true. First, the virtual OptiConnect bus is less than or equal to the
|
||
|
|
size of the MTU on the real LAN interface. Second, the OptiConnect bus subnet
|
||
|
|
is a subnet of the LAN network address. If both statements are true, then
|
||
|
|
transparent subnetting is automatically enabled. The interface 10.6.7.3 performs
|
||
|
|
a proxy for all the interfaces defined in the partitions. This allows clients
|
||
|
|
on the LAN to connect to the partitions.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajwoptlpar.htm" title="OptiConnect can connect multiple iSeries servers by using a high-speed, fiber-optic bus. This information covers using OptiConnect with logical partitions and the advantages of using them.">Routing with OptiConnect and logical partitions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|