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

Last change on this file since 173 was 16, checked in by rock, 17 years ago
File size: 5.1 KB
Line 
1.TH mmaddnode 03/31/06
2mmaddnode Command
3.SH "Name"
4.PP
5\fBmmaddnode\fR Adds nodes to a GPFS cluster.
6.SH "Synopsis"
7.PP
8\fBmmaddnode\fR \fB-N\fR
9{\fINodeDesc\fR[,\fINodeDesc\fR...] |
10\fINodeFile\fR}
11.SH "Description"
12.PP
13Use the \fBmmaddnode\fR command to add nodes to an existing GPFS
14cluster. On each new node, a mount point directory and character mode
15device is created for each GPFS file system.
16.PP
17You must follow these rules when adding nodes to a GPFS cluster:
18.RS +3
19.HP 3
20\(bu You may issue the command only from a node that already belongs to the
21GPFS cluster.
22.HP 3
23\(bu While a node may mount file systems from multiple clusters, the node
24itself may only be added to a single cluster using the \fBmmcrcluster\fR or \fBmmaddnode\fR command.
25.HP 3
26\(bu The nodes must be available for the command to be successful. If
27any of the nodes listed are not available when the command is issued, a
28message listing those nodes is displayed. You must correct the problem
29on each node and reissue the command to add those nodes.
30.RE
31.SH "Parameters"
32.PP
33.RS +3
34\fB-N \fINodeDesc\fR[,\fINodeDesc\fR...] |
35\fINodeFile\fR
36\fR
37.RE
38.RS +9
39Specifies node descriptors, which provide information about nodes to be
40added to the cluster.
41.PP
42.RS +3
43\fB\fINodeFile\fR
44\fR
45.RE
46.RS +9
47Specifies a file containing a list of node descriptors (see below), one
48per line, to be added to the cluster.
49.RE
50.PP
51.RS +3
52\fB\fINodeDesc\fR[,\fINodeDesc\fR...]
53\fR
54.RE
55.RS +9
56Specifies the list of nodes and node designations to be added to the GPFS
57cluster. Node descriptors are defined as:
58.sp
59.nf
60NodeName:NodeDesignations:AdminNodeName
61.fi
62.sp
63.PP
64where:
65.RS +3
66.HP 3
671. \fBNodeName\fR is the hostname or IP address to be used by the GPFS
68daemons for node to node communication.
69.sp
70The hostname or IP address must refer to the communications adapter over
71which the GPFS daemons communicate. Alias interfaces are not
72allowed. Use the original address or a name that is resolved by the
73\fBhost\fR command to that original address. You may specify a node
74using any of these forms:
75.br
76.sp
77.RS +0.1i
78.nf
79.TS
80tab(~);
81 l l.
82Format~Example
83\fBShort hostname\fR~k145n01
84\fBLong hostname\fR~k145n01.kgn.ibm.com
85\fBIP address\fR~9.119.19.102
86.TE
87.sp
88.fi
89.RE
90.HP 3
912. \fBNodeDesignations\fR is an optional, '-' separated list of
92node roles.
93.RS +3
94.HP 3
95\(bu \fBmanager\fR | \fB\fIclient\fR\fR Indicates whether a node is
96part of the pool of nodes from which configuration mangers, file system
97managers, and token managers are selected. The default is
98\fBclient\fR.
99.HP 3
100\(bu \fBquorum\fR | \fB\fInonquorum\fR\fR Indicates whether a node is
101counted as a quorum node. The default is \fBnonquorum\fR.
102.RE
103.HP 3
1043. \fBAdminNodeName\fR is an optional field that consists of a node name
105to be used by the administration commands to communicate between nodes.
106.sp
107.sp
108If \fBAdminNodeName\fR is not specified, the \fBNodeName\fR value is
109used.
110.RE
111.PP
112You must provide a \fINodeDesc\fR for each node to be added to the GPFS
113cluster.
114.RE
115.RE
116.SH "Options"
117.PP
118NONE
119.SH "Exit status"
120.PP
121.PP
122.RS +3
123\fB0
124\fR
125.RE
126.RS +9
127Successful completion.
128.RE
129.PP
130.RS +3
131\fBnonzero
132\fR
133.RE
134.RS +9
135A failure has occurred.
136.RE
137.SH "Security"
138.PP
139You must have root authority to run the \fBmmaddnode\fR command.
140.PP
141You may issue the \fBmmaddnode\fR command from any node in the GPFS
142cluster.
143.PP
144When using the \fBrcp\fR and \fBrsh\fR commands for remote
145communication, a properly configured \fB.rhosts\fR file must exist
146in the root user's home directory on each node in the GPFS
147cluster. If you have designated the use of a different remote
148communication program on either the
149\fBmmcrcluster\fR
150or the
151\fBmmchcluster\fR command, you must
152ensure:
153.RS +3
154.HP 3
1551. Proper authorization is granted to all nodes in the GPFS cluster.
156.HP 3
1572. The nodes in the GPFS cluster can communicate without the use of a
158password, and without any extraneous messages.
159.RE
160.PP
161\fBExamples\fR
162.PP
163To add nodes \fBk164n06\fR and \fBk164n07\fR as quorum nodes,
164and further designating \fBk164n06\fR to be available as a
165\fBmanager\fR node, issue this command:
166.sp
167.nf
168mmaddnode -N k164n06:quorum-manager,k164n07:quorum
169.fi
170.sp
171.PP
172To confirm the addition, issue this command:
173.sp
174.nf
175mmlscluster
176.fi
177.sp
178.PP
179The system displays information similar to:
180.sp
181.nf
182GPFS cluster information
183========================
184  GPFS cluster name:       cluster1.kgn.ibm.com
185  GPFS cluster id:         680681562214606028
186  GPFS UID domain:         cluster1.kgn.ibm.com
187  Remote shell command:      /usr/bin/rsh
188  Remote file copy command:  /usr/bin/rcp
189GPFS cluster configuration servers:
190-----------------------------------
191  Primary server:    k164n07.kgn.ibm.com
192  Secondary server:  k164n04.kgn.ibm.com
193Node  Daemon node name   IP address    Admin node name  Designation
194-------------------------------------------------------------------
195 1  k164n04.kgn.ibm.com  198.117.68.68  k164n04.kgn.ibm.com  quorum
196 2  k164n07.kgn.ibm.com  198.117.68.71  k164n07.kgn.ibm.com  quorum
197 3  k164n06.kgn.ibm.com  198.117.68.70  k164n06.kgn.ibm.com quorum-manager
198.fi
199.sp
200.SH "See also"
201.PP
202mmchconfig Command
203.PP
204mmcrcluster Command
205.PP
206mmchcluster Command
207.PP
208mmdelnode Command
209.PP
210mmlscluster Command
211.SH "Location"
212.PP
213\fB/usr/lpp/mmfs/bin\fR
214.PP
Note: See TracBrowser for help on using the repository browser.