ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaig_5.4.0.1/rzaigplancommunications.htm

85 lines
5.6 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="Communications requirements for clusters" />
<meta name="abstract" content="Use any type of communications media in your clustering environment as long as it supports Internet Protocol (IP)." />
<meta name="description" content="Use any type of communications media in your clustering environment as long as it supports Internet Protocol (IP)." />
<meta name="DC.Relation" scheme="URI" content="rzaigplanrequirements.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzau3/rzau3kickoff.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="rzaigplancommunications" />
<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 for clusters</title>
</head>
<body id="rzaigplancommunications"><a name="rzaigplancommunications"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Communications requirements for clusters</h1>
<div><p>Use any type of communications media in your clustering environment
as long as it supports Internet Protocol (IP).</p>
<p>Cluster resource services uses only TCP/IP protocols to communicate between
nodes. Local area networks (LANs), wide area networks (WANs), OptiConnect
system area networks (SANs), or any combination of these connectivity devices
are supported. Your choice should be based on the following factors:</p>
<ul><li>Volume of transactions</li>
<li>Response time requirements</li>
<li>Distance between the nodes</li>
<li>Cost considerations</li>
</ul>
<p>You can use these same considerations when determining the connection media
to be used to connect primary and backup locations of resources. When planning
your cluster, it is recommended that you designate one or more of your backup
nodes in remote locations in order to survive a site loss disaster.</p>
<p>To avoid performance problems that might be caused by inadequate capacity,
you need to evaluate the communication media that is used to handle the volumes
of information that is sent from node to node. You can choose which physical
media you prefer to use such as token ring, Ethernet, asynchronous transfer
mode (ATM), SPD OptiConnect, High-Speed Link (HSL) OptiConnect, or Virtual
OptiConnect (a high-speed internal connection between logical partitions).</p>
<p>HSL OptiConnect is a technology provided by OptiConnect for <span class="keyword">i5/OS™</span> software
(<span class="keyword">i5/OS</span> Option 23 - <span class="keyword">i5/OS</span> OptiConnect). It can be used
to construct highly available solutions. HSL OptiConnect is a system area
network that provides high-speed, point-to-point connectivity between cluster
nodes by using High Speed Link (HSL) Loop technology. HSL OptiConnect requires
standard HSL cables, but no additional hardware.</p>
<p>For switchable hardware, also referred to as resilient device CRGs, you
need to have an independent disk pool that is switchable in your environment.
In a logical partition environment, this is a collection of disk units that
are on the bus that is being shared by the logical partitions, or that are
attached to an input/output processor that has been assigned to an I/O pool.
For a multi-system environment, this is one or more switchable expansion units
(towers) properly configured on the HSL loop also containing the systems in
the recovery domain. The switchable tower can also be used in an LPAR environment.
For more planning information about switchable hardware and independent disk
pools, see <a href="../rzaly/rzalyplan.htm"> Plan
for independent disk pools</a>.</p>
<div class="note"><span class="notetitle">Note:</span> If you are using 2810 LAN adapters using <strong>only</strong> TCP/IP, and not
using Systems Network Architecture (SNA) or IPX, you can increase your adapter
performance on a V4R5M0 server by specifying Enable only for TCP(*YES) for
your specific line description using the <a href="../cl/wrklind.htm"><span class="cmdname">Work with Line Descriptions (WRKLIND)</span> command</a>.
Enable only for TCP(*YES) is set automatically in V5R1M0 and later releases.</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplanrequirements.htm" title="Outlines the hardware, software, and communications requirements for using clusters.">Cluster requirements</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../rzau3/rzau3kickoff.htm">OptiConnect for i5/OS</a></div>
</div>
</div>
</body>
</html>