IBM Cluster Systems Management for AIX 5LPlanning and Installation Guide Version 1.3.2 SA22-7919-04 ___IBM Cluster Systems
Management for AIX 5LPlanning and Installation
Guide Version 1.3.2 SA22-7919-04 ___Note Before using this
information and the product it supports, read the information in “Notices” on
page 109.Fifth Edition (September
2003) This edition applies to
version 1, release 3, modification 2 of IBM Cluster Systems Management (CSM)
for AIX 5L 5.2, program number 5765–F67, and to all subsequent releases of this
product until otherwise indicated in new editions. Significant changes or
additions to the text and illustrations are indicated by a vertical line ( | )
to the left of the change. IBM® welcomes your comments.
A form for readers’ comments may be provided at the back of this publication,
or you may address your comments to the following address: International
Business Machines Corporation Department 55JA, Mail Station P384 2455 South
Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States
& Canada): 1+845+432-9405 FAX (Other Countries): Your International Access
Code +1+845+432-9405 IBMLink™ (United States customers
only): IBMUSM10(MHVRCFS) IBM Mail Exchange: USIB6TC9 at IBMMAIL Internet
e-mail: mhvrcfs@us.ibm.comIf you would like a reply, be sure to include your
name, address, telephone number, or FAX number. Make sure to include the
following in your comment or note: v Title and order number of this book v Page
number or topic related to your commentWhen you send information to IBM, you
grant IBM a nonexclusive right to use or distribute the information in any way
it believes appropriate without incurring any obligation to you. © Copyright
International Business Machines Corporation 2002, 2003. All rights reserved. US Government Users
Restricted Rights – Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp. Contents About this book . . . . . . . . . . . . . . . . . . . . . . . .vii Who should use
this book . . . . . . . . . . . . . . . . . . . . .vii Typographic conventions
. . . . . . . . . . . . . . . . . . . . .vii ISO 9000 . . . . . . . . . . . . .
. . . . . . . . . . . . . .vii Prerequisite and related information . . . . . .
. . . . . . . . . . .viii How to send your comments . . . . . . . . . . . . . .
. . . . . .viii Chapter 1. CSM Overview . . . . . . . . . . . .
. . . . . . . . .1 What is Cluster Systems Management (CSM)? . . . . . . . . .
. . . .1 How CSM helps you manage your cluster . . . . . . . . . . . . . .1
Communicating with CSM . . . . . . . . . . . . . . . . . . . .3 What’s new or
changed in CSM 1.3.2 . . . . . . . . . . . . . . . . .3 Additional hardware for
cluster nodes . . . . . . . . . . . . . . . .3 Linux on pSeries support . . . .
. . . . . . . . . . . . . . . .3 Use of AIX installation and software
maintenance tools . . . . . . . . .4 User customization scripts for AIX nodes .
. . . . . . . . . . . . . .4 Secondary adapter configurations . . . . . . . . .
. . . . . . . .4 Enhanced backup and restore features . . . . . . . . . . . . .
. .4 Chapter 2. Planning for
Cluster Systems Management . . . . . . . . .5 Parallel Systems Support Program (PSSP) and CSM
non-compatibility . . . . .5 Understanding CSM hardware requirements . . . . .
. . . . . . . . .5 Management server requirements . . . . . . . . . . . . . . .
. .5 Cluster node requirements . . . . . . . . . . . . . . . . . . . .7
Hardware installation . . . . . . . . . . . . . . . . . . . . . .8 Hardware
control requirements . . . . . . . . . . . . . . . . . .8 Understanding CSM
licensing requirements . . . . . . . . . . . . . . .9 CSM Try and Buy option .
. . . . . . . . . . . . . . . . . . . .9 CSM full license . . . . . . . . . . .
. . . . . . . . . . . . .9 Understanding CSM software requirements . . . . . .
. . . . . . . .10 1. AIX 5.2 . . . . . . . . . . . . . . . . . . . . . . . . .
.10 2. AIX version 5.1 with the 5100–03 Recommended Maintenance package (only
required for AIX version 5.1) . . . . . . . . . . . . . . . .10 3. CSM for AIX
product software . . . . . . . . . . . . . . . . .10 4. Required open source
software shipped on the AIX product media . . . .11 5. Other required open
source software . . . . . . . . . . . . . . .11 6. Product software updates and
fixes . . . . . . . . . . . . . . .11 7. Linux distribution software (only
required for Linux nodes) . . . . . . .11 8. CSM for Linux product software
(only required for Linux nodes) . . . . .12 9. Open source software shipped on
Linux product media (only required for Linux nodes) . . . . . . . . . . . . . .
. . . . . . . . . .12 10. Software required to support the Equinox Ethernet
Serial Provider (ESP) console . . . . . . . . . . . . . . . . . . . . . . . . .
.16 11. OpenSSH and prerequisite software (only required when using OpenSSH as
the remote shell) . . . . . . . . . . . . . . . . . . . . .17 Host name
resolution . . . . . . . . . . . . . . . . . . . . . .17 Chapter 3. Installing
the Management Server . . . . . . . . . . . . .19 Before you install the management
server . . . . . . . . . . . . . . .19 Summary of the installation steps . . .
. . . . . . . . . . . . . . .19 Step 1. Check management server software
requirements . . . . . . . . .19 Step 2. Register host names of nodes and
management server . . . . . . .20 Step 3. Update the $PATH and $MANPATH
variables . . . . . . . . . .20 © Copyright IBM Corp. 2002, 2003 iii |||||||||||||||||||||||||
Step
4. Create the /csminstall file system (optional) . . . . . . . . . . .20 Step
5. Download CSM Updates . . . . . . . . . . . . . . . . . .21 Step 6. Download
Open Source Software . . . . . . . . . . . . . . .21 Downloading openCIMOM
(required for hardware control) . . . . . . . .21 Downloading autoupdate (required
for CSM Software Maintenance System (SMS)) . . . . . . . . . . . . . . . . . .
. . . . . . . .22 Step 7. Verify that the prerequisite software is installed .
. . . . . . . . .22 Step 8. Apply updates to CSM filesets that have already
been installed with AIX 24 Step 9. Install CSM management server software . . .
. . . . . . . . .24 Step 10. Apply management server software updates . . . . .
. . . . . .24 Step 11. Check the remote shell attribute . . . . . . . . . . . .
. . .25 Setting up OpenSSH . . . . . . . . . . . . . . . . . . . . . .25
Running csmconfig to display remote shell values . . . . . . . . . . .26 Step
12. Install OpenSSH and OpenSSL (optional) . . . . . . . . . . .26 Step 13.
Accept the CSM license . . . . . . . . . . . . . . . . . .27 Accepting the full
production license . . . . . . . . . . . . . . . .27 Accepting the try-and-buy
license . . . . . . . . . . . . . . . . .27 Step 14. Copy CSM files into the
/csminstall subdirectories . . . . . . . .28 Step 15. Set the cluster ID (optional)
. . . . . . . . . . . . . . . . .28 Step 16. Verify the installation . . . . .
. . . . . . . . . . . . . .28 Chapter
4. Defining nodes for the cluster .
. . . . . . . . . . . . .29 Determining node attributes . . . . . . . . . . . .
. . . . . . . .29 General attributes . . . . . . . . . . . . . . . . . . . . .
. .29 Hardware control attributes . . . . . . . . . . . . . . . . . . .29
Installation software information for nodes . . . . . . . . . . . . . .32
Collecting node attribute values . . . . . . . . . . . . . . . . . . .33
Defining the nodes . . . . . . . . . . . . . . . . . . . . . . .34 Defining a
single node . . . . . . . . . . . . . . . . . . . . .34 Creating a node
definition file . . . . . . . . . . . . . . . . . .36 Using a node definition file
. . . . . . . . . . . . . . . . . . .38 Using a host name mapping file . . . .
. . . . . . . . . . . . .39 Using the starting_node and count method for
xSeries nodes . . . . . . .42 Chapter
5. Adding AIX nodes to the cluster .
. . . . . . . . . . . .45 Before you add AIX nodes . . . . . . . . . . . . . .
. . . . . . .45 Summary of the steps for adding AIX nodes . . . . . . . . . . .
. . .45 Step 1. Check node software requirements . . . . . . . . . . . . . .45
Step 2. Store hardware control point user IDs and passwords . . . . . . .45
Step 3. Verify the node definitions . . . . . . . . . . . . . . . . . .46 Step
4. Create CSM node groups (optional) . . . . . . . . . . . . . .47 Step 5.
Prepare customization scripts (optional) . . . . . . . . . . . . .48 Step 6.
Add the AIX nodes to the cluster . . . . . . . . . . . . . . .48 Remote shell
authentication . . . . . . . . . . . . . . . . . . .49 Step 7. Verify that the
nodes are added . . . . . . . . . . . . . . . .50 Chapter 6. Adding Linux nodes to the
cluster . . . . . . . . . . . .53 Before you
add Linux nodes . . . . . . . . . . . . . . . . . . . .53 Summary of the steps
for adding Linux nodes . . . . . . . . . . . . .53 Step 1. Check node software
requirements . . . . . . . . . . . . . .53 Step 2. Copy the Linux CSM packages
and other prerequisite software . . . .53 Step 3. Store hardware control point
user IDs and passwords . . . . . . .54 Step 4. Verify the node definitions . .
. . . . . . . . . . . . . . . .55 Step 5. Create CSM node groups (optional) . .
. . . . . . . . . . . .57 Step 6. Prepare customization scripts (optional) . .
. . . . . . . . . . .57 Step 7. Add Linux nodes to the cluster . . . . . . . .
. . . . . . . .57 iv CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||||||||||||||
Remote
shell authentication: . . . . . . . . . . . . . . . . . . .58 Step 8. Reboot
the nodes (optional for hardware control) . . . . . . . . .58 Step 9. Verify
that the nodes are added . . . . . . . . . . . . . . . .59 Chapter 7. Installing the AIX
operating system and adding nodes .
. . .61 Before you install the AIX operating system and add cluster nodes . . .
. . .61 Summary of the steps for installing both AIX and CMS on cluster nodes .
. . .61 Step 1. Store hardware control point user IDs and passwords . . . . . .
.62 Step 2. Verify the node definitions . . . . . . . . . . . . . . . . . .63
Step 3. Create CSM node groups (optional) . . . . . . . . . . . . . .64 Step 4.
Validate hardware control (required for hardware control) . . . . . .64 Step 5.
Get network adapter information . . . . . . . . . . . . . . .65 Step 6. Set up
Network Installation Manager (NIM) . . . . . . . . . . .66 Step 7. Create
additional NIM network definitions and routes (optional) . . . .68 Step 8.
Create NIM machine definitions . . . . . . . . . . . . . . . .69 Step 9. Create
NIM machine groups (optional) . . . . . . . . . . . . .70 Step 10. Prepare NIM
to add the nodes . . . . . . . . . . . . . . . .71 Step 11. Prepare
customization scripts (optional) . . . . . . . . . . . .71 Step 12. Define
secondary adapter resources for the nodes (optional) . . . .71 Step 13. Add
OpenSSH and OpenSSL software (optional) . . . . . . . . .71 Step 14. Issue the
nim bos_inst operation . . . . . . . . . . . . . . .73 Step 15. Initiate a network
installation of the nodes . . . . . . . . . . .73 Step 16. Monitor and verify
the installation . . . . . . . . . . . . . . .74 Chapter 8. CSM post-installation
tasks . . . . . . . . . . . . . . .77
Getting started with the newly installed cluster . . . . . . . . . . . . .77
Step 1. Verifying that dsh is working on the nodes . . . . . . . . . . .77 Step
2. Checking the status of the nodes . . . . . . . . . . . . . .77 Step 3.
Verifying the power status of the nodes . . . . . . . . . . . .77 Step 4. Verifying
reachability of the nodes . . . . . . . . . . . . . .77 Step 5. Listing
predefined conditions, responses, and dynamic node groups 78 Setting up remote
access manually for AIX . . . . . . . . . . . . . .78 Manually setting up rsh
on AIX nodes . . . . . . . . . . . . . . .78 Manually setting up rsh on Red Hat
Linux nodes . . . . . . . . . . .78 Manually setting up rsh on SuSE or SLES
nodes . . . . . . . . . . .79 Manually setting up OpenSSH on the nodes . . . .
. . . . . . . . .79 Using OpenSSH v3.4.0.5200 for AIX nodes . . . . . . . . . .
. . .79 Using probes . . . . . . . . . . . . . . . . . . . . . . . . .80
Management server probe (ibm.csm.ms) . . . . . . . . . . . . . .80 Hardware
control probe (ibm.csm.HWCtrl) . . . . . . . . . . . . . .80 Understanding the
installation and configuration log files . . . . . . . . .80 Uninstalling CSM .
. . . . . . . . . . . . . . . . . . . . . . .81 Chapter 9. Reconfiguring a cluster . . . . . . . . . . . . . . . . .83
Changing the host name or IP address of the management server . . . . . .83
Notifying CSM of a change to the host name of a managed node . . . . . .83
Removing a node from an existing cluster . . . . . . . . . . . . . . .84 Chapter 10. Backing up and restoring
CSM and ERRM data . . . . . . .85 Using csmbackup to
back up CSM and ERRM data . . . . . . . . . . .85 Using csmrestore to restore
data . . . . . . . . . . . . . . . . . .86 Backing up data on Linux for pSeries
and for versions of CSM earlier than CSM 1.3.2 . . . . . . . . . . . . . . . .
. . . . . . . . . . . .86 Restoring CSM and ERRM data . . . . . . . . . . . . .
. . . . .87 Chapter 11. Maintaining CSM software
. . . . . . . . . . . . . . .89 Contents v
|||||||||||||||||||||||||
Obtaining
CSM updates . . . . . . . . . . . . . . . . . . . . .89 Updating the Management
Server . . . . . . . . . . . . . . . . . .89 Step 1. ″Unwrap″ the tar file . .
. . . . . . . . . . . . . . . . .90 Step 2. Install the software . . . . . . .
. . . . . . . . . . . .90 Step 3. Copy the files to /csminstall . . . . . . . .
. . . . . . . .90 Updating AIX cluster nodes . . . . . . . . . . . . . . . . .
. . .90 Step 1. Copy the updates . . . . . . . . . . . . . . . . . . . .91 Step
2. Update the AIX nodes . . . . . . . . . . . . . . . . . .91 Updating Linux
cluster nodes . . . . . . . . . . . . . . . . . . . .91 Step 1. Obtain the
updates . . . . . . . . . . . . . . . . . . .91 Step 2. Copy the updates to
/csminstall subdirectories . . . . . . . . .92 Step 3. Update the
InstallCSMVersion attribute if needed . . . . . . . .92 Step 4. Update the
Linux nodes . . . . . . . . . . . . . . . . .93 Backing out Updates . . . . . .
. . . . . . . . . . . . . . . . .93 Special Handling for Updates to CSM 1.3.0 .
. . . . . . . . . . . . .94 Appendix
A. Understanding the installation directories and files . . . . .97 Appendix B. Installation scenario:
configuring additional Ethernet or High Performance Switch (HPS) adapters . . . . . . . . . . . . . . .101
Configuring additional Ethernet or HPS adapters . . . . . . . . . . . .101 (1)
Gather adapter information and create an adapter stanza file . . . . .101 (2)
Create a NIM adapter_def resource . . . . . . . . . . . . . .103 (3) Run
nimadapters to create an adapter configuration file for each node included in
the stanza file . . . . . . . . . . . . . . . . . . .103 (4) Run the NIM cust
operation to configure the adapters on the cluster nodes . . . . . . . . . . .
. . . . . . . . . . . . . . .103 Bibliography
. . . . . . . . . . . . . . . . . .
. . . . . . .105 Related information . . . . . . . . . . . . . . . . . . . . .
. .105 Obtaining publications . . . . . . . . . . . . . . . . . . . . . .105
Redbooks . . . . . . . . . . . . . . . . . . . . . . . . .105 Other CSM
information . . . . . . . . . . . . . . . . . . . .105 Getting help from IBM .
. . . . . . . . . . . . . . . . . . . . .106 Finding service information . . .
. . . . . . . . . . . . . . . .106 Calling IBM for help . . . . . . . . . . . .
. . . . . . . . . .106 Contacting CSM development . . . . . . . . . . . . . . .
. . .107 Notices . . . . . . . . . . . . . . . . . .
. . . . . . . . .109 Trademarks . . . . . . . . . . . . . . . . . . . . . . . .
. .110 Glossary . . . . . . . . . . . . . . . . . .
. . . . . . . .113 Index . . . . . . . . . . . . . . . . . .
. . . . . . . . . .121 vi CSM for AIX 5L: Planning and
Installation Guide ||||||||||||||||||||||
About this book This book provides planning,
installation, backup and recovery, and troubleshooting information related to
getting the Cluster Systems Management for AIX 5L product up and running. Attention! v Refer to the Statement of Direction
in the IBM Cluster Systems Management V1.3.2 Release For Announcement (RFA) for
information on support for the eServer 325. v If you are using CSM as part of a
prepackaged Eserver Cluster 1600 solution that you
purchased from IBM or an IBM solutions provider, then all of the prerequisite
hardware is included. See the Eserver
Cluster 1600 documentation resources
listed in the front matter of the CSM
for AIX 5L: Hardware Control Guide for
specific cluster hardware configuration details.Who should use this book This guide is intended for system
administrators who want to use IBM Cluster Systems Management. The system
administrator should have the following skills: v Understanding of most basic
system administration tools and processes. v Skills using most AIX (and if
applicable, Linux) commands and utilities. v Understanding of an AIX-based (and
if applicable, Linux-based) operating system. v Fundamental networking and
distributed computing environment concepts.Typographic
conventions This book uses the following typographic
conventions: Convention Usage bold Bold words or characters represent system
elements that you must use literally, such as: command names, file names, flag
names, and path names. constant width Examples and information that the
system displays appear in constant-width typeface. italic Italicized words or characters represent
variable values that you must supply. Italics
are also used for book titles, for
the first use of a glossary term, and for general emphasis in text. [item] Used to indicate optional items. <Key> Used to indicate keys you press. ISO 9000 ISO 9000 registered quality systems
were used in the development and manufacturing of this product. © Copyright IBM Corp. 2002, 2003 vii
||||||||
Prerequisite and related information
See “Bibliography” on page 105 for v
A list of related publications v How to get help from IBM v Information on
Linux XCAT toolsHow to send your comments Your feedback is important in
helping us to produce accurate, high-quality information. If you have any
comments about this book or any other CSM documentation: v Send your comments
by e-mail to: mhvrcfs@us.ibm.com. Include the book title and order number, and,
if applicable, the specific location of the information you have comments on
(for example, a page number or a table number). v Fill out one of the forms at
the back of this book and return it by mail, by fax, or by giving it to an IBM
representative.To contact the IBM cluster development organization, send your
comments by e-mail to: cluster@us.ibm.com. viii
CSM for AIX 5L: Planning and
Installation Guide
Chapter 1. CSM Overview What is Cluster Systems Management
(CSM)? Cluster Systems Management (CSM)
software provides a distributed system management solution that allows a system
administrator to set up and maintain a cluster of nodes that run the AIX or
Linux operating system. CSM simplifies cluster administration tasks by
providing management from a single point-of-control. CSM can be used to manage
homogeneous clusters of servers that run Linux, servers that run AIX, or
heterogeneous clusters which include both. The management server is the machine that is designated to
install, control, monitor, and maintain the rest of the cluster. Managed nodes are the machines that you define as
belonging to the cluster. How
CSM helps you manage your cluster CSM
enables system administrators to resolve a number of system management challenges.
Some of the tasks you can perform from the management server include: v
Installing and updating software on the cluster nodes v Running distributed
commands across the cluster v Synchronizing files across the cluster v
Monitoring the cluster nodes v Controlling cluster hardware v Managing node
groups v Running diagnostic toolsAdding
nodes and updating software on the cluster nodes From the management server, you can
define nodes and add them to the CSM cluster as well as install the AIX
operating system on the AIX nodes. Running
distributed commands across the cluster As
an administrator, you can run commands in parallel across nodes of the cluster
and gather output using the dsh (distributed shell) command. You can set up dsh to use either rsh (UNIX basic remote shell) or ssh (secure shell). The Distributed Command Execution
Manager (DCEM) graphical user interface allows
you to construct command specifications for running commands on multiple target
machines, while providing real-time status as commands are run. You can perform
the following functions: v Enter the command definition, run time options, and
selected hosts and groups for a command specification v Save command
specifications for future use v Create and modify node groups to use as targets
for a command directly from DCEM.For more information about the DCEM graphical
user interface, see the CSM
for AIX 5L: Administration Guide.
Note: DCEM is not available for
Linux on pSeries nodes. ©
Copyright IBM Corp. 2002, 2003 1 |||||||
||||
Synchronizing files across the
cluster The Configuration File Manager (CFM) provides a repository for
synchronizing configuration files across the nodes of the cluster. CFM works by
storing all shared configuration files in one location on the management server
and automatically propagating changes to these files throughout the cluster. As
a result, you only need to update files once, on the management server, instead
of manually updating all the nodes of the cluster. For more information about
CFM, see the CSM for AIX 5L: Administration Guide. Monitoring
the cluster nodes CSM allows an adminstrator to set up
monitoring for various conditions across nodes or node groups, and designate
specific actions to be run in response to events that occur in the cluster. For
monitoring, CSM uses the Resource
Monitoring and Control (RMC) application,
which is part of RSCT (Reliable Scalable Computing Technology). RMC offers a
comprehensive set of monitoring and response capabilities that lets you detect,
and in many cases correct, system resource problems such as a critical file
system becoming full. You can monitor virtually all aspects of your system
resources and specify a wide range of actions to be taken when a problem
occurs, from simple notification by e-mail to recovery that runs a customized
script. The conditions that you can monitor include v Network reachability v
Power status v Status of applications or daemons running on a node (whether
they are up or down) v CPU, memory, and file system utilization.Actions that
you can designate to be run in response to the occurence of one of these
conditions (an event) include: v Commands that can be run on the management
server or any node of the cluster v Notifications such as logging, e-mailing,
or paging v Recovery actions for cleaning up filesystems that are filling up,
restarting applications that go down, and so on.Predefined conditions and
predefined responses are included with CSM, and you can customize these
conditions and responses to fit their own needs. For more information about
monitoring with CSM, see the CSM
for AIX 5L: Administration Guide.
Controlling cluster hardware The hardware control software of CSM
allows an adminstrator to power on, power off, reboot, bring up the remote
hardware console, and query the nodes of the cluster from a single
point-of-control; the CSM management server. Cluster commands are run from the
management server using the command line interface. For more information about
hardware control with CSM, see the CSM
for AIX 5L: Hardware Control Guide.
Managing node groups As a system administrator, you can
create node groups within the cluster that can be managed and monitored as
distinct entities. You can define node groups as a static set of nodes or as a
dynamic set of nodes. Static node groups are created by explicitly specifying
node names, node group names, or both. When you define a dynamic node group,
you can designate a particular characteristic for those nodes. For example, you
can create a node group for a specific type of hardware and then 2
CSM for AIX 5L: Planning and
Installation Guide
monitor
that node group. If a new machine of that hardware type is added to the
cluster, monitoring will automatically start for that machine. For more information
about creating and using node groups, see the CSM
for AIX 5L: Administration Guide Running
diagnostic tools CSM includes a set of diagnostic probes that adminstrators can use to check
the health of specific software functions and identify the cause of system
problems. You can set up these probes to run periodically, or automatically as
a response to a condition occurring in the system. CSM also allows you to write
their own probes. For more information about using the CSM probes, see CSM for AIX 5L: Administration Guide. Communicating
with CSM CSM offers you several options for
issuing commands to the cluster: v Command line interface v Distributed Command
Execution Manager (DCEM) v Web-based System Manager v SMITCommand line interface CSM includes command line interfaces
for all CSM functions. The command line interface allows you to access all the
resources in the system, the attributes of those resources, and state values.
It also allows you to query and control the nodes, file systems, CPU and memory
statistics, global cluster parameters, and so on. For more information about
the CSM commands, see the CSM
for AIX 5L: Command and Technical Reference.
Distributed Command Execution
Manager (DCEM) For information about the
Distributed Command Execution Manager (DCEM), see “Running distributed commands
across the cluster” on page 1 and the CSM
for AIX 5L: Administration Guide.
DCEM is not available for Linux on pSeries nodes. Web-based System Manager The Web-based System Manager is a
graphical user interface application for managing and monitoring a cluster. It
provides point-and-click control of objects as an alternative to learning and
using AIX commands. For more information about using the Web-based System
Manager, see the CSM for AIX 5L: Administration Guide. SMIT
SMIT panels are currently provided
with CSM for installation, setup, and hardware control functions. SMIT panels
for the remaining CSM functions will be added over time. What’s new or changed in CSM 1.3.2
Additional hardware for cluster nodes Additional
hardware is supported in this release. For a list of the new hardware servers
that CSM supports, see “Cluster node requirements” on page 7. Linux on pSeries support CSM now supports certain IBM Cluster
pSeries hardware models for Linux nodes. Chapter
1. CSM Overview 3 ||||||||||
Use of AIX installation and software
maintenance tools CSM now uses standard AIX
installation tools to install software and add AIX nodes. AIX provides
Web-based System Manager (Websm) support as well as System Management Interface
Tool (SMIT) and command line interfaces. The following changes to commands and
node attributes occur in the this release of CSM: v The installms command, which has been used in
prior releases for AIX nodes, is no longer supported for AIX. v The copycsmpkgs command is now only used for Linux
nodes. v The CSM node attribute InstallCSMVersion
is no longer used and does not
require being set for AIX nodes. InstallCSMVersion
is still required for Linux nodes.If
you have defined CSM nodes using an earlier version of CSM you might want to
remove the value for the InstallCSMVersion
attribute, which is no longer used
by AIX nodes and is not required. To erase the value for all your AIX nodes,
issue the following command. chnode
-N AIXNodes InstallCSMVersion= See
“Step 9. Install CSM management server software” on page 24. User customization scripts for AIX
nodes CSM for AIX now supports the
automatic running of user-provided customization scripts when you update or
install cluster nodes. Optional steps are added to some of the procedures in
this book to indicate how to use the support. For complete information, see CSM for AIX 5L: Administration Guide. Secondary
adapter configurations CSM
on AIX supports the configuration of additional (secondary) Ethernet or High
Performance Switch (HPS) adapters on the nodes of the CSM cluster. These
adapters are in addition to the install adapter that is used for remote network
installation of the node, which is automatically configured during the node
installation. For a scenario on how to set up secondary adapter configurations,
see “Configuring additional Ethernet or HPS adapters” on page 101. For complete
information. see CSM for AIX 5L: Administration Guide. Enhanced
backup and restore features CSM
provides two new commands for backing up and restoring CSM: v The csmbackup command copies vital CSM data from
the management server and stores the data in a specified directory. The command
backs up a CSM management server in case of a hardware problem, or if you are
setting up the management server on another machine. v The csmrestore command restores the files that are
copied by csmbackup into the specified directory.See
Chapter 10, “Backing up and restoring CSM and ERRM data,” on page 85. 4
CSM for AIX 5L: Planning and Installation
Guide ||||||||||||||||||
|||||||||||||||||||||||
Chapter 2. Planning for Cluster
Systems Management The Cluster Systems Management (CSM)
planning and installation process helps you as a system administrator set up
the IBM Cluster Systems Management for AIX 5L. Read this chapter before you
install CSM. CSM options: Before you can add nodes to the CSM
cluster, you must ensure that the AIX 5L operating system is installed on the
machine that you use for the management server. After you set up the management
server, you can add nodes to the cluster in one of two ways: v Add the CSM node
that already has the AIX operating system installed, OR v Install the AIX
operating system as well as add the CSM node.Managing
Linux nodes: You can manage Linux cluster nodes
from an AIX management server; however, you cannot install the Linux operating
system from an AIX management server. Linux must be installed on the node
before adding it to the cluster. Hardware
control: CSM allows you to set up a cluster
with or without hardware control. Some typical CSM hardware
functions you can perform from the management server include: v Power nodes on
and off v Reboot nodes v Query the power status of nodes v Open a console to a
cluster node. v Power CECs on and off. v Display LCD information for CECs v
Display LCD information for AIX nodesThis chapter provides an overview of some of
the hardware requirements for hardware control. It assumes that your hardware
has already been set up. For detailed information about hardware control, see
the CSM for AIX 5L: Hardware Control
Guide. Parallel
Systems Support Program (PSSP) and CSM non-compatibility PSSP must not be installed on the
management server or any of the nodes in the cluster. Coexistence between PSSP
and CSM is not supported. Understanding
CSM hardware requirements The
following topics describe hardware requirements for the management server,
cluster nodes, and hardware control. Management
server requirements v The
machine you use for your management server must have a CD-ROM drive or
equivalent (for example, a DVD-ROM or DVD-RAM drive). v The management server
must be a workstation, capable of running AIX 5L Version 5.2. © Copyright IBM Corp. 2002, 2003 5
||||||||||||
v A sufficient number of network
adapters are required to accommodate the required management, cluster and
public VLANs. For information on the network options and requirements, see the CSM for AIX 5L: Hardware Control
Guide. v On the management server, a
minimum of 1024MB of memory and 120MB of disk space are required for installing
CSM. Additional disk space on the management server is required to support
installation of the AIX operating system and CSM on the managed nodes. (Typically,
for every version of AIX that you have installed, you need at least 2.0 GB of
storage.)If you are using CSM as part of a prepackaged eServer Cluster 1350
solution that you purchased from IBM or an IBM solutions provider, all of the
prerequisite hardware is included. Cluster 1350 hardware and networking are
delivered preconfigured for using CSM Using
a Logical Partition (LPAR) as a CSM management server CSM 1.3 for AIX supports a logical
partition (LPAR) as a CSM management server with the following limitations and
considerations. Depending on your cluster configuration and needs, you can
choose to use an LPAR as the CSM management server. However, it is important to
understand the limitations and considerations to decide if an LPAR CSM
management server is appropriate for your cluster. Limitations & Considerations of
LPAR management server: If
you use an LPAR as a CSM management server, consider the following limitations.
Note that these limitations apply only if the CSM management server is an LPAR
and not a separate physical machine: 1. The CSM management server can be
brought down inadvertently by a user on the HMC who deactivates the LPAR. Even
if a user does not have access to the CSM management server, a user with access
to the HMC can power off the management server or move resources such as CPU or
I/O from the LPAR. 2. If the firmware needs to be upgraded, the LPAR management
server might also go down when the system is quiesced. However, bringing the
CEC back up returns the system to normal. 3. There is no direct manual hardware
control of the CSM management server. You must use the HMC for power control of
the management server. 4. In many cases a physically separate CSM management
server can be safer than an LPAR because an LPAR management server is part of a
CEC that can go down during a hardware or power failure. As a result, you can
lose access to the management server. 5. An LPAR management server cannot have
an attached display. This limitation can affect the performance of your CSM GUIs.
6. In machines such as the p690, you can assign a CD-ROM drive to the
management server LPAR. 7. Do not define an LPAR management server as a managed
node. 8. A cluster that is installed and configured can still function even if
the management server goes down. For example, cluster applications can continue
to run, and nodes in the cluster can be rebooted. However, tasks including
monitoring, automated responses for detecting problems in the cluster, and
scheduled file and software updates cannot occur while the management server is
down. 9. If the cluster contains a 9076 SP Node or 7026 server, you cannot
define an LPAR management server for the cluster. 6
CSM for AIX 5L: Planning and
Installation Guide ||||||||||
Cluster node requirements You can use the following hardware
for the cluster nodes, as long as they are not part of a PSSP-managed cluster. Hardware support Supported hardware for AIX nodes v IBM
Cluster pSeries™615
(p615) v IBM Cluster pSeries 630 (p630) v IBM Cluster pSeries 650 (p650) v IBM
Cluster pSeries 655 (p655) v IBM Cluster pSeries 670 (p670) v IBM Cluster
pSeries 690 (p690) v IBM 9076 SP Nodes (feature numbers 2050, 2051, 2052, 2053,
2054, 2056, 2057, and 2058) v IBM p660 servers (models H80, M80, 6H0/6H1, 6M1,
and pSeries 660 or p660) v IBM SP Expansion I/O Unit (feature 2055)Note: For hardware control, the IBM p660
server models are referred to as p660 servers in this and other CSM
publications. For information, see CSM
for AIX 5L: Hardware Control Guide.
Supported hardware for Linux nodes: The following hardware is
supported for the Linux nodes on the xSeries, IntelliStation, or BladeCenter
hardware of the AIX cluster: xSeries
nodes for Linux v IBM
xSeries 330 (x330) v IBM xSeries 335 (x335) v IBM xSeries 342 (x342) v IBM
xSeries 345 (x345) v IBM xSeries 360 (x360) v IBM xSeries 440 (x440) v IBM
xSeries 445 (x445) v IntelliStation 6221. Hardware is controlled for the
IntelliStation 6221 through the APC MasterSwitch.eServer BladeCenter for Linux v BladeCenter:
HS20-8677 Blade Server. v BladeCenter: HS20-8678 Blade Server v BladeCenter:
HS20-8832 Blade ServereServer 325 (e325) for Linux v IBM
eServer 325Note: The eServer 325 is planned to be
supported in CSM 1.3.2 but is not fully documented in this initial release of
the book. pSeries on Linux Chapter 2. Planning for Cluster
Systems Management 7 ||
|||||||||||||||||||||
v IBM Cluster pSeries 615 (p615) v IBM
Cluster pSeries 630 (p630) v IBM Cluster pSeries 650 (p650) v IBM Cluster
pSeries 655 (p655)Linux distribution packages and xSeries,
IntelliStation, and BladeCenter The
following table shows the distributions and xSeries, IntelliStation, or
BladeCenter hardware supported by CSM for Linux 1.3.1 and later nodes in your
AIX cluster. For BladeCenter 8678 and 8832 models, see the following web site: http://www.pc.ibm.com/us/eserver/xseries/bladecenter_family.html
An X means it is supported and a
blank means that it is not supported. Table
1. Linux distributions and supported xSeries, IntelliStation, or BladeCenter
hardware for nodes in an AIX cluster Linux
Distribution x330 x335 x342 x345 x360 x440 x445 BladeCenter (8677)
IntelliStation Model 6221 Red Hat 7.2 X
X X Red Hat 7.3 X X X X X X X Red Hat AS 2.1 X X X X X X X X Red Hat 8.0 X X X X X Red Hat 9 X X X SuSE 8.0 X X X X SuSE 8.1 X X X X X SuSE SLES 7 (7.2) X X X X X SuSE SLES 8 (8.1) X X X X X X X Linux distribution packages and
pSeries hardware The following table shows the
distributions and pSeries hardware supported by CSM for Linux 1.3.2 in an AIX
cluster. An X means it is supported and a blank means that it is not supported.
Table 2. Linux distributions and
supported pSeries hardware for nodes in an AIX cluster Linux Distribution p615 p630 p650
p655 SuSE SLES 8 (8.1) X
X X X Memory and disk space for nodes On each managed node, a minimum of
256MB of memory and 20MB of disk space is required for CSM, and the required
amount of additional disk space for the operating system and RPM™ packages
that you choose to install. Hardware
installation It is assumed that your hardware is
already set up before you begin the installation process. If you have not set
up your hardware, see the CSM
for AIX 5L: Hardware Control Guide for
the hardware requirements and set up tasks. Hardware
control requirements CSM hardware control software
provides remote hardware control functions for CSM cluster nodes from a single
point of control. The management server can be connected to cluster nodes and
external networks using various configurations of IBM and non-IBM hardware and
software that meet 8 CSM
for AIX 5L: Planning and Installation Guide ||||||||||||||||||||||||
|||||||
the
CSM hardware control architecture requirements. You can use commands to to
request node power status, reboot, power on and off functions, and perform
other functions. You can also use commands to communicate with console server
hardware to open a console window for a node on the CSM management server.
Console servers should be on the management virtual LAN (VLAN), which connects
the management server to the cluster hardware, and connected to node serial
ports. Each SP frame connects to the CSM management server through an RS-232
line cabled from the frame supervisor to a tty port on the management server.
The frame supervisor requires a daisy-chain connection to the node supervisor
for each server in the frame. Each p660 server connects to the CSM management
server through its own RS-232 line cabled from its CSP serial port to a tty
port on the management server. For multiple SP Nodes and p660 servers,
additional tty extender adapters must be connected to the management server.
Depending on the type of hardware, the hardware control point for the
management server is one of the following: v IBM Hardware Management Console
(HMC) for pSeries hardware (also depends on the firmware supported for HMC) v
Port connection on the SP frame supervisor v p660 CSP serial server v Remote
Supervisor Adapter (RSA) for xSeries hardware v APC® MasterSwitch
for IntelliStation v Management Module for BladeCenter v Baseboard Management
Controller on eServer 325 hardwareFor more details about the hardware and
networking requirements for CSM hardware control, see the CSM for AIX 5L: Hardware Control
Guide. Understanding
CSM licensing requirements The
following topics describe options for CSM licensing requirements. CSM Try and Buy option You can try CSM and clustering at no
charge for 60 days under the Try & Buy option.You can use all functions of
CSM for 60 days, after which CSM will no longer function. When you purchase and
receive a full production license and key for CSM, and accept its IPLA License
Agreement, you can use CSM for production purposes. CSM configuration data
stored during Try & Buy will remain available for later production use. CSM full license To use CSM for production purposes,
you’ll need to purchase a full CSM production license and key, and accept its
IPLA License Agreement. CSM configuration data stored during your Try & Buy
period, will remain available for production use. Orders can be placed by calling
IBM.COM, Americas at 1-800-IBM-CALL 1-800-426-2255. For procedural information
about licensing options for CSM, see “Step 13. Accept the CSM license” on page
27. Chapter 2. Planning for Cluster
Systems Management 9 |||||||||||
Understanding CSM software
requirements Installing IBM Cluster Systems
Management involves installing both IBM CSM software and prerequisite non-IBM
software. Before installing CSM, gather all the necessary software, including
CSM, open source prerequisites, software updates, and, optionally, software
provided on the Linux distribution CD-ROM. Most of the required software is
available from AIX, CSM, or the Linux product media, but you need to download
some software from the Internet. If you plan on using AIX 5L for POWER Version
5.1 with the 5100–03 Recommended Maintenance package on the nodes of your
cluster, note that the management server must have AIX 5.2 installed. Note: Once you have installed the
management server, you can refer to the README file (/opt/csm/README/csm.README) on the CD-ROM or the tar file that
you have downloaded during the installation procedure for additional service
requirements. See “Step 9. Install CSM management server software” on page 24.
The following topics describe software requirements for a CSM cluster. 1. AIX 5.2 This AIX operating system product
media is available from IBM. You must use the media to install the machine that
you plan to use as the CSM management server. Required
CSM release for AIX 5.2: You
can only install CSM 1.3.2 or higher on the AIX 5.2 machine that you use as the
management server. 2. AIX version 5.1 with the 5100–03
Recommended Maintenance package (only required for AIX version 5.1) If you are adding AIX 5.1 nodes to a
cluster, you must update the nodes with the 5100-03 or higher Recommended
Maintenance package. The AIX 5.1 product media and updates are available from
IBM. 3. CSM for AIX product software Software available on AIX 5.2 media The following CSM files are
automatically installed when you install AIX on your system. These files are
located on CD-ROM 1. v csm.core v csm.client v csm.dsh v csm.msgThe following
CSM files are shipped with AIX 5.2, but are not automatically installed. They
are located on CD-ROM 2. v csm.server v csm.diagnostics v csm.gui.dcem v
csm.gui.websm 10 CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||
Software available on AIX Version
5.1 with the 5100-03 Recommended Maintenance package For AIX 5L for POWER Version 5.1
with the 5100-03 Recommended Maintenance package, the following files are
automatically installed with AIX: v csm.client 1.1.2 v csm.core 1.1.2The
following file is not automatically installed (optional): v csm.diagnostics 1.1.24. Required open source software
shipped on the AIX product media The
open source software, shipped on the CSM for AIX 5L Version 5.2 CD-ROM includes
the following files. v conserver v expect v tcl v tkNote: No open source software is shipped
with CSM for AIX 5L for POWER Version 5.1 with the 5100-03 Recommended
Maintenance package. 5. Other required open source
software Open Source Software Location openCIMOM-0.7-4.aix5.1.noarch.rpm
http://www.ibm.com/servers/aix/products/aixos/linux/download.html (IBM AIX
Toolbox), or the IBM AIX toolbox CD-ROM Autoupdate (used when managing Linux
nodes only. See “Step 2. Copy the Linux CSM packages and other prerequisite
software” on page 53.) http://freshmeat.net/projects/autoupdate (Select the
link under RPM package, then download the
autoupdate-*.noarch.rpm) 6.
Product software updates and fixes CSM
updates and fixes (APARs) are available from
http://techsupport.services.ibm.com/server/cluster/fixes. 7. Linux distribution software (only
required for Linux nodes) When
you add nodes to a CSM cluster managed by an AIX management server, you must
install the xSeries, IntelliStation, or
BladeCenter Linux nodes with
one of the following Linux distributions: v Red Hat Linux 7.2 v Red Hat Linux
7.3 v Red Hat Linux 8.0 v Red Hat Linux 9 v Red Hat Linux AS 2.1 v SuSE Linux
8.0 v SuSE Linux 8.1 v SuSE SLES Linux 7 (7.2) v SuSE SLES Linux 8 (8.1) Chapter 2. Planning for Cluster
Systems Management 11 ||||||||||| || |||
When
you add nodes to a CSM cluster managed by an AIX management server, you must
install the Linux on pSeries nodes with the following Linux
distributions: v SuSE SLES Linux 8 (8.1)8.
CSM for Linux product software (only required for Linux nodes) The following files are shipped with
the CSM for Linux CD-ROM. They are needed for managing Linux nodes from an AIX
management server. v csm.client 1.3.2 v csm.core 1.3.2 v csm.diagnostics 1.3.2
v rsct.core 2.3.1 v rsct.core.utils 2.3.1 v rsct.basic 2.3.1 v src 1.2.0CSM packages needed for GPFS and CSM
coexistence This section only applies if you
manage Linux nodes from an AIX management server. Because GPFS and CSM rely on
common enabling technologies in RSCT and SRC, it is important when you use GPFS
and CSM together that you install the latest RSCT and SRC RPM images. Select
and install the latest RSCT and SRC RPM images from either the GPFS or CSM
distribution. For example, if the CSM distribution contains the following: v
rsct.basic–2.3.1* v rsct.core–2.3.1* v rsct.core.utils–2.3.1* v src–1.2.1*and
GPFS distribution contains the following: v rsct.basic–2.2.1* v
rsct.core–2.2.1* v rsct.core.utils–2.2.1* v src–1.1.1*select and install the
RSCT and SRC images from the CSM distribution. Note: GPFS requires specific kernel
levels. See the GPFS documentation for more information. 9. Open source software shipped on
Linux product media (only required for Linux nodes) These packages are required when
adding Linux nodes to the cluster. Red
Hat Linux software The following required non-IBM
software is available on the Red Hat Linux 7.2 CD and is used by CSM: v
freetype–2.0* v libstdc++–* v pdksh–* 12 CSM for AIX 5L: Planning and
Installation Guide ||||||||||||||||||||||||||| ||||
v perl–5* v rdist–* v nfs–utils–* v
dhcp–* v expect–5.32* v tcl–8.3* v tk–8.3* v XFree86–libs–4.1* v
perl–libnet–1.07* The following required non-IBM software is available on the
Red Hat Linux 7.3 CD and is used by CSM: v freetype–2.0* v libstdc++–* v
pdksh–* v perl–5* v rdist–* v nfs–utils–* v dhcp–* v expect–5.32* v tcl–8.3* v
tk–8.3* v XFree86–libs–4.2* v perl–libnet–1.09* The following required non-IBM
software is available on the Red Hat Linux 8.0 CD and is used by CSM: v
freetype–2.1* v pdksh–* v perl–5* v rdist–6* v nfs–utils–* v dhcp–3* v
expect–5.38* v tcl–8.3* v tk–8.3* v XFree86–libs–4.2* The following required
non-IBM software is available on the Red Hat Linux 9 CD and is used by CSM: v
freetype–2.1* v pdksh–* v perl–5* v rdist–6* v nfs–utils–* v dhcp–3* v
expect–5.38* Chapter 2. Planning for Cluster
Systems Management 13 ||||||||||||||||||||||||||||||||||||||||||||
v tcl–8.3* v tk–8.3* v
XFree86–libs–4.3* v compat-libstdc++* The following required non-IBM software
is available on the Red Hat Linux AS 2.1 CD and is used by CSM: v perl-5* v
nfs-utils-* v pdksh-* v dhcp-* v rdist-6* v expect-5.32* v tcl-8.3* v tk-8.3* v
XFree86-libs-4.1* v freetype-2.0* v perl -libnet-1.07*SuSE Linux software The following required non-IBM
software is available on the SuSE Linux 8.0 CD and is used by CSM: v pdksh-* v
perl-5* v nfs-utils-* v rdist-6.1.5-429* v tcl-8* v tk-8* v expect-5.34-63* v
expat-* v termcap 2.0.8* v rsync-* v perl-XML-Parser-* v perl-XML-Simple-* v
perl-DBI-* v dhcp-server-* v dhcp-base-* v perl-libnet-1.09* v rsh-server-* v
gppshare-* v xf86* v freetype2* The following required non-IBM software is
available on the SuSE Linux 8.1 CD and is used by CSM: v perl-5* v nfs-utils-* 14
CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||
|||||||||||||||||||||||||
v pdksh-* v dhcp-base* v dhcp-server*
v rdist-6.1.5-524* v expect-5.34-178* v expat-* v tcl-8* v tk-8* v xf86* v
freetype2* v rsync-* v rsh-server-* v telnet-server-* v termcap-* v perl-DBI-*
v perl-XML-Parser-* v perl-XML-DOM-* v perl-XML-RegExp-* v perl-HTML-Tagset-* v
perl-HTML-Parser-* v perl-URI-* v perl-libwww-perl-*SuSE SLES Linux software The following required non-IBM
software is available on the SuSE SLES 7 (7.2) CD and is used by CSM: v pdksh-*
v perl-5* v nfs-utils-* v dhcp-* v tcl-8* v tk-8* v expat-* v termcap-* v
rsync-* v dosftools-* v gppshare-* v xf86* v freetype2*The following required
non-IBM software is available on the SuSE SLES Linux 8 (8.1) CD and is used by
CSM: v perl-5* v nfs-utils-* v nfs-server v pdksh-* Chapter 2. Planning for Cluster
Systems Management 15 |||||||||||||||||||||||| ||||||||||||||||||||
v dhcp-base* v dhcp-server* v
rdist-6.1.5-543* v expect-5.34-192* v termcap-* v expat-* v tcl-8* v tk-8* v
xf86* v freetype2* v rsync-* v Glibc v libstdc++ v termcap v rsh-server-* v
perl-XML-Parser-* v perl-HTML-tagset v perl-HTML-Parser v perl-URI v perl-libwww-perl10. Software required to support the
Equinox Ethernet Serial Provider (ESP) console When you use the Equinox ESP console
server, the bos.uucp.net fileset must be installed from the
AIX CD. The rconsole command communicates with the
console server hardware to open a console window for a node on the CSM
management server. v bos.net.uucp (Required for using ESP on xSeries nodes with
an AIX management server in a mixed CSM cluster.)The Equinox ESP console device
requires the installation of software and drivers that are shipped with the
device. The software is only required if you are using an ESP console server to
connect to the consoles of xSeries, Intellistation, or eServer 325 Linux nodes.
Once these are installed, the device can be configured using the espcfg command. See the ESP device
installation instructions for details at the following web site: http://www.equinox.com/
Hardware_Manuals192.html To run the ESP software on an AIX
management server, the /etc/uucp/Devices
file must be modified to include the
tty devices hosted by the ESP. The tty device names are returned by the espcfg command in the form /dev/ttyesp_numeesp_port_num. For example, port 3 attached to
ESP number 1 is named /dev/tty01e2 . (Note that on the ESP, the tty
ports are zero-based, so the port labeled 3 on the actual ESP device is
represented as tty port 2). If the ESP port speeds are configured at 9600 bps,
the entry in the /etc/uucp/Devices file for this port is as follows: Direct /dev/tty01e2 - 9600 direct An entry needs to be in the file for
each tty device hosted by the ESP. 16
CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||||||||||||||||||||||||||
11. OpenSSH and prerequisite
software (only required when using OpenSSH as the remote shell) The OpenSSH software is available on
the IBM AIX Bonus Pack - AIX 5L for Power 5.2. The minimum list of filesets
that should be installed (assuming the desired language is English) is: v
openssh.base v openssh.license v openssh.man.en_US v openssh.msg.en_US v
openssh.msg.EN_USThe OpenSSL software is a prerequisite of OpenSSH software.
The following RPM package is available on the AIX Toolbox for Linux
Applications for Power Systems: v opensslHost
name resolution When you define nodes, general
attributes define the host name of the network to which the management server
is connected. CSM uses the host name for network communications among the nodes
in the CSM cluster. You can use a short host name or a long host name with CSM,
but you must make sure that the resolution of the host name for the CSM cluster
complies with the following guidelines: v If the Hostname resolves to the short host name, all
hosts must be configured so that the short name is returned from the gethostname application programming interface
(API) and the hostname command. All IP addresses must
resolve to the short host name first. All references to the nodes in the CSM
database must make use of the short host name. v If the Hostname resolves to the long host name, all
hosts must be configured so that the long name is returned from the gethostname API and the hostname command. All IP addresses must
resolve to the long host name. All references to the nodes in the CSM database
must make use of the long host name.If you switch between using short host
names or long host names, you must ensure that all host names comply with these
guidelines. Chapter 2. Planning for Cluster
Systems Management 17 ||||||||||||||||||||||||||||||
18
CSM for AIX 5L: Planning and
Installation GuideThis chapter provides step-by-step
instructions for installing a CSM management server. Before you begin the
installation and set up tasks, read these instructions carefully. For details
about the commands that are used for installation, see CSM for AIX 5L: Command and
Technical Reference. You can use standard AIX tools and
procedures to install CSM and required open source software. The tools that AIX
provides includes Web-based System Manager (WebSM) support as well as the
System Management Interface Tool (SMIT), and a command line interface. Before you install the management
server Ensure that the machine that you use
for the CSM management server already has AIX 5L for POWER Version 5.2
installed. Web site access: This procedure describes downloading
software products from various web sites. If the machine that you use for your
management server does not have internet access, you need to download to
another machine (AIX, Linux, or Windows), and transfer the files to your
management server. Summary of the installation steps __ 1. “Step 1. Check management
server software requirements” __ 2. “Step 2. Register host names of nodes and
management server” on page 20 __ 3. “Step 3. Update the $PATH and $MANPATH
variables” on page 20 __ 4. “Step 4. Create the /csminstall file system
(optional)” on page 20 __ 5. “Step 5. Download CSM Updates” on page 21 __ 6.
“Step 6. Download Open Source Software” on page 21 __ 7. “Step 7. Verify that
the prerequisite software is installed” on page 22 __ 8. “Step 8. Apply updates
to CSM filesets that have already been installed with AIX” on page 24 __ 9.
“Step 9. Install CSM management server software” on page 24 __ 10. “Step 10.
Apply management server software updates” on page 24 __ 11. “Step 11. Check the
remote shell attribute” on page 25 __ 12. “Step 12. Install OpenSSH and OpenSSL
(optional)” on page 26 __ 13. “Step 13. Accept the CSM license” on page 27 __
14. “Step 14. Copy CSM files into the /csminstall subdirectories” on page 28 __
15. “Step 15. Set the cluster ID (optional)” on page 28 __ 16. “Step 16. Verify
the installation” on page 28Step
1. Check management server software requirements Before continuing with the
installation, understand the software requirements for the management server.
See Chapter 2, “Planning for Cluster Systems Management,” on page 5 for
information about management server requirements. © Copyright IBM Corp. 2002, 2003 19
|||||||||||||||||||||||||||||||||||||||||||
Step 2. Register host names of nodes
and management server Register
the host names of the following with the nameserver, or add them to the /etc/hosts file on the management server. v
Management server v Nodes that are being defined to the cluster v Hardware
Control: – Hardware management console (HMC) host name for pSeries hardware –
Remote Supervisor Adapter (RSA) host name for xSeries hardware – APC
MasterSwitch host name for Intellistation – Management module host name for
BladeCenterStep 3. Update the $PATH and
$MANPATH variables Add /opt/csm/bin to the root user’s $PATH variable on
the management server: export PATH=$PATH:/opt/csm/bin To access the CSM man pages, add /opt/csm/man to the root user’s $MANPATH variable
on the management server: export
MANPATH=$MANPATH:/opt/csm/man To
verify that this step completed successfully, issue the following commands: echo $PATH echo $MANPATH Note: The examples above only show how to
change the $PATH and $MANPATH variables in the current login session. To
permanently change them, edit your login environment. Step 4. Create the /csminstall file
system (optional) IBM suggests that you create a
separate file system called /csminstall
on the management server to store
the files that are to be used with CSM. The size of this file system depends on
your particular cluster. The following list provides estimates of the space
that you might require for some basic categories of files that you can store in
/csminstall: v Space required for CSM software,
configuration files, and so on – 120 MB v Space required for AIX operating
system installation resources – 2.0 GB (per level of AIX). It is not necessary
to store these resources in the /csminstall
file system. v Additional space
required if adding Linux nodes to the cluster – 120 MB v Additional space required
to store Linux distribution RPMs – 1.5 GB (per level of Linux distribution)You
can create the /csminstall file system as part of the rootvg or in its own volume group. The
following examples illustrates how to create /csminstall
using the root volume group. To
create a 1 GB file system called /csminstall, do the following: 20
CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||
|||||||||||||||||||||
If using: Do this: Command line Issue the AIX crfs command: crfs -v jfs -g rootvg -m /csminstall
-a size=1024M If you do not create the /csminstall directory, CSM creates it when you
install the management server. In this case, however, it will simply be created
as a subdirectory of / (root)
file system and might not contain enough space for your intended use. SMIT
Issue the crfs command via SMIT. The fastpath is crfs. For example: smit crfs Web-based System Manager Use the File Systems plug-in to create the new file
system. After you have created /csminstall, you must mount it, as follows: mount /csminstall Step 5. Download CSM Updates You can obtain the latest CSM
software updates by downloading the CSM updates from the CSM support web site.
The management server must always be installed with the latest version of CSM
filesets. To download the latest updates, go to the following web site and
select CSM updates with the correct version.release.modification.fix
level (for example, 1.3.2.0): http://techsupport.services.ibm.com/server/cluster/fixes
If you are downloading directly to
the management server, put the tar file in a temporary directory, (for example,
/tmp/csm). If you download the file to a
different machine, copy the tar file to the management server before you
″unwrap″ it. Use the tar command to unwrap the tar file. For example, assuming
the name of the file is csm-aix-1.3.2.tar.gz
and that it is in the /tmp/csm directory, issue the following
commands: gunzip csm-aix-1.3.2.tar.gz tar
-xvf csm-aix-1.3.2.tar The command creates a set of
subdirectories under /tmp/csm and locates the files in the
appropriate subdirectories. When you apply any updates, ensure that you check
the CSM support web site for the most current information on required
prerequisites and information on any special handling that might be required. Step 6. Download Open Source
Software Downloading openCIMOM (required for hardware control) This software is required to support
CSM hardware control functions. If you do not use the CSM hardware control
support, you do not need openCIMOM. Download OpenCIMON from the following web
site: http://www-1.ibm.com/servers/aix/products/aixos/linux/download.html
You download to a temporary
directory like the following: /tmp/csm/RPMS/ppc
Chapter 3. Installing the Management
Server 21 ||||||| |||| | ||||||||||||||||||| |||||||||||||
Copy
the file to a temporary directory on the management server. You can use the rpm command to install the file. For
example, assuming the name of the RPM package is openCIMOM-0.7-4.aix5.1.noarch.rpm, issue the following command: rpm -i
openCIMOM-0.7-4.aix5.1.noarch.rpm You
can also obtain openCIMOM on the IBM AIX Toolbox CD_ROM. Downloading autoupdate (required for
CSM Software Maintenance System (SMS)) This
software is required to support the CSM Software Maintenance System (SMS)
feature that is available for updating software on Linux nodes. You only need
the software if you are adding Linux nodes to you CSM cluster. You can download
the autoupdate software from the following web
site: http://freshmeat.net/projects/autoupdate
To download the software, select the
link under ″RPM package:″, then download autoupdate<release>.noarch.rpm (for example, autoupdate-5.2.5-1.noarch.rpm). Copy the RPM to a temporary
directory, for example /tmp/csm/RPMS/ppc. You do not have to install the RPM
on the management server. The autoupdate
RPM is required only when you add
Linux nodes to the cluster. You can postpone downloading the autoupdate RPM until you are ready to follow
the procedure to add the Linux node. See Chapter 6, “Adding Linux nodes to the
cluster,” on page 53. You can also download the autoupdate RPM open source software from other
sites on the web. Step 7. Verify that the prerequisite
software is installed When
AIX is installed, the following CSM base filesets are also automatically
installed: v csm.core v csm.client v csm.dshIf the filesets are not available,
use AIX CD-ROM #1 to reinstall them. To verify that the CSM filesets are
installed, use the lslpp command as follows: If using: Do this: Command line Issue the lslpp command, as follows: and lslpp -L csm* SMIT Issue the lslpp command using SMIT. The fastpath is
list_installed_sw. For example: smit
list_installed_sw Web-based System Manager Use the Software plug-in to list installed software. The following is sample command
output for the lslpp command. In this sample, it shows
that the required CSM filesets are installed at the 1.3.1.0 level: Fileset Level State Type
Description (Uninstaller)
----------------------------------------------------------------------------
csm.client 1.3.1.0 A F Cluster Systems Management 22
CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||||||||||||||||||| |
||||||
Client csm.core 1.3.1.0 A F Cluster Systems Management
Core csm.dsh 1.3.1.0 A F Cluster Systems Management Dsh Checking for the required rsct.core
fileset: CSM requires RSCT software. To
check for the correct version of RSCT software, determine that the installed
version of rsct.core is version 2.3.1 or later. To verify
the required level of rsct.core, use the lslpp command as follows: If using: Do this: Command line Issue the lslpp command, as follows: and lslpp -L rsct* SMIT Issue the lslpp command using SMIT. The fastpath is
list_installed_sw. For example: smit
list_installed_sw Web-based System Manager Use the Software plug-in to list installed software. The following is sample command
output for the lslpp command. In this sample, it shows
that the required rsct.core filesets are installed at the
2.3.1.0 version or later: Fileset Level State Type
Description (Uninstaller)
----------------------------------------------------------------------------
rsct.core.auditrm 2.3.1.0 C F RSCT Audit Log Resource Manager rsct.core.errm
2.3.1.1 A F RSCT Event Response Resource Manager rsct.core.fsrm 2.3.1.1 A F
RSCT File System Resource Manager rsct.core.gui 2.3.1.0 C F RSCT Graphical User
Interface rsct.core.hostrm 2.3.1.2 A F RSCT Host Resource Manager rsct.core.rmc
2.3.1.2 A F RSCT Resource Monitoring and Control rsct.core.sec 2.3.1.2 A F RSCT
Security rsct.core.sensorrm 2.3.1.0 C F RSCT Sensor Resource Manager
rsct.core.sr 2.3.1.0 C F RSCT Registry rsct.core.utils 2.3.1.2 A F RSCT
Utilities RSCT updates are available from the
AIX CD-ROM or by downloading updates from the following AIX support web site: https://techsupport.services.ibm.com/server/aix.fdc
Checking Java software: CSM requires that Java filesets be
installed on the management server. The required filesets are listed in the
following example. Issue the following command to check that Java 1.3.1 version
or higher has been installed: lslpp
-L Java* The following is sample command
output for the lspp command. In this sample, it shows
that the Java filesets are installed at the 1.3.1.2 version: Fileset Level State Type
Description
-------------------------------------------------------------------------------
Java131.rte.bin 1.3.1.2 C F Java Runtime Environment Executables
Java131.rte.lib 1.3.1.2 C F Java Runtime Environment Libraries Chapter 3. Installing the Management
Server 23 ||||| |||||||||||| | |||||||||||||||||||| ||||||||| ||||||
Java131.rte filesets are normally installed with
AIX and are available on the AIX CD-ROM #1. Step
8. Apply updates to CSM filesets that have already been installed with AIX If any updates are available for the
CSM filesets that have already been installed with AIX, apply the updates
before you continue. Check for updates to the following CSM filesets: v
csm.core v csm.client v csm.dshYou can use standard AIX tools to install these
filesets. For example, assuming that you downloaded the tar file into the /tmp/csm directory, you can use the
geninstall command as follows: geninstall
-IaX -d/tmp/csm csm.core csm.client csm.dsh Step
9. Install CSM management server software The
following AIX filesets and RPM packages are available on AIX CD-ROM #2 product
media: CSM on AIX filesets: v csm.server v csm.diagnostics v
csm.gui.dcem v csm.gui.websmOpen
source software: v expect v tcl v tkTo install this
software, insert CD-ROM #2 and use AIX WebSM, SMIT panels, or the AIX command
line interface. For example, you can use the AIX geninstall command to install selected CSM
software as follows: geninstall -IaX -d /dev/cd0
csm.server csm.diagnostics \ csm.gui.dcem csm.gui.websm R:expect R:tcl R:tk Step 10. Apply management server
software updates If CSM software updates are
available, you need to install them when you set up the management server. The
management server must always be installed with the latest version of CSM in
the cluster. Note: If you are applying updates to
version 1.3.0 of the CSM software, see “Special Handling for Updates to CSM
1.3.0” on page 94. Updates for the management server software are contained in
the tar file that you downloaded from the CSM support site in “Step 5. Download
CSM Updates” on page 21 24 CSM for AIX 5L: Planning and
Installation Guide ||||||||||||||||||||||||||||||||||
||||||||||
page
21. Assuming that you downloaded the updates to the /tmp/csm directory and unwrapped them, you
can issue the geninstall command as follows: geninstall -IaX -d/tmp/csm all Rejecting the update and going back
to an earlier CSM version: If
you need to reject a CSM version 1.3.2.* update and go back to version 1.3.1.* and you installed Version 0.7-4 of
openCIMOM, you might need to install the
latest CSM 1.3.1 update (1.3.1.4 or greater). Previous levels of CSM 1.3.1 do
not work with this version of openCIMOM. To check for the latest 1.3.1
updates, see the CSM support web site: http://techsupport.services.ibm.com/server/cluster/fixes
To determine the version of openCIMOM, issue the following command: rpm -qi openCIMOM Note: If you have gone back to a 1.3.1.*
level of CSM, be sure to see the CSM 1.3.1 documentation. Step 11. Check the remote shell
attribute A distributed shell program (dsh) is used to issue remote commands
from the management server to the nodes. It is contained in the csm.dsh package. The dsh program uses a remote shell of your
choice to issue remote commands to the managed nodes. The default remote shell
is /usr/bin/rsh, but you can specify a different
remote shell (/usr/bin/ssh) by running the csmconfig command with attribute value pairs. csmconfig attributes for the remote
shell RemoteShell Stores the pathname of the
executable that dsh uses to run remote commands. SetupRemoteShell Indicates to CSM that you want the
remote shell to be automatically configured (1 = yes, 0= no).CSM can
automatically configure rsh
and OpenSSH when the node is being added to the
cluster. Setting up OpenSSH Consider the following for setting
up OpenSSH Installing OpenSSH on the
management server: Before setting up OpenSSH , you must ensure that the required
software is installed on the management server and the nodes. For the required
software and instructions for installing it on the management server, see “Step
12. Install OpenSSH and OpenSSL (optional)” on page 26. Installing OpenSSH during the
initial installation of an AIX node: If
you want to have OpenSSH configured during the initial
installation of an AIX node, you must include the required software as part of
the installation. See “Step 13. Add OpenSSH and OpenSSL software (optional)” on
page 71. Chapter 3. Installing the Management
Server 25 ||||||||||||||||||||||||||||||||||||||||||
Adding a previously installed AIX
node and configuring OpenSSH: If
you are adding a previously installed AIX node to the cluster and you want to
have OpenSSH configured, you must first install
the required software on the node. You use the AIX Network Installation Manager
(NIM) cust operation to install the software.
For information about where to find the required software, see “Step 13. Add
OpenSSH and OpenSSL software (optional)” on page 71. For information about
using the NIM cust operation, see the IBM Network Installation Management
Guide and Reference. Running
csmconfig to display remote shell values Run
the csmconfig command to display the current
values for the RemoteShell and SetupRemoteShell attributes. You can then set the Remote Shell and SetupRemoteShell attributes to other values. For
example, the following command sets the remote shell to rsh and instructs CSM not to
automatically set it up: csmconfig RemoteShell=/usr/bin/rsh
SetupRemoteShell=0 You can also temporarily change the
remote shell setting with the DSH_REMOTE_CMD environment variable. If you
wanted to switch from the default rsh
shell to ssh, specify the DSH_REMOTE_CMD
environment variable with the full path name of the remote shell command:: export DSH_REMOTE_CMD=/usr/bin/ssh
To set up remote access manually,
see “Setting up remote access manually for AIX” on page 78. For more
information about using the RemoteShell
attribute, see the csmconfig and dsh
man pages or CSM for AIX 5L: Command and
Technical Reference. Step
12. Install OpenSSH and OpenSSL (optional) This
step is required if you plan to use OpenSSH
as your remote shell. Because OpenSSH and its prerequisite OpenSSL are not installed with AIX, you must
install the software on the management server and the AIX cluster nodes. You
can find the software at the following locations: v OpenSSL on the AIX Toolbox for Linux
Applications for Power Systems v OpenSSH
on the IBM AIX Bonus Pack - AIX 5L
for Power 5.2.Bundle files: To handle the installation, create
two bundle files that you can use with AIX tools to facilitate the copying and
installation of the software. A bundle file simply contains a list of software
filesets or packages. Create one bundle file for OpenSSL and one bundle file for OpenSSH. You can also use these bundle
files when you install the software on the nodes. If you are using the NIM tool
to install the nodes, after you set up NIM, copy the bundle files to the same
filesystem that is used to store the other NIM resources that the node is using
(for example, /export/nim). For details, see Chapter 7,
“Installing the AIX operating system and adding nodes,” on page 61. Ensure that
the OpenSSL bundle file contains the following
line: R:openssl* Ensure that the OpenSSH bundle file contains the following
lines: 26 CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||||||||||||||||||||||||
I:openssh.base I:openssh.license I:openssh.man.en_US
I:openssh.msg.en_US I:openssh.msg.EN_US If
you intend to use additional or different languages in the cluster, you need to
include additional or different filesets in this list. To install OpenSSL on the management server, insert the
Linux Toolbox CD and issue the geninstall
command. The following example
assumes the name of the OpenSSL
bundle to be openssl.bnd: geninstall -IaXY -d /dev/cd0 -f openssl.bnd To install OpenSSH on the management server, insert the
Bonus Pack CD and issue the geninstall
command. The following example
assumes the name of the OpenSSH
bundle file to be s openssh.bnd: geninstall -IaXY -d /dev/cd0 -f openssh.bnd Step 13. Accept the CSM license A License Use Key is required to run
CSM, which is shipped separately on the CSM license CD-ROM. CSM is available in
two forms. You can either purchase a full production license and license key
for CSM, or you can use a 60–day try-and-buy
license option, at no charge. The try-and-buy license is included with the AIX 5L
base code. Accepting the full production
license 1. The license key you need is
located on the CSM CD-ROM. It is called csmlum.full. You will use the key file as input
for the csmconfig command, in the next step. 2. Accept
the license and activate the license key, using the mount and csmconfig commands, as follows. mount -v cdrfs -o ro /dev/cd0 /mnt
csmconfig -L /mnt/csmlum.full At
the prompt, follow the directions to accept the CSM license. 3. Check the
success of the csmconfig command, by running it with no
flags, and then checking the output: csmconfig
The following is sample command
output for the csmconfigcommand: AddUnrecognizedNodes = 0 (no)
ClusterSNum = 654BN5011 ClusterTM = 9078-160 ExpDate = MaxNumNodesInDomain = -1
(unlimited) MaxNumNodesInDomain = -1 (unlimited) RemoteShell = /usr/bin/rsh
SetupRemoteShell = 1 Accepting the try-and-buy license To accept the 60–day try-and-buy
license agreement, issue the csmconfig
command, as follows: csmconfig -L Chapter 3. Installing the Management
Server 27 ||||| ||||||||||||||||||||||||| |||||||||||| ||||
You
can check the success of the csmconfig
command, by running it with no
flags, and then checking the output: csmconfig
The following is sample output of
the csmconfig command. Because you accepted the
try-and-buy license, you see a date in the ExpDate
field. AddUnrecognizedNodes = 0 (no)
ClusterSNum = 654BN5011 ClusterTM = 9078-160 ExpDate = Sat Oct 19 18:59:59 2002
MaxNumNodesInDomain = -1 (unlimited) RemoteShell = /usr/bin/rsh
SetupRemoteShell = 1 Step 14. Copy CSM files into the
/csminstall subdirectories Issue
the following csmconfig command to copy the CSM files into
the proper /csminstall subdirectories: csmconfig -c Step 15. Set the cluster ID
(optional) Supply the cluster serial number.
The serial number is provided on the labels that are delivered with your
Cluster 1600 hardware. The labels are part of the group of materials that also
includes the IBM Cluster 1600 Planning,
Installation, and Service Guide.
To store this information, issue the csmconfig
command: csmconfig -s 654BN5011 Note: If the cluster serial number is not
currently available, you can skip this step and return to it later. Step 16. Verify the installation To verify that the management server
has installed correctly and is ready for use, you can run the ibm.csm.ms probe, which is shipped with CSM. To
run the probe issue the following command. probemgr
-p ibm.csm.ms -l 0 For information about CSM support
for probes, see CSM for AIX 5L: Administration Guide. 28
CSM for AIX 5L: Planning and
Installation Guide |||||||||||| |||||||||||||||||||||||
Chapter 4. Defining nodes for the
cluster Determining node attributes As part of the CSM cluster
installation process, gather information that will be used to define the
cluster nodes. The pieces of information that make up a node definition are
referred to as node attributes. The complete list of node
attributes and descriptions are documented in the nodeattributes man page. This section provides
information about the attributes that are needed when you define nodes and how
to determine which values to use. The information is divided into three
categories; general attributes, hardware control information, and information
about installation software. General
attributes ManagementServer The host name of the CSM management
server. ManagementServer is always required. It must be set
to the host name of the management server as it is known by the node. Because
the management server can have multiple interfaces, different nodes might use
different interfaces to communicate with the management server. If a route to
the node exists at the time that the node is defined, CSM attempts to set the
value automatically. UserComment Any useful information concerning
this node. Not required.Hardware
control attributes You must define the hardware-related
attributes for AIX and Linux nodes. In some cases default values are provided.
If these defaults are acceptable, you do not need to provide the attribute
values when you define the node. For a complete description of the meaning and
use of these attributes, see CSM
for AIX 5L: Hardware Control Guide.
For AIX on pSeries or Linux on
pSeries nodes: PowerMethod The power method that is to perform
hardware control. For pSeries nodes that are controlled by a Hardware
Management Console (HMC), this value is hmc. HWControlPoint
The host name of the hardware
control point. For pSeries nodes, this value is the host name of the HMC. © Copyright IBM Corp. 2002, 2003 29
||||||||
HWControlNodeId The identifier used for power
control that is associated with the node. For pSeries nodes, this is the
partition name of the LPAR or CEC name of the CEC in SMP mode. ConsoleMethod The console method that is to open a
node console. For pSeries nodes that are controlled by a Hardware Management
Console (HMC), this value is hmc. If the PowerMethod attribute is set to hmc, this value is set by default. ConsoleServerName The host name of the network adapter
for the console server. For pSeries nodes that are controlled by a Hardware
Management Console (HMC) this value is host name of the HMC. If the PowerMethod attribute is set to hmc, this value is set by default to
the host name of the HMC. InstallAdapterDuplex
The duplex value of the network
adapter that is used to install the node. Valid values are: auto, half, or full. InstallAdapterMacaddr
The machine address of the Ethernet
adapter that is to install the node. InstallAdapterSpeed
The speed of the network adapter
that is to install the node. Valid values are: auto, 10, 100, or 1000. InstallAdapterType
The type of the network adapter that
is to install the node. Valid values are: ent
(Ethernet) or tok (token ring). For xSeries Linux nodes,
IntelliStation, and eServer 325 nodes PowerMethod
The power method that is used to
perform hardware control. For xSeries nodes, the value must be set to xseries.
For IntelliStation nodes, the value must be set to apc. For eServer 325 nodes, the value
must be set to bmc. HWControlPoint
The host name of the network
interface for the hardware control point. For xSeries nodes, use the hostname
of the IBM Remote Supervisor Adapter (RSA). For IntelliStation nodes, use the
host name of the APC MasterSwitch into which the node is plugged. For eServer
325 nodes, use the host name or IP address of the Baseboard Management
Controller (BMC). HWControlNodeId The power control identifier that is
associated with the node. For xSeries nodes, use the TextID associated with the node’s Internal
System Management Processor (ISMP). For IntelliStation nodes, use the APC
MasterSwitch outlet number the node is plugged into. For eServer 325 nodes, use
the node host name. ConsoleMethod The console method that is to open a
node console. Valid values are: mrv, esp, els, computone, and cps. ConsoleSerialDevice
The device name of the console
serial port on the node. This attribute is an option when you define the
resource and can be edited. Valid values are: 30
CSM for AIX 5L: Planning and
Installation Guide ||||||||||||||||||||||
ttyS0, ttyS1, and NONE. If no value is specified for this
attribute when the node is created with the definenode command, a default value
of ttyS0 is set. If the system has no serial
port defined, or if you do not want console output redirected to the serial
port, the ConsoleSerialDevice attribute value must be set to NONE. ConsoleServerName
The host name of the network adapter
for the console server. ConsoleServerNumber
The number associated with the ESP
console server. This attribute is only required if you are using ESP console
servers. ConsolePortNum The number associated with the
console port for this node. The valid MRV console port numbers range from 1
through 40 depending on the model. Valid ESP port numbers are:
0,1,2,3,4,5,6,7,8,9,a,b,c,d,e, and f. The valid CPS, ELS and Computone console
numbers range from 1 through 16 (decimal). For
SP nodes and p660 servers PowerMethod
The power method that is used to
perform hardware control. For SP Nodes and p660 servers, the value must be set
to csp. HWControlPoint
The device specification of the
management server’s tty port that is connected to the SP frame supervisor or
p660 CSP serial port (for example, /dev/tty0) HWControlNodeId
The power control identifier that is
associated with the node. For SP Nodes, use the frame slot number that the node
is installed in. For p660 servers, this value must be set to 1. ConsoleMethod The console method that is to open a
node console. For SP Nodes and p660 servers, this value must be set to cps. ConsoleSerialDevice
The device name of the console
serial port on the node. Leave this value blank, or set to NONE to disable console support for this
node. ConsoleServerName The device specification of the
management server tty port that is connected to the SP
frame supervisor or p660 CSP serial port (for example, /dev/tty0). ConsoleServerNumber
This field is blank. ConsolePortNum The number associated with the
console port for this node. For SP Nodes, use the frame slot number that the
node is installed in. For p660 servers, this value must be set to 1.Note: POWER3 SMP High Nodes (feature
numbers 2054 and 2058) with attached expansion I/O units (feature number 2055)
require additional configuration. See the topic on SP Expansion I/O units in
for more information in CSM
for AIX 5L: Hardware Control Guide.
Chapter 4. Defining nodes for the
cluster 31 ||||||||||||||||||||||||||||
For BladeCenter nodes PowerMethod The power method that is used to
perform hardware control. For BladeCenter nodes, the value must be set to xseries. HWControlPoint
The host name of the network
interface for the hardware control point. For BladeCenter nodes, use the hostname of the BladeCenter Management
Module. HWControlNodeId The power control identifier that is
associated with the node. For BladeCenter nodes, use the blade Advanced System
Management (ASM) name. ConsoleMethod
The console method that is to open a
node console. For SP Nodes and p660 servers, this value must be set to cps. The following console attributes
are only valid if the BladeCenter is part of an eServer Cluster 1350, and the
optional Serial Port Module (SPM) components have been installed. If the SPM
components have not been installed, set the ConsoleSerialDevice
attribute for all blades to NONE, and leave the ConsoleMethod, ConsoleServerName, ConsoleServerNumber, and ConsolePortNum attributes blank. ConsoleSerialDevice For BladeCenter nodes, this value
must be set to mrv. ConsoleServerName
For BladeCenter nodes, use the host
name of the MRV Console Server the blade to which it is connected. ConsoleServerNumber Leave this field blank. ConsolePortNum For BladeCenter nodes, use the MRV
console server port number the blade to which it is connected.Installation software information
for nodes The following topic describes the
software-related attributes that you must define for Linux nodes, and AIX
nodes. Note that all of these values use the characteristics of the management
server as defaults. If these values are acceptable, you do not need to specify
any of the attributes when you define the node. For AIX nodes: InstallOSName The name of the operating system on
the node. When you define a node, the default is the name of the operating
system that is installed on the management server. For AIX systems the value
must be AIX. For
Linux nodes: InstallCSMVersion The version of CSM that is to be
installed on the node. This value must be 32
CSM for AIX 5L: Planning and
Installation Guide ||||||||||||||||
in
the format version.release.modification, (for example, 1.3.2). When you
define a node, the default is the version of CSM that is installed on the
management server. InstallOSName The name of the operating system to
install. When you define a node, the default is the name of the operating
system that is installed on the management server. For Linux nodes the value
must be Linux. InstallDistributionName
The name of the operating system
distribution. The valid values are RedHat, RedHatAS, SuSE, and SLES. For Linux on pSeries nodes, only SLES is valid. When you define a node,
the default is the distribution name installed on the management server. For
Linux on pSeries nodes, only SLES
is valid. InstallDistributionVersion The name of the distribution version
to be installed. For Linux, the format is version.release, (for example, 8.0). When you
define a node, the default is the distribution version installed on the
management server. The valid values are v For Red Hat Linux: 7.2, 7.3, 8.0, or 9 v
For Red Hat Linux AS: 2.1 v For
SuSE Linux: 8.0, or 8.1 v For
SuSE SLES Linux: 7.2 or 8.1InstallPkgArchitecture The machine architecture of the
node. For xSeries, IntelliStation, or BladeCenter nodes, the only valid
attribute value is i386. This value represents any machine
whose architecture is i386, i486, i586, or i686. For pSeries nodes, the only valid
attribute value is ppc64. . When you define a node, the
default is the machine architecture of the management server.Collecting node attribute values At this point, you have identified
what attributes are required for your node definitions. The next step is to
collect the actual values you need for the attributes. You can do this as a
manual task. You can make decisions about the hostnames, networks, adapters,
and so on during the planning process, and record the information for use when
you actually define the nodes in the CSM database. You should complete one
template for each node. An alternative to creating a hard copy template for
each node would be to create a node definition stanza file. This is a file that
contains information for each node, and you can pass this file directly to the definenode command during the CSM installation
process. See “Creating a node definition file” on page 36 for details. Also,
the scenarios in Appendix B, “Installation scenario: configuring additional
Ethernet or High Performance Switch (HPS) adapters,” on page 101 provide
examples. Chapter 4. Defining nodes for the
cluster 33 ||||||||
Defining the nodes You will run the definenode command on the CSM management server
to define all the nodes in a CSM cluster. The command creates node definitions
in the CSM database. Note that the definenode
command simply creates definitions
for the nodes in the cluster (premanaged
node). It does not actually install
the nodes. The definenode command provides several options for
creating cluster node definitions: 1. Create one definition at a time. 2. Use a
node definition file as input to the command to define multiple nodes. 3. Use
the –M flag to automatically define nodes
that are listed in a host name mapping file. 4. For Linux nodes, use starting_node and count values to automatically generate a
set of node definitions with consecutive IP addresses. 5. Create a node
definition file (use the –s
flag and redirect the output to a
file) that you can modify and use as input to the definenode command.Note that you can pass null
values for any of the attributes with the definenode
command by not specifying anything
for the attribute value. In the following example, the values for the PowerMethod and ConsoleMethod attributes are specified as null: definenode -n clsn01 PowerMethod=
ConsoleMethod= See the man page or CSM for AIX 5L: Command and
Technical Reference for details on definenode command line syntax. You can also
define CSM nodes using SMIT. The SMIT fastpath is csm_defnodes. To use this interface, issue: smit csm_defnodes Defining a single node The information required to define a
node differs depending on the type of node to be defined, and whether or not
hardware control is supported on the node. The host name or IP address of the
node is always required. The specific information about a node is stored in the
CSM database and is usually referred to as node attributes. For a complete list of attributes
that you can set when issuing the definenode
command see the nodeattributes man page. Note: If you are not using hardware
control in the cluster, the only required attribute for a node is the host
name. AIX nodes in an AIX cluster The resolvable host name or IP
address of the node is always required. This is the node’s network interface,
as known by the management server The following information is required if you
are using hardware control: v The PowerMethod
attribute value set to hmc. v The HWControlPoint and either the LParID or HWControlNodeId
attribute values.For example, the
following command defines an AIX node with host name clsn01. definenode -n clsn01 -H hmc12 PowerMethod=hmc \
InstallOSName=AIX 34 CSM for AIX 5L: Planning and
Installation Guide |||| |||||
If
values are not provided for some attributes on the command line, default values
are set. For example, the default values for the InstallOSName attribute is set to the operating
system name. Also, for nodes with a PowerMethod
of hmc, the ConsoleMethod and ConsoleServerName can be set automatically. To view
the values that are set by the definenode
command, without actually creating
the definition, use the –s
option. If –s is specified on the command line,
the definenode command displays the list of attributes
and values that would be set for the node. xSeries
Linux nodes in an AIX cluster The
following information is required if you are using hardware control: v The
resolvable host name or IP address of the node. This is the nodes’ network
interface, as known by the management server. v The PowerMethod attribute set to xseries. v The HWControlPoint and HWControlNodeId attribute values. v The ConsoleMethod attribute set to mrv, esp, computone, conserver, els, or cps. v The ConsoleServer, ConsoleServerNumber, and ConsolePortNum, and ConsoleSerialDevice attribute values. v The InstallCSMVersion, InstallOSName, InstallDistributionName, InstallDistributionVersion
and InstallPkgArchitecture attributes must be set to
appropriate values.For example, to define a node whose hardware control point
is defined as an RSA adapter on a Linux node whose service processor is defined
as the short host name of the node, and uses an MRV console server, issue the definenode command: definenode -n node1.pok.ibm.com -H
rsa01.pok.ibm.com -C \ mrv01.pok.ibm.com PowerMethod=xseries ConsoleMethod=mrv Note: When using an AIX management server,
the default values that are normally set for AIX cluster nodes are not valid
for Linux nodes. Linux on pSeries nodes in an AIX
cluster The following information is
required if you are using hardware control: v The resolvable host name or IP
address of the node. This is the node’s network interface, as known by the
management server. v The PowerMethod
attribute value set to hmc. v The HWControlPoint and either the LParID or HWControlNodeId
attribute values. v The InstallCSMVersion, InstallOSName, InstallDistributionName, InstallDistributionVersion
and InstallPkgArchitecture attributes must be set to
appropriate values.For example, the following command defines an AIX node with
host name clsn01.d definenode -n node1.pok.ibm.com -H hmc12
PowerMethod=hmc \ InstallCSMVersion=1.3.2 Chapter
4. Defining nodes for the cluster 35 |||| || |||||||||
Creating a node definition file A node definition file contains a
stanza of information for each node to be defined. You can pass this file to
the definenode command to create the node
definitions in the CSM database. This section contains rules for the format of
the node definition file and examples of stanzas for AIX and Linux nodes. Note
that the examples contain attributes that have default values. If the default
values are acceptable, you do not have to include them in the stanzas. The
information in this section is also provided in the CSM nodedef man page. Node definition file rules v A
stanza header consists of the node name followed by a colon ( : ). v Attribute
lines must take the form of Attribute=Value. v If a line is not blank, a
comment, a header, or an attribute=value pair, then the command will skip to
the next valid header. v A warning message is issued for attributes that are
not valid, but the code will continue. v Each line of the file may have only
one header or attribute definition. v Only one stanza may exist for each node.
v If the header keyword is default
then the attribute values in the
stanza are considered default values for subsequent node definitions. v Default
stanzas may be specified multiple times and at any point in a definition file.
The values apply to all definitions following it in the file. The default
values are cumulative. That is, a default attribute value will remain set until
it is explicitly unset or changed. v To turn off a default value, set the
attribute to nothing (blank). v When a specific value for an attribute is
provided in the node stanza, it will take priority over any default value that
had been set. v Comments beginning with the pound sign (#) may be added to the
file. Comments must be on a separate line. v When parsing the file, tab characters
and spaces are ignored. v Some attribute values is set by default by the definenode command when this file is used as
input. This applies to attributes that you do not include in the node
definition file (if you do not set them in the node definition file, the
default value is used).AIX
examples without default stanzas clstrnode01:
ManagementServer=c46cw.ppd.ibm.com InstallOSName=AIX PowerMethod=hmc
HWControlPoint=hmc23 HWControlNodeId=clstrnode01 ConsoleMethod=hmc
ConsoleServerName=hmc23 InstallAdapterMacaddr=0004AC5E06E2
InstallAdapterType=ent InstallAdapterSpeed=100 InstallAdapterDuplex=full
UserComment="First LPAR on CEC #1" clstrnode02:
ManagementServer=c46cw.ppd.ibm.com InstallOSName=AIX 36
CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||||||||||||||||||||||||||||||||
PowerMethod=hmc HWControlPoint=hmc23
HWControlNodeId=clstrnode02 ConsoleMethod=hmc ConsoleServerName=hmc23
InstallAdapterMacaddr=0003AC6E05E2 InstallAdapterType=ent
InstallAdapterSpeed=100 InstallAdapterDuplex=full UserComment="Second LPAR
on CEC #1" Linux examples without default
stanzas nfnode11:
ManagementServer=c5bs.ppd.ibm.com InstallCSMVersion=1.3.2 InstallOSName=Linux
InstallDistributionName=RedHat InstallDistributionVersion=9
InstallPkgArchitecture=i386 PowerMethod=xseries HWControlPoint=rsa05
HWControlNodeId=nfnode11 ConsoleMethod=mrv ConsoleSerialDevice=ttyS0
ConsoleServerName=mrv15 ConsolePortNum=1 nfnode12:
ManagementServer=c5bs.ppd.ibm.com InstallCSMVersion=1.3.2 InstallOSName=Linux
InstallDistributionName=RedHat InstallDistributionVersion=9
InstallPkgArchitecture=i386 PowerMethod=xseries HWControlPoint=rsa04
HWControlNodeId=nfnode12 ConsoleMethod=mrv ConsoleSerialDevice=ttyS0
ConsoleServerName=mrv15 ConsolePortNum=2 AIX
examples with a default stanza Note:
You can use the getadapter command to include information on
the adapter configuration (InstallAdapterMacaddr, InstallAdapterType, InstallAdapterSpeed, and InstallAdapterDuplex)default:
ManagementServer=c46cw.ppd.ibm.com InstallOSName=AIX PowerMethod=hmc
HWControlPoint=hmc23 ConsoleMethod=hmc ConsoleServerName=hmc23 InstallAdapterType=ent
InstallAdapterSpeed=100 InstallAdapterDuplex=full clstrnode01:
InstallAdapterMacaddr=0003AC6E05E1 HWControlNodeId=clstrnode01 clstrnode02:
InstallAdapterMacaddr=0003AC6E05E3 HWControlNodeId=clstrnode02 Chapter 4. Defining nodes for the
cluster 37 |||||||||| ||||||||||||||||||||||||||||| ||||||||||||||||||||
clstrnode03: InstallAdapterMacaddr=0003AC6E05E4
HWControlNodeId=clstrnode03 Linux
examples with a default stanza default:
PowerMethod=xseries ConsoleMethod=esp ConsoleServerName=esp15 ConsoleServerNumber=2
ConsolePortNum=0 InstallOSName=Linux InstallCSMVersion=1.3.2
HWControlPoint=asm03 ManagementServer=c5bs.ppd.xyz.com
InstallDistributionVersion=9 nfnode11: HWControlNodeId=nfnode11 nfnode12:
ConsolePortNum=2 HWControlNodeId=nfnode12 nfnode13: HWControlPoint=asm05
HWControlNodeId=nfnode13 ConsolePortNum=3 Using
a node definition file You
can use a node definition (nodedef) file to define multiple nodes.
This file consists of stanzas containing node attribute values for each node to
be defined. To use a node definition file, you should start by looking at the
sample file provided with CSM. The /opt/csm/install/nodedef.sample
file contains information on the
format that must be used and also provides examples. You can create this file
manually and pass it to the definenode
command using the –f flag. The definenode command uses information in the nodedef file to create node definitions.
When possible, default values are set for attributes that are not specified in
the file. The definenode command does not allow you to
specify additional attributes on the command line when using the –f flag. You can also use the definenode –s flag to create a nodef file. The –s flag tells the definenode command to send a list of the nodes
and their attributes to standard output. The information includes what you
provided on the command line in addition to whatever default values would be
set. The nodes are not defined in the CSM database if you use the –s flag. You can redirect the output of
the definenode –s command to a file. This file is
created in the correct format to be used as a node definition file. Check this
file to be sure it is correct and complete, and edit the file, if necessary,
before using it to define the nodes. For details about the node definition
file, see the nodedef man page or CSM for AIX 5L: Command and
Technical Reference. For an example of a typical node
definition file, see “Creating a node definition file” on page 36. To define a
set of cluster nodes, as specified in a node definition file, do the following:
38 CSM for AIX 5L: Planning and
Installation Guide ||| |||||||||||||||||||||||| |
If using: Do this: Command line Issue the definenode command. For example: definenode -f /tmp/mynodedefs SMIT Issue the definenode command via SMIT. The fastpath is csm_defnodes. For example: smit csm_defnodes Web-based System Manager or DCEM Use
DCEM (Distributed Command Execution Manager) to run the definenode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
Using a host name mapping file With the the –M flag on the definenode command, you can specify a host name
mapping file that allows you to define large numbers of CSM cluster nodes. The
host name mapping (hostmap) file contains a list of host names and associated
hardware control information. The definenode
command uses the information in the
file to create CSM node definitions. Any other required attribute values can be
specified on the command line. Note that if the PowerMethod attribute is hmc, the default value for the ConsoleMethod attribute is hmc and the default for ConsoleServerName is the name of the hardware control
point. For other power methods, the console information must be provided on the
command line. A hostmap file can be created by running the lshwinfo command, redirecting the output to a
file, and editing the file to add the host names for each machine. This command
gathers hardware control information for all nodes that are controlled by the
specified hardware control point. Example
for an AIX node or Linux on pSeries node The
following example shows how to create a host name mapping file that lists the
nodes associated with hardware control point hmc01, has a PowerMethod of hmc, and is redirected to a file called
/tmp/mymapfile: 1. Create the hostmap file, as
follows: If using: Do this: Command line Issue the lshwinfo command, as follows: lshwinfo -p hmc -c hmc01 -o
/tmp/mymapfile SMIT Issue the lshwinfo command via SMIT. The fastpath is lshwinfo. For example: smit lshwinfo Web-based System Manager or DCEM Use
DCEM (Distributed Command Execution Manager) to run the lshwinfo command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
The output file /tmp/mymapfile would look like the following: #
Hostname::PowerMethod::HWControlPoint::HWControlNodeID::LParId::HWType: \
:HWModel::HWSerialNum
no_hostname::hmc::hmc01.kav.opn.com::lpar01::001::7040::681::7017-S9 no_hostname::hmc::hmc01.kav.opn.com::lpar02::002::7040::681::7017-S9
no_hostname::hmc::hmc01.kav.opn.com::lpar03::003::7040::681::7017-S9
no_hostname::hmc::hmc01.kav.opn.com::lpar04::004::7040::681::7017-S9 2. Edit the hostmap file to add the
host names for each node. For example: Chapter
4. Defining nodes for the cluster 39 |
#
Hostname::PowerMethod::HWControlPoint::HWControlNodeID::LParId::HWType: \
:HWModel::HWSerialNum
clstrn01::hmc::hmc01.kav.opn.com::lpar01::001::7040::681::7017-S9
clstrn02::hmc::hmc01.kav.opn.com::lpar02::002::7040::681::7017-S9
clstrn03::hmc::hmc01.kav.opn.com::lpar03::003::7040::681::7017-S9
clstrn04::hmc::hmc01.kav.opn.com::lpar04::004::7040::681::7017-S9 Note that if the nodes you are
defining are pSeries LPARS, the value of the HWControlNodeId
is the name that was assigned to the
LPAR when it was defined. If the host name that you intend to use for that LPAR
is used as the LPAR name, it is easier to add the host names to the hostmap
file. In this case, the host name would be the same as the HWControlNodeId. For example, the first line in
step 2 above would be: clstrn01::hmc::hmc10.acme.com::clstrn01::001::7040::681::7017-S9
The lshwinfo command might not always be able to
return information for all the columns listed above. In most cases, except for
the host name, the information left out is not required. You can add missing
fields manually, if necessary. For pSeries systems, the file can contain
information about the LPARs that have been defined. This information allows you
to create CSM node definitions, as follows: If
using: Do this: Command line Issue the definenode command, similar to the following
example: definenode -M /tmp/mymapfile
InstallOSName=AIX SMIT Issue the definenode command via SMIT. The fastpath is csm_defnodes. For example: smit csm_defnodes Web-based System Manager or DCEM Use
DCEM (Distributed Command Execution Manager) to run the definenode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
Example for an xSeries node The following example shows how to
create a hostmap file that lists the nodes associated with hardware control
points frame10 and frame11 and a PowerMethod of xseries
to a file called /tmp/mymapfile: 40
CSM for AIX 5L: Planning and
Installation Guide ||
If using: Do this: Command line 1. Issue the lshwinfo command, as follows: lshwinfo -p xseries -c
frame10,frame11 -o /tmp/mymapfile The
output file /tmp/hcp_out would look similar to this: #
Hostname::PowerMethod::HWControlPoint::HWControlNodeID: \
:LParId::HWType::HWModel::HWSerialNum
no_hostname::xseries::frame10.acme.com::node01::::::::
no_hostname::xseries::frame10.acme.com::node02::::::::
no_hostname::xseries::frame10.acme.com::node03::::::::
no_hostname::xseries::frame10.acme.com::node04::::::::
no_hostname::xseries::frame11.acme.com::node01:::::::: no_hostname::xseries::frame11.acme.com::node02::::::::
no_hostname::xseries::frame11.acme.com::node03::::::::
no_hostname::xseries::frame11.acme.com::node04:::::::: 2. Edit the hostmap file to add the
host names for each node. For example: #
Hostname::PowerMethod::HWControlPoint::HWControlNodeID: \
:LParId::HWType::HWModel::HWSerialNum
clsn01::xseries::frame10.acme.com::node01::::::::
clsn02::xseries::frame10.acme.com::node02::::::::
clsn03::xseries::frame10.acme.com::node03::::::::
clsn04::xseries::frame10.acme.com::node04::::::::
clsn05::xseries::frame11.acme.com::node01::::::::
clsn06::xseries::frame11.acme.com::node02::::::::
clsn07::xseries::frame11.acme.com::node03::::::::
clsn08::xseries::frame11.acme.com::node04:::::::: SMIT Issue the lshwinfo command using SMIT. The fastpath is lshwinfo. For example: smit lshwinfo CSM Web-based System Manager Not
applicable. The lshwinfo command may not always be able to
return information for all the columns listed above. In most cases, except for
the host name, the information left out will not be required. Missing fields
could be added manually, if necessary. When using xSeries systems, the file
could contain information about the LPARs that have been defined. This
information could be used to create CSM node definitions, as follows: If using: Do this: Command line Issue the definenode command. For example: definenode -M /mydir/mymapfile -C
mrv1:1:0:12 ConsoleMethod=mrv \ InstallCSMVersion=1.3.2 InstallOSName=Linux SMIT Issue the definenode command using SMIT. The fastpath is definenode. For example: smit csm_defnodes CSM Web-based System Manager Not
applicable. To verify the information that is
used to define the nodes in the examples, use the –M flag with the –s flag and redirect the output to a
file. You could check this file for accuracy, edit it if necessary, and then
use this file as a node definition file with the –f flag. Chapter
4. Defining nodes for the cluster 41
Using the starting_node and count
method for xSeries nodes Multiple
nodes can also be defined using the starting_node and count method. This method
defines the starting node and increments the nodes IP address to determine the
value for the next node. IP addresses are incremented up to the count — the
total number of nodes. The values for node hardware control and remote console
attributes must be specified with the –H
and –C flags. This method for defining
nodes assumes the hardware has been configured in a way that facilitates the
use of this method. The mapping of IP address to node hardware and console
servers can range in complexity, depending on the type of hardware being used
and the cluster environment. Initial planning is required for cluster
installation and configuration to be automated as much as possible. When using
the starting_node and count method the following is required: v Short host
names to be assigned to the nodes are resolvable. v There is a set of valid
consecutive IP addresses that can be assigned to a particular set of nodes. v
The node name as defined on the hardware control point must be set to the short
host name that will be assigned to the node. For example, the user defined
text_id that is set when an xSeries machine is defined on the RSA must be set
to the short host name to be used for the node. v A consecutive set of console
port numbers must be connected to nodes with consecutive IP addresses. For
example, the first port number connects to the first IP address, the second
port number connects to the second IP address, and so on.To define xSeries,
IntelliStation, or BladeCenter nodes the HWControlNodeId
attribute values must be set to the
node short host names. The following command would define 30 nodes with
consecutive IP addresses as HWControlNodeId
values node1 — node30: definenode -n node1 -c 30 -s -H rsa1:10,rsa2:10,rsa3:10
-C mrv1::1:20,mrv2::1:20 \ PowerMethod=xseries ConsoleMethod=mrv
InstallCSMVersion=1.3.2 \ InstallDistributionName=RedHat
InstallDistributionVersion=7.3 The
nodes are assigned to hardware control points in order up to the total number
of nodes for each hardware control point. In the example, there are 10 nodes
connected to each hardware control point. The first hardware control point
(rsa1) is assigned to the first 10 nodes (node1 - node10); the second hardware control
point (rsa2) is assigned to the next 10 nodes (node11 - node20); the third
hardware control point (rsa3) is assigned to the last 10 nodes (node21 -
node30). The HWControlNodeId attributes are set to the nodes host
names, which should be the same as the node text_id. The number of hardware
control point nodes must be greater than or equal to the number of nodes that
are being defined. The nodes are assigned to the console servers in order up to
the number of ports for each console server. In the example, the first console
server (mrv1) is assigned to the first 20 nodes (node1 - node20) and the second
console server (mrv2) is assigned to the next 10 nodes (node21 - node30). The
number of console ports must be greater than or equal to the number of nodes
being defined. In this case there are only 30 nodes being defined so the last
console server is left with some unassigned ports. In the example, the console
port numbers are assigned in consecutive order starting with 1. Port 1 is
assigned to the node with the first IP address, port 2 to the next IP address,
and so on. 42 CSM for AIX 5L: Planning and
Installation Guide |
When
using the starting_node and count node definition method, it is important to
redirect output to a file and check the file for accuracy before actually
creating the node definitions. You can do this using the –s flag as described earlier. Chapter 4. Defining nodes for the
cluster 43
44
CSM for AIX 5L: Planning and
Installation GuideChapter 5. Adding AIX nodes to the
cluster This chapter tells you how to add
AIX nodes to the cluster. To add Linux nodes, see Chapter 6, Adding Linux nodes
to the cluster,” on page 53. For information about installing the AIX operating
system and adding cluster nodes at the same time, see Chapter 7, “Installing
the AIX operating system and adding nodes,” on page 61. If you need to update
the CSM level for your AIX nodes, see Chapter 11, “Maintaining CSM software,”
on page 89. Before you add AIX nodes Before you begin the installation
steps, consider the following: v You have set up the management server. v You
have defined the nodes to be added to the cluster.Summary of the steps for adding AIX
nodes __ v “Step 1. Check node software
requirements” __ v “Step 2. Store hardware control point user IDs and
passwords” __ v “Step 3. Verify the node definitions” on page 46 __ v “Step 4.
Create CSM node groups (optional)” on page 47 __ v “Step 5. Prepare
customization scripts (optional)” on page 48 __ v “Step 6. Add the AIX nodes to
the cluster” on page 48 __ v “Step 7. Verify that the nodes are added” on page
50Step 1. Check node software
requirements For information about AIX cluster
node requirements, see Chapter 2, “Planning for Cluster Systems Management,” on
page 5. If you are upgrading to a new version of CSM, see Chapter 11,
“Maintaining CSM software,” on page 89. Step
2. Store hardware control point user IDs and passwords The systemid command stores the user ID and
password required for internal programs to access remote hardware. You must run
the command for each hardware control point in the cluster except for those
associated with SP Node or p660 servers. (In other words you do not have to run
the systemid command for any hardware control
points that are to be used with a power method of csp.) The step is required for hardware
control. For complete information about hardware control points for the
cluster, see CSM for AIX 5L: Hardware Control
Guide. ©
Copyright IBM Corp. 2002, 2003 45 ||||||||||||||||||
If using: Do this: Command line HMC-attached pSeries hardware: Issue the systemid command. For example, if the host
name of the HMC is hmc1 and the user ID is hscroot, issue the following command: systemid hmc1 hscroot You will be prompted for a password
for the user ID you specified. IntelliStation:
Issue the systemid command. For example, if the APC
MasterSwitch name is apc01.pok.com,, issue the following command: systemid apc01.pok.ibm.com USERID You will be prompted for a password
for the user ID you specified. The systemid
command stores the user ID and
password for remote hardware. xSeries
hardware: To configure xSeries servers, IBM
recommends changing the default hardware control point user IDs and passwords
using the utility disks and documentation provided with the hardware. For xSeries
RSAs the default user ID is ″USERID″ and the default password is ″PASSW0RD″
(P-A-S-S-W-zero-D). SP Nodes and p660 servers: Because user IDs and passwords are
not shipped with the hardware, you do not need to issue the systemid command. SMIT Issue the systemid command via SMIT. The fastpath is systemid. For example: smit systemid The systemid command stores the user ID and
password for remote hardware. Web-based System Manager or DCEM Not applicable. Step 3. Verify the node definitions After you have run definenode, the management server has all the
node information for CSM, and you are now ready to verify the node definitions.
This section tells you how to verify and customize the cluster node definitions
before you add the nodes. At this stage, you can make changes to any of the
node definitions. To determine whether the nodes have
been defined: If using: Do this: Command line Issue the lsnode command from the management server,
as follows: lsnode SMIT Issue the lsnode command via SMIT. The fastpath is csm_lsnode. For example: smit csm_lsnode Web-based System Manager or DCEM Use
the Nodes plug-in to display node information,
or use DCEM to run the lsnode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
The system responds with one line
for each node that has been correctly defined. If a node has not been defined,
it will not appear in the output for the lsnode
command. To display all the information about
each node: 46 CSM for AIX 5L: Planning and
Installation Guide |
If using: Do this: Command line Issue the lsnode command, from the management server,
with the –l (lowercase L, not uppercase i)
option: lsnode -l SMIT Issue the lsnode command via SMIT. The fastpath is csm_lsnode. For example: smit csm_lsnode Web-based System Manager or DCEM Use
the Nodes plug-in to display node information,
or use DCEM to run the lsnode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
The system responds with a list
(output), containing extended information, for each node that has been
correctly defined. If a node has not been defined, it does not appear in the
output for the lsnode command. Note that some of the
attributes for a node might have null values at this point. If something needs
to be corrected, you can either remove the node that was not correctly defined
and then run the definenode command again with the correct arguments,
or you can make the necessary changes to the attributes of the node. To remove a node before redefining
it: If using: Do this: Command line Issue the rmnode command on the management server: rmnode hostname SMIT Issue the rmnode command via SMIT. The fastpath is csm_rmnode. For example: smit csm_rmnode Web-based System Manager or DCEM Use
the Nodes plug-in to remove a node, or use
DCEM to run the rmnode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
To change the attributes of a node: If using: Do this: Command line Issue the chnode command from the management server: chnode hostname attr=value SMIT Issue the chnode command via SMIT. The fastpath is csm_chnode. For example: smit csm_chnode Web-based System Manager or DCEM Use
the Nodes plug-in to change attributes of a
node, or use DCEM to run the chnode
command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
See the man pages or the CSM for AIX 5L: Command and
Technical Reference for more information about the lsnode, rmnode, and chnode commands. Step 4. Create CSM node groups
(optional) Creating CSM node groups simplifies
the remaining installation process. To create a node group: Chapter 5. Adding AIX nodes to the
cluster 47 |
If using: Do this: Command line Issue the CSM nodegrp command. For example: nodegrp -a
clusternode1,clusternode2 cluster_grp SMIT
Issue the nodegrp command via SMIT. The fastpath is mk_group. For example: smit mk_group Web-based System Manager or DCEM Use
the Groups plug-in to create a node group. DCEM
can be started standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
When you use the nodegrp command, you supply the node names
followed by the name you want to designate for that group. In the example
above, clusternode1,clusternode2 are the nodes and cluster_grp is the name of the group that
includes those nodes. See the man pages or the CSM for AIX 5L: Command and
Technical Reference for more information about the nodegrp command. Step 5. Prepare customization
scripts (optional) Prepare any user-defined customization
scripts. These scripts are used in the next step when you add the AIX nodes to
the cluster. For information on CSM support for user-provided customization
scripts, see the CSM for AIX 5L: Administration Guide. Step
6. Add the AIX nodes to the cluster The
updatenode command adds the AIX nodes to the
cluster. Run the updatenode command for the AIX nodes that you
have defined. The updatenode command does the following for an
AIX node: v Configures the AIX node so that the management server can manage it
(changes the node attribute Mode
from PreManaged to Managed). v If remote shell authentication
is not already set up, automatically sets up remote shell authentication for
OpenSSH or rsh. See “Remote shell authentication”
on page 49. v Distributes configuration files if Configuration File Manager
(CFM) is set up. Setting up CFM before installing your nodes can save you from
needing to customize the nodes later. For information on configuring CFM, see
the CSM for Linux: Administration Guide. v Runs any user customization
scripts. See “Step 5. Prepare customization scripts (optional).”Before you run updatenode, ensure the following: v The
management server is installed and the AIX nodes are defined. v The AIX nodes
have all the prerequisite AIX software. For information on prerequisite
software, see the CSM README file and Chapter 2, “Planning for Cluster Systems
Management,” on page 5.If you need to update the CSM level for your AIX nodes,
see Chapter 11, “Maintaining CSM software,” on page 89. When a node has been
defined but not added to the cluster, its Mode
attribute is PreManaged. After a node has been defined and
added to the cluster with the 48 CSM for AIX 5L: Planning and
Installation Guide |||||||||||||||||||||||||||||
updatenode command, its Mode attribute changes to Managed, and the node becomes a managed
node of the cluster. Note that if the updatenode
command is not successful, the
node’s Mode attribute remains PreManaged
and the UpdateNodeFailed attribute is set to 1 (true).
To add all premanaged AIX nodes to your cluster and make
them managed nodes, do the following: If using: Do this: Command line Issue the updatenode command, as follows: updatenode -P -I The updatenode command with the -I option adds the premanaged AIX nodes to the cluster. Note that
the command does not update or install any software on the AIX node. For more
information, see the man page or the CSM
for AIX 5L: Command and Technical Reference.
SMIT Issue the updatenode command via SMIT. The fastpath is csm_update. For example: smit csm_update Note: When you run the updatenode command from SMIT, the command will
not set up remote shell access to the nodes. Make sure you do this manually
before running the updatenode command with SMIT. See “Setting up
remote access manually for AIX” on page 78 for information about how to do
this. Web-based System Manager or DCEM 1. Select the Nodes plug-in 2. From the Nodes menu, select Update Nodes. The Update Nodes dialog appears. 3. In the Nodes to update area, select Update all premanaged nodes. 4. In the Updates to perform area, select Update CSM client code and Update configuration files. 5. Click the OK button to install
the nodes. Remote shell authentication For authentication, the updatenode command prompts you for the root
password for the target nodes. As a result, you must either make the root
password common to all the target nodes, or run the updatenode command to each node, or group of
nodes, and provide the related passwords. The updatenode
command behaves differently,
depending on the values you specified with the RemoteShell and SetupRemoteShell attributes of the csmconfig command. v If you specified RemoteShell=/usr/bin/rsh
and SetupRemoteShell=1
(yes), the updatenode command sets up remote shell access
to all AIX PreManaged nodes. This is also true for all nodes in the cluster if
you used the –k flag with the updatenode command. To do this, the updatenode command will prompt you for the root
password. v If you specified RemoteShell=/usr/bin/ssh
and SetupRemoteShell=1
(yes), and OpenSSH is installed on
the management server and the nodes, the updatenode
command sets up secure shell access
to all PreManaged nodes. This is also true for all nodes in the cluster if you
used the –k flag with the updatenode command. To do this, the updatenode command will prompt you for the root
password. However, you will need to set up PAM authentication for OpenSSH
v3.4.0.5200 manually on all of the nodes. See “Using OpenSSH v3.4.0.5200 for
AIX nodes” on page 79 for more information. v If you specified SetupRemoteShell=0(no), the updatenode command does not set up remote
access for any of the nodes. Chapter
5. Adding AIX nodes to the cluster 49 ||||||||||||| |||||| ||| ||||| |||||||||||||||||||||||||
To
set up remote access manually, see “Setting up remote access manually for AIX”
on page 78. Step 7. Verify that the nodes are
added To verify that the nodes are added,
do the following: If using: Do this: Command line Issue the lsnode command, specifying the name of the
node. In this example, the name of the node is clstrn01. lsnode -n clstrn01 -a Mode,UpdatenodeFailed SMIT Issue the lsnode command via SMIT. The fastpath is csm_lsnode. For example: smit csm_lsnode Web-based System Manager or DCEM Use
the Nodes plug-in to display node information,
or use DCEM to run the lsnode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
The output of the lsnode command should consist of the name
of the node, followed by the values for these two attributes. For example: clstrn01: Managed, 0 If the Mode is not Managed, or if the UpdatenodeFailed attribute is equal to 1, then the
node has not been successfully added to the cluster. Do the following: v Check
the following log files for error and informational messages: – /var/log/csm/updatenode.log on the management server – /var/log/csm/install.log on each cluster nodev If the log
indicates that the mgmtsvr command failed, do the following: If using: Do this: Command line Issue the updatenode command, specifying the –k option and the name of the node. For
example: updatenode -k -n clstrn01 SMIT Issue the updatenode command via SMIT. The fastpath is csm_update. For example: smit csm_update Web-based System Manager or DCEM Use
the Nodes plug-in to update nodes, or use DCEM
to run the updatenode command. DCEM can be started
standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
v If
you are running the updatenode command to a large number of nodes,
you might be overloading the NFS server. If errors like Bad UMNT RPC: RPC: Timed out occur in the updatenode.log, try reducing the updatenode fanout. To do this, set the
CSM_FANOUT environment variable to a low value, such as 16, then run the updatenode command again. v Issue a remote
command on the node: If using: Do this: Command line Issue the dsh command, specifying the name of the
node. For example: dsh -n clstrn01 -s date SMIT Not applicable. Web-based System
Manager or DCEM Use DCEM to run a test command such as the date command on a specified node. DCEM
can be started standalone, or launched from the Nodes, Groups, or Commands plug-in of Web-based System Manager.
50 CSM for AIX 5L: Planning and
Installation Guide ||||
If the dsh command returns an error, see the CSM for AIX 5L:
Administration Guide for information on diagnosing dsh problems. Chapter 5. Adding AIX
nodes to the cluster 51
No comments:
Post a Comment