source: gpfs_3.1_ker2.6.20/share/man/man8/mmchnsd.8 @ 219

Last change on this file since 219 was 16, checked in by rock, 17 years ago
File size: 5.0 KB
Line 
1.TH mmchnsd 02/16/06
2mmchnsd Command
3.SH "Name"
4.PP
5\fBmmchnsd\fR - Changes Network Shared Disk (NSD) configuration
6parameters.
7.SH "Synopsis"
8.PP
9\fBmmchnsd\fR
10{"\fIDiskDesc\fR[;\fIDiskDesc\fR...]"
11| \fB-F\fR \fIDescFile\fR}
12.SH "Description"
13.PP
14The \fBmmchnsd\fR command serves several purposes:
15.RS +3
16.HP 3
171. Change either or both the primary and backup NSD server nodes.
18.HP 3
192. Define a backup server node for an NSD that currently does not have
20one.
21.HP 3
223. Delete a backup server node for an NSD.
23.HP 3
244. Delete both the primary and backup NSD server nodes. The disk must
25now be SAN-attached to all nodes in the cluster.
26.HP 3
275. Assign a primary and, if specified, a backup NSD server node. Nodes
28that are not SAN-attached to the disk, or nodes that experience a local device
29driver failure, will now have access to the data over the network from these
30servers.
31.RE
32.PP
33You must follow these rules when changing NSDs:
34.RS +3
35.HP 3
36\(bu You must identify the disks by the NSD names that were given to them by
37the
38\fBmmcrnsd\fR command.
39.HP 3
40\(bu You must explicitly specify values for both the primary and backup NSD
41server nodes even if you are only changing one of them.
42.HP 3
43\(bu The file system that contains the NSD being changed must be unmounted
44prior to issuing the \fBmmchnsd\fR command.
45.HP 3
46\(bu The NSD must be properly connected to the new nodes prior to issuing the
47\fBmmchnsd\fR command.
48.HP 3
49\(bu This command cannot be used to change the \fIDiskUsage\fR or
50\fIFailureGroup\fR for an NSD. You must issue the \fBmmchdisk\fR command to change these.
51.HP 3
52\(bu To move a disk from one storage pool to another, use the \fBmmdeldisk\fR and \fBmmadddisk\fR commands.
53.HP 3
54\(bu You cannot change the name of the NSD.
55.RE
56.SH "Parameters"
57.PP
58.RS +3
59\fB\fIDiskDesc\fR
60\fR
61.RE
62.RS +9
63A descriptor for each NSD to be changed. Each descriptor is
64separated by a semicolon (;). The entire list must be enclosed in
65single or double quotation marks.
66.RE
67.PP
68.RS +3
69\fB\fIDescFile\fR
70\fR
71.RE
72.RS +9
73Specifies a file containing a list of disk descriptors, one per
74line.
75.PP
76Each disk descriptor must be specified in the form:
77.sp
78.nf
79DiskName:PrimaryServer:BackupServer
80.fi
81.sp
82.PP
83.RS +3
84\fB\fIDiskName\fR
85\fR
86.RE
87.RS +9
88The NSD name that was given to the disk by the \fBmmcrnsd\fR command.
89.RE
90.PP
91.RS +3
92\fB\fIPrimaryServer\fR
93\fR
94.RE
95.RS +9
96The name of the primary NSD server node.
97.PP
98If this field is omitted, the disk is assumed to be SAN-attached to all
99nodes in the cluster.
100.PP
101To change only the primary NSD server, ensure that if a backup NSD server
102exists that you specify it, or the backup NSD server will be deleted.
103Any parameter that is not specified defaults to null.
104.sp
105.nf
106DiskName:PrimaryServer:BackupServer
107.fi
108.sp
109.PP
110To remove the primary GPFS server, explicitly skip the parameter:
111.sp
112.nf
113DiskName
114.fi
115.sp
116.RE
117.PP
118.RS +3
119\fB\fIBackupServer\fR
120\fR
121.RE
122.RS +9
123The name of the backup NSD server node.
124.PP
125If the \fIPrimaryServer\fR has not been specified and this field is
126omitted, the disk is assumed to be SAN-attached to all nodes in the
127cluster.
128.PP
129To remove the backup NSD server, explicitly skip the parameter, but ensure
130you have specified the \fIPrimaryServer\fR or it will be removed
131also:
132.sp
133.nf
134DiskName:PrimaryServer
135.fi
136.sp
137.RE
138.PP
139For information on how to specify node names, see \fISpecifying nodes as input to GPFS commands\fR
140in \fIGPFS: Administration and Programming Reference\fR.
141.RE
142.SH "Options"
143.PP
144NONE
145.SH "Exit status"
146.PP
147.PP
148.RS +3
149\fB0
150\fR
151.RE
152.RS +9
153Successful completion.
154.RE
155.PP
156.RS +3
157\fBnonzero
158\fR
159.RE
160.RS +9
161A failure has occurred.
162.RE
163.SH "Security"
164.PP
165You must have root authority to run the \fBmmchnsd\fR command.
166.PP
167You may issue the \fBmmchnsd\fR command from any node in the GPFS
168cluster.
169.PP
170When using the \fBrcp\fR and \fBrsh\fR commands for remote
171communication, a properly configured \fB.rhosts\fR file must exist
172in the root user's home directory on each node in the GPFS
173cluster. If you have designated the use of a different remote
174communication program on either the
175\fBmmcrcluster\fR
176or the
177\fBmmchcluster\fR command, you must
178ensure:
179.RS +3
180.HP 3
1811. Proper authorization is granted to all nodes in the GPFS cluster.
182.HP 3
1832. The nodes in the GPFS cluster can communicate without the use of a
184password, and without any extraneous messages.
185.RE
186.SH "Examples"
187.PP
188If the disk \fBgpfs1nsd\fR is currently defined with
189\fBk145n05\fR as its primary server and \fBk145n07\fR as its backup
190NSD server, and you want to change the primary NSD server to
191\fBk145n09\fR, issue this command:
192.sp
193.nf
194mmchnsd "gpfs1nsd:k145n09:k145n07:::"
195.fi
196.sp
197.PP
198To confirm the changes, issue this command:
199.sp
200.nf
201mmlsnsd -d "gpfs1nsd"
202.fi
203.sp
204.PP
205The system displays information similar to:
206.sp
207.nf
208 File system   Disk name    Primary node             Backup node
209 ---------------------------------------------------------------
210 fs1           gpfs1nsd     k145n09                  k145n07
211\
212.fi
213.sp
214.SH "See also"
215.PP
216mmchdisk Command
217.PP
218mmcrcluster Command
219.PP
220mmcrnsd Command
221.PP
222mmlsnsd Command
223.SH "Location"
224.PP
225\fB/usr/lpp/mmfs/bin\fR
226.PP
Note: See TracBrowser for help on using the repository browser.