source: gpfs_3.1_ker2.6.20/share/man/man8/mmaddnode.8 @ 16

.TH mmaddnode 03/31/06
mmaddnode Command
.SH "Name"
.PP
\fBmmaddnode\fR Adds nodes to a GPFS cluster.
.SH "Synopsis"
.PP
\fBmmaddnode\fR \fB-N\fR
{\fINodeDesc\fR[,\fINodeDesc\fR...] |
\fINodeFile\fR}
.SH "Description"
.PP
Use the \fBmmaddnode\fR command to add nodes to an existing GPFS
cluster. On each new node, a mount point directory and character mode
device is created for each GPFS file system.
.PP
You must follow these rules when adding nodes to a GPFS cluster:
.RS +3
.HP 3
\(bu You may issue the command only from a node that already belongs to the
GPFS cluster.
.HP 3
\(bu While a node may mount file systems from multiple clusters, the node
itself may only be added to a single cluster using the \fBmmcrcluster\fR or \fBmmaddnode\fR command.
.HP 3
\(bu The nodes must be available for the command to be successful. If
any of the nodes listed are not available when the command is issued, a
message listing those nodes is displayed. You must correct the problem
on each node and reissue the command to add those nodes.
.RE
.SH "Parameters"
.PP
.RS +3
\fB-N \fINodeDesc\fR[,\fINodeDesc\fR...] |
\fINodeFile\fR
\fR
.RE
.RS +9
Specifies node descriptors, which provide information about nodes to be
added to the cluster.
.PP
.RS +3
\fB\fINodeFile\fR
\fR
.RE
.RS +9
Specifies a file containing a list of node descriptors (see below), one
per line, to be added to the cluster.
.RE
.PP
.RS +3
\fB\fINodeDesc\fR[,\fINodeDesc\fR...]
\fR
.RE
.RS +9
Specifies the list of nodes and node designations to be added to the GPFS
cluster. Node descriptors are defined as:
.sp
.nf
NodeName:NodeDesignations:AdminNodeName
.fi
.sp
.PP
where:
.RS +3
.HP 3
1. \fBNodeName\fR is the hostname or IP address to be used by the GPFS
daemons for node to node communication. 
.sp
The hostname or IP address must refer to the communications adapter over
which the GPFS daemons communicate. Alias interfaces are not
allowed. Use the original address or a name that is resolved by the
\fBhost\fR command to that original address. You may specify a node
using any of these forms:
.br
.sp
.RS +0.1i
.nf
.TS
tab(~);
 l l.
Format~Example
\fBShort hostname\fR~k145n01
\fBLong hostname\fR~k145n01.kgn.ibm.com
\fBIP address\fR~9.119.19.102
.TE
.sp
.fi
.RE
.HP 3
2. \fBNodeDesignations\fR is an optional, '-' separated list of
node roles.
.RS +3
.HP 3
\(bu \fBmanager\fR | \fB\fIclient\fR\fR Indicates whether a node is
part of the pool of nodes from which configuration mangers, file system
managers, and token managers are selected. The default is
\fBclient\fR.
.HP 3
\(bu \fBquorum\fR | \fB\fInonquorum\fR\fR Indicates whether a node is
counted as a quorum node. The default is \fBnonquorum\fR.
.RE
.HP 3
3. \fBAdminNodeName\fR is an optional field that consists of a node name
to be used by the administration commands to communicate between nodes.
.sp
.sp
If \fBAdminNodeName\fR is not specified, the \fBNodeName\fR value is
used.
.RE
.PP
You must provide a \fINodeDesc\fR for each node to be added to the GPFS
cluster.
.RE
.RE
.SH "Options"
.PP
NONE
.SH "Exit status"
.PP
.PP
.RS +3
\fB0
\fR
.RE
.RS +9
Successful completion.
.RE
.PP
.RS +3
\fBnonzero
\fR
.RE
.RS +9
A failure has occurred.
.RE
.SH "Security"
.PP
You must have root authority to run the \fBmmaddnode\fR command.
.PP
You may issue the \fBmmaddnode\fR command from any node in the GPFS
cluster.
.PP
When using the \fBrcp\fR and \fBrsh\fR commands for remote
communication, a properly configured \fB.rhosts\fR file must exist
in the root user's home directory on each node in the GPFS
cluster. If you have designated the use of a different remote
communication program on either the
\fBmmcrcluster\fR
or the
\fBmmchcluster\fR command, you must
ensure:
.RS +3
.HP 3
1. Proper authorization is granted to all nodes in the GPFS cluster.
.HP 3
2. The nodes in the GPFS cluster can communicate without the use of a
password, and without any extraneous messages.
.RE
.PP
\fBExamples\fR
.PP
To add nodes \fBk164n06\fR and \fBk164n07\fR as quorum nodes,
and further designating \fBk164n06\fR to be available as a
\fBmanager\fR node, issue this command: 
.sp
.nf
mmaddnode -N k164n06:quorum-manager,k164n07:quorum
.fi
.sp
.PP
To confirm the addition, issue this command:
.sp
.nf
mmlscluster
.fi
.sp
.PP
The system displays information similar to:
.sp
.nf
GPFS cluster information
========================
  GPFS cluster name:       cluster1.kgn.ibm.com
  GPFS cluster id:         680681562214606028
  GPFS UID domain:         cluster1.kgn.ibm.com
  Remote shell command:      /usr/bin/rsh
  Remote file copy command:  /usr/bin/rcp
GPFS cluster configuration servers:
-----------------------------------
  Primary server:    k164n07.kgn.ibm.com
  Secondary server:  k164n04.kgn.ibm.com
Node  Daemon node name   IP address    Admin node name  Designation
-------------------------------------------------------------------
 1  k164n04.kgn.ibm.com  198.117.68.68  k164n04.kgn.ibm.com  quorum
 2  k164n07.kgn.ibm.com  198.117.68.71  k164n07.kgn.ibm.com  quorum
 3  k164n06.kgn.ibm.com  198.117.68.70  k164n06.kgn.ibm.com quorum-manager
.fi
.sp
.SH "See also"
.PP
mmchconfig Command
.PP
mmcrcluster Command
.PP
mmchcluster Command
.PP
mmdelnode Command
.PP
mmlscluster Command
.SH "Location"
.PP
\fB/usr/lpp/mmfs/bin\fR
.PP