80 lines
4.7 KiB
HTML
80 lines
4.7 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="topic" />
|
||
|
|
<meta name="DC.Title" content="Communications requirements" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalyplan.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzalycommunications" />
|
||
|
|
<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>Communications requirements</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalycommunications"><a name="rzalycommunications"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Communications requirements</h1>
|
||
|
|
<div><p>Depending on how you plan to use independent disk pools, you must satisfy
|
||
|
|
the following communications requirements:</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Single-system environment</h4>There are no communications
|
||
|
|
requirements.</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Multisystem clustered environment </h4><div class="p">Switchable independent disk pools and independent disk pools
|
||
|
|
that are geographically mirrored are configured within an iSeries™ cluster.
|
||
|
|
The communication requirements include the following:<ul><li><span class="uicontrol">For switchable independent disk
|
||
|
|
pools</span>, at least one TCP/IP communications interface between the
|
||
|
|
servers in the cluster. For redundancy, it is recommended that there be at
|
||
|
|
least two separate interfaces between the servers. </li>
|
||
|
|
<li><span class="uicontrol">For geographic mirroring</span>,
|
||
|
|
the following are recommended: <ul><li>Up to a maximum of four unique TCP/IP addresses,
|
||
|
|
used exclusively for geographic mirroring. Geographic mirroring can generate
|
||
|
|
heavy communications traffic. If geographic mirroring shares the same IP
|
||
|
|
connection with another application, for example clustering, then geographic
|
||
|
|
mirroring might be suspended which results in synchronization. Likewise,
|
||
|
|
clustering response might be unacceptable which results in partitioned nodes.</li>
|
||
|
|
<li>Throughput for each data port connection should match, meaning that the
|
||
|
|
speed and connection type should be the same for all connections between server
|
||
|
|
pairs. If throughput is different, performance will be gated by the slowest
|
||
|
|
connection. </li>
|
||
|
|
</ul>
|
||
|
|
<p>Consider configuring a <a href="../rzaja/rzajagetstart.htm">virtual private network</a> for TCP/IP connections for the
|
||
|
|
following advantages:</p>
|
||
|
|
<ul><li>Security of data transmission by encrypting the data </li>
|
||
|
|
<li>Increased reliability of data transmission by sending greater redundancy</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Connections from the production system </h4>Geographic
|
||
|
|
mirroring will establish connections from the production system to each of
|
||
|
|
the data port TCP/IP addresses on the mirror copy. TCP can choose to connect
|
||
|
|
from any available TCP/IP address on the production system according to the
|
||
|
|
TCP routing table. The TCP address used is not limited to the addresses configured
|
||
|
|
for geographic mirroring on the production system. TCP may select the same
|
||
|
|
TCP/IP address on the production system to connect to each TCP/IP address
|
||
|
|
on the mirror copy. To control which TCP/IP address(es) on the production
|
||
|
|
system are used to connect to each address on the mirror copy, TCP/IP routes
|
||
|
|
can be created. This is useful to control which addresses on the production
|
||
|
|
system will be chosen for geographic mirroring. It can also eliminate a single
|
||
|
|
point of failure and potential bottleneck caused when all connections are
|
||
|
|
created from the same TCP/IP address.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalyplan.htm">Plan for independent disk pools</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|