283 lines
21 KiB
HTML
283 lines
21 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="reference" />
|
|
<meta name="DC.Title" content="Cluster configuration checklist" />
|
|
<meta name="abstract" content="Complete the cluster configuration checklist to ensure that your environment is prepared properly before you begin to configure your cluster." />
|
|
<meta name="description" content="Complete the cluster configuration checklist to ensure that your environment is prepared properly before you begin to configure your cluster." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplan.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconfigsimpleclustermanagement.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconfiginetd.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigmanagetunablecommparameters.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigadminchecklist.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="rzaigconfigchecklist" />
|
|
<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>Cluster configuration checklist</title>
|
|
</head>
|
|
<body id="rzaigconfigchecklist"><a name="rzaigconfigchecklist"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Cluster configuration checklist</h1>
|
|
<div><p>Complete the cluster configuration checklist to ensure that your
|
|
environment is prepared properly before you begin to configure your cluster.</p>
|
|
<div class="section">
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. TCP/IP configuration checklist
|
|
for clusters</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e24">TCP/IP requirements</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="4.550758459743291%" headers="d0e24 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 ">Start TCP/IP on every node you plan to include in the cluster using
|
|
the <a href="../cl/strtcp.htm"><span class="cmdname">Start TCP/IP (STRTCP)
|
|
Command</span></a>.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e24 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 ">Configure the TCP loopback address (127.0.0.1) and verify that it shows
|
|
a status of <var class="varname">Active</var>. Verify using the <a href="../cl/wrktcpsts.htm"><span class="cmdname">Work with TCP/IP Network Status (WRKTCPSTS)</span> Command</a> on
|
|
every node in the cluster.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e24 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 ">Verify that the IP addresses used for clustering to a given node must
|
|
show a status of <var class="varname">Active</var> using the <a href="../cl/wrktcpsts.htm"><span class="cmdname">Work
|
|
with TCP/IP Network Status (WRKTCPSTS)</span> Command</a> on the subject
|
|
node.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e24 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 "><img src="./delta.gif" alt="Start of change" />Verify that INETD is active on all nodes in the cluster
|
|
by using either the STRTCPSVR *INETD command or through iSeries™ Navigator
|
|
by completing the following steps:<ol><li>In iSeries Navigator,
|
|
expand <span class="uicontrol">Network</span>.</li>
|
|
<li>Expand <span class="uicontrol">Servers</span>.</li>
|
|
<li>Expand <span class="uicontrol">TCP/IP</span>.</li>
|
|
<li>Right-click <span class="uicontrol">INETD</span> and select <span class="uicontrol">Start</span>.</li>
|
|
</ol>
|
|
This can be verified by the presence of a QTOGINTD (User QTCP) job in
|
|
the Active Jobs list on the subject node. <img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e24 "><img src="./delta.gif" alt="Start of change" />__<img src="./deltaend.gif" alt="End of change" /></td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 "><img src="./delta.gif" alt="Start of change" />Verify that user profile for INETD, which is specified in /QIBM/ProdData/OS400/INETD/inetd.config,
|
|
does not have more than minimal authority. The Start Cluster Node (STRCLUNOD)
|
|
command will fail, if this user profile has more than minimal authority.
|
|
By default, QUSER is specified as the user profile for INETD. <img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e24 "><img src="./delta.gif" alt="Start of change" />__<img src="./deltaend.gif" alt="End of change" /></td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 "><img src="./delta.gif" alt="Start of change" />Verify every IP address in the cluster can route to and send UDP datagrams
|
|
to every other IP address in the cluster. Use the PING command specifying
|
|
a local IP address and the TRACEROUTE command specifying UDP messages. <img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e24 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e24 ">Verify that ports 5550 and 5551 are not being used by other applications.
|
|
These ports are reserved for IBM<sup>®</sup> clustering. Port usage can be viewed using the <a href="../cl/wrktcpsts.htm"><span class="cmdname">Work with TCP/IP Network
|
|
Status (WRKTCPSTS)</span> command</a>. Port 5550 will be opened and
|
|
in a 'Listen' state by clustering once INETD is started.</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>If you plan to use switchable devices in your cluster, the following
|
|
requirements must be satisfied:</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 2. Resilient
|
|
device configuration checklist for clusters</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e131">Resilient device requirements</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">Verify that <a href="rzaigplanoption41.htm">Option 41 (HA Switchable
|
|
Resources)</a> is installed and a valid license key exists on all cluster
|
|
nodes that will be in the device domain. Note that any use of the <a href="rzaigconfigsimpleclustermanagement.htm">iSeries Navigator
|
|
cluster management</a> interface requires this option.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">In order to access disk management functions in iSeries Navigator, configure the service
|
|
tools server (STS) with DST access and user profiles. See <a href="../rzaly/rzalydst.htm">Set up communication</a> for details.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">If you are switching resilient devices between logical partitions on
|
|
a system, and you are using something other than the HMC to manage your logical
|
|
partitions, enable Virtual OptiConnect for the partitions. This is done at
|
|
dedicated service tools (DST) signon. See <a href="../rzait/rzaitvirtualconn.htm">Virtual
|
|
OptiConnect</a> for details.<p>If you are using the Hardware Management
|
|
Console to manage your partitions, <a href="../icbase/iphbl/iphblchangeprofile.htm">change
|
|
your partition profile properties</a> on the OptiConnect tab to enable
|
|
Virtual OptiConnect for each partition in the switchable configuration. You
|
|
must <a href="../icbase/iphbl/iphblactivate.htm">activate
|
|
the partition profile</a> to reflect the change.</p>
|
|
</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">If a tower on an HSL OptiConnect loop is switched between two systems,
|
|
and one of the systems has logical partitions, enable HSL OptiConnect for
|
|
the partitions. If you are using something other than the HMC to manage logical
|
|
partitions, this is done at dedicated service tools (DST) signon.<p>If you
|
|
are using the Hardware Management Console to manage your partitions, <a href="../icbase/iphbl/iphblchangeprofile.htm">change your partition
|
|
profile properties</a> on the OptiConnect tab to enable HSL OptiConnect
|
|
for each partition in the switchable configuration. You must <a href="../icbase/iphbl/iphblactivate.htm">activate the partition profile</a> to
|
|
reflect the change.</p>
|
|
</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">If you are switching resilient devices between logical partitions,
|
|
and you are using something other than the HMC to manage your logical partitions,
|
|
you must configure the bus to be shared between the partitions or configure
|
|
an I/O Pool. The bus must be configured the bus as "own bus shared" by one
|
|
partition, and all other partitions that will participate in the device switching
|
|
must be configured as "use bus shared."<p>If you are using the Hardware Management
|
|
Console to manage your logical partitions, you must configure an <a href="../icbase/iphbl/iphbliopools.htm">I/O Pool</a> that includes the
|
|
I/O processor, I/O adapter, and all attached resources to allow an independent
|
|
disk pool to be switchable between partitions. Each partition must have access
|
|
to the I/O pool. See <a href="../rzaly/rzalymakehardwareswitchable.htm">Make
|
|
your hardware switchable</a> for more details. <span><img src="./delta.gif" alt="Start of change" />For details
|
|
on physical planning requirements for switchable devices, see <a href="../rzaly/rzalyphysicalplanning.htm">Physical planning requirements</a>.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
|
</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">When switching a tower on a HSL loop between two different systems,
|
|
the tower must be configured as switchable. See <a href="../rzaly/rzalymakehardwareswitchable.htm">Make
|
|
your hardware switchable</a> for details.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">When a tower is added to an existing HSL loop, restart all servers
|
|
on that same loop.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e131 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e131 ">The maximum transmission unit (MTU) for your communication paths must
|
|
be greater than the cluster communications tuneable parameter, message fragment
|
|
size. MTU for a cluster IP address can be verified using the <a href="../cl/wrktcpsts.htm"><span class="cmdname">Work with TCP/IP Network Status (WRKTCPSTS)</span> command</a> on
|
|
the subject node. The MTU must also be verified at each step along the entire
|
|
communications path. It may be easier to lower the message fragment size parameter
|
|
once the cluster is created than raise the MTU for the communications path.
|
|
See <a href="rzaigmanagetunablecommparameters.htm">Tunable cluster communications
|
|
parameters</a> for more information about message fragment size. You can
|
|
use the <a href="../apis/clcntrtcrs.htm"><span class="apiname">Retrieve
|
|
Cluster Resource Services Information (QcstRetrieveCRSInfo)</span> API</a> to
|
|
view the current settings of the tuning parameters and the <a href="../apis/clcntchgcrs.htm"><span class="apiname">Change Cluster Resource Services (QcstChgClusterResourceServices)</span> API</a> to
|
|
change the settings.</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 3. Security configuration checklist
|
|
for clusters</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e249">Security requirements</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="4.550758459743291%" headers="d0e249 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e249 ">The ALWADDCLU (Allow Add to Cluster) network attribute must be appropriately
|
|
set on the target node if trying to start a remote node. This should be set
|
|
to *ANY or *RQSAUT depending on your environment. If set to *RQSAUT, then <span class="keyword">i5/OS™</span> option 34 (Digital Certificate
|
|
Manager) and Cryptographic Access Provided Product must be installed. See
|
|
<a href="rzaigconfigenablenode.htm">Enable a node to be added to a cluster</a> for
|
|
details on setting the ALWADDCLU network attribute.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e249 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e249 "><img src="./delta.gif" alt="Start of change" />Enable the status of the user profile for INETD specified
|
|
in /QIBM/ProdData/OS400/INETD/inetd.config. It must not have *SECADM or *ALLOBJ
|
|
special authorities. By default, QUSER is specified as the user profile for
|
|
INETD.<img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e249 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e249 ">Verify that the user profile invoking the cluster resource services
|
|
APIs exists on all cluster nodes and has *IOSYSCFG authority.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e249 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e249 "><img src="./delta.gif" alt="Start of change" />Verify that the user profile to run the exit program
|
|
for a cluster resource group (CRG) exists on all recovery domain nodes. <img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 4. Job configuration checklist for clusters</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e287">Job considerations</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="4.550758459743291%" headers="d0e287 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e287 ">Jobs can be submitted by the cluster resource services APIs to process
|
|
requests. The jobs will either run under the user profile to run the exit
|
|
program specified when creating the a cluster resource group, or under the
|
|
user profile that requested the API (for varying on devices in resilient device
|
|
CRGs only). The user must ensure that the subsystem which services the job
|
|
queue associated with the user profile is configured as: *NOMAX for the number
|
|
of jobs it can run from that job queue.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e287 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e287 ">Jobs will be submitted to the job queue specified by the job description
|
|
which is obtained from the user profile defined for a CRG. The default job
|
|
description will cause the jobs to be sent to the QBATCH job queue. Since
|
|
this job queue is used for many user jobs, the exit program job may not run
|
|
in a timely fashion. Users should consider a unique job description with a
|
|
unique user queue.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e287 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e287 ">When exit program jobs are run, they will use routing data from the
|
|
job description to choose which main storage pool and run time attributes
|
|
they will use. The default values will result in jobs that are run in a pool
|
|
with other batch jobs with a run priority of 50. Neither of these may produce
|
|
the desired performance for exit program jobs. The subsystem initiating the
|
|
exit program jobs (the same subsystem that is using the unique job queue)
|
|
should assign the exit program jobs to a pool that is not used by other jobs
|
|
initiated by the same subsystem or other subsystems. In addition, the exit
|
|
program jobs should be assigned a run priority of 15 so that they will run
|
|
before almost all other user jobs.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e287 "><img src="./delta.gif" alt="Start of change" />__<img src="./deltaend.gif" alt="End of change" /></td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e287 "><img src="./delta.gif" alt="Start of change" />The <a href="../rzakz/rzakzqmltthdacn.htm">QMLTTHDACN</a> system value must be set to 1 or 2. <img src="./deltaend.gif" alt="End of change" /></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>There are several software solutions available for configuring
|
|
and managing your cluster. One of these solutions is iSeries Navigator cluster management.
|
|
If you choose to use iSeries Navigator, the following requirements must
|
|
be satisfied:</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 5. iSeries Navigator configuration checklist
|
|
for clusters</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e331">iSeries Navigator cluster management
|
|
considerations</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="4.550758459743291%" headers="d0e331 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e331 "><a href="rzaigplanoption41.htm">Option 41 (<span class="keyword">i5/OS</span> -
|
|
HA Switchable Resources)</a> must be installed and a valid license key
|
|
must exist on all cluster nodes that will be in the device domain.</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e331 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e331 ">Verifty that all host servers are started using the <a href="../cl/strhostsvr.htm"><span class="cmdname">STRHOSTSVR (Start Host Server)</span> Command</a>:
|
|
STRHOSTSVR SERVER(*ALL)</td>
|
|
</tr>
|
|
<tr><td valign="top" width="4.550758459743291%" headers="d0e331 ">__</td>
|
|
<td valign="top" width="95.44924154025671%" headers="d0e331 ">Verify that the Management Central server is started using the <a href="../cl/strtcpsvr.htm"><span class="cmdname">STRTCPSVR (Start TCP/IP
|
|
Server) </span>Command</a>: STRTCPSVR SERVER(*MGTC)</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplan.htm" title="Find out what you need to do before you can set up clusters on your iSeries servers. Find out the prerequisites for clusters as well as hints on designing your cluster. Finally, read tips for setting up your network and some performance hints for clusters.">Plan for clusters</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaigconfigsimpleclustermanagement.htm" title="IBM offers a cluster management interface that is available through iSeries Navigator and accessible through Option 41 (i5/OS - HA Switchable Resources).">iSeries Navigator cluster management</a></div>
|
|
<div><a href="rzaigconfiginetd.htm" title="The Internet daemon (INETD) server must be started in order for a node to be added or started, as well as for merge partition processing.">INETD server</a></div>
|
|
<div><a href="rzaigmanagetunablecommparameters.htm" title="The Change Cluster Resource Services (QcstChgClusterResourceServices) API enables some of the cluster topology services and cluster communications performance and configuration parameters to be tuned to better suit the many unique application and networking environments in which clustering occurs. This API is available to any cluster that is running at cluster version 2 or later.">Tunable cluster communications parameters</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzaigadminchecklist.htm" title="Covers all the prerequisites that must be completed before creating a cluster administrative domain.">Cluster administrative domain checklist</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |