66 lines
4.5 KiB
HTML
66 lines
4.5 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="Physical planning 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="rzalyphysicalplanning" />
|
||
|
<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>Physical planning requirements</title>
|
||
|
</head>
|
||
|
<body id="rzalyphysicalplanning"><a name="rzalyphysicalplanning"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Physical planning requirements</h1>
|
||
|
<div><p>Depending on how you plan to use independent disk pools, you must satisfy
|
||
|
the following physical planning requirements:</p>
|
||
|
<div class="section"><h4 class="sectiontitle">Multisystem clustered environment (for switchable independent
|
||
|
disk pools)</h4><p>High-speed link (HSL) cables must be used to attach
|
||
|
the expansion units to the servers in the cluster. </p>
|
||
|
<p>The expansion unit
|
||
|
must be physically adjacent in the HSL loop to the alternate system or expansion
|
||
|
unit owned by the alternative system. You can include a maximum of two servers
|
||
|
(cluster nodes) on each HSL loop, though each server can be connected to multiple
|
||
|
HSL loops. You can include a maximum of four expansion units on each HSL loop,
|
||
|
though a maximum of three expansion units can be included on each loop segment.
|
||
|
On an HSL loop containing two servers, two segments exist, separated by the
|
||
|
two servers. All expansion units on one loop segment must be contained in
|
||
|
the same device cluster resource group (CRG).</p>
|
||
|
<div class="p"><img src="./delta.gif" alt="Start of change" />In order
|
||
|
for an expansion unit to become switchable it must physically be the farthest
|
||
|
away from the owning server on the loop segment. <div class="note"><span class="notetitle">Note:</span> An error will occur
|
||
|
if you try to make an expansion unit switchable if there is another expansion
|
||
|
unit farther away the owning server that has not become switchable.</div>
|
||
|
<div class="fignone"><span class="figcap">Figure 1. These expansion units are all private and are not switchable.</span><br /><img src="./delta.gif" alt="Start of change" /><img src="rzaly500.gif" alt="This is an
example of units that are not switchable." /><img src="./deltaend.gif" alt="End of change" /><br /></div>
|
||
|
<div class="fignone"><span class="figcap">Figure 2. The expansion unit farthest away from the owning
|
||
|
server on the loop segment has been made switchable.</span><br /><img src="./delta.gif" alt="Start of change" /><img src="rzaly509.gif" alt="This is an
example of one expansion unit that has been made switchable. The other units
are still private." /><img src="./deltaend.gif" alt="End of change" /><br /></div>
|
||
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
<p>The switchable expansion unit must be SPCN-cabled to the system unit that
|
||
|
will initially serve as the primary node for the switchable hardware group
|
||
|
(device CRG). The primary node might be a primary or secondary logical partition
|
||
|
within the system unit. If using logical partitions, the system buses in the
|
||
|
intended expansion unit must be owned and dedicated by the partition involved
|
||
|
in the cluster.</p>
|
||
|
</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>
|