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

Last change on this file since 16 was 16, checked in by rock, 16 years ago
File size: 4.9 KB
Line 
1.TH mmgetstate 02/16/06
2mmgetstate Command
3.SH "Name"
4.PP
5The \fBmmgetstate\fR command displays the state of the GPFS daemon on one
6or more nodes.
7.SH "Synopsis"
8.PP
9\fBmmgetstate\fR [\fB-L\fR] [\fB-s\fR]
10[\fB-v\fR] [\fB-a\fR | \fB-N\fR
11{\fINode\fR[,\fINode\fR...] | \fINodeFile\fR |
12\fINodeClass\fR}]
13.SH "Description"
14.PP
15Use the \fBmmgetstate\fR command to show the state of the GPFS daemon on
16one or more nodes.
17.SH "Parameters"
18.PP
19.RS +3
20\fB-a
21\fR
22.RE
23.RS +9
24List all nodes in the GPFS cluster. The option does not display
25information for nodes that cannot be reached. You may obtain more
26information if you specify the \fB-v\fR option.
27.RE
28.PP
29.RS +3
30\fB-N {\fINode\fR[,\fINode\fR...] |
31\fINodeFile\fR | \fINodeClass\fR}
32\fR
33.RE
34.RS +9
35Directs the \fBmmgetstate\fR command to return GPFS daemon information
36for a set of nodes. For information on how to specify node names, see \fISpecifying nodes as input to GPFS commands\fR
37in \fIGPFS: Administration and Programming Reference\fR.
38.PP
39This command does not support a \fINodeClass\fR of
40\fBmount\fR.
41.RE
42.SH "Options"
43.PP
44.RS +3
45\fB-L
46\fR
47.RE
48.RS +9
49Display quorum, number of nodes up, total number of nodes, and other
50extended node information.
51.RE
52.PP
53.RS +3
54\fB-s
55\fR
56.RE
57.RS +9
58Display summary information such as: number of local and remote
59nodes that have joined in the cluster, number of quorum nodes.
60.RE
61.PP
62.RS +3
63\fB-v
64\fR
65.RE
66.RS +9
67Display intermediate error messages.
68.RE
69.PP
70The GPFS states recognized and displayed by this command are:
71.PP
72.RS +3
73\fBactive
74\fR
75.RE
76.RS +9
77GPFS is ready for operations.
78.RE
79.PP
80.RS +3
81\fBarbitrating
82\fR
83.RE
84.RS +9
85A node is trying to form a quorum with the other available nodes.
86.RE
87.PP
88.RS +3
89\fBdown
90\fR
91.RE
92.RS +9
93GPFS daemon is not running on the node.
94.RE
95.PP
96.RS +3
97\fBunknown
98\fR
99.RE
100.RS +9
101Unknown value. Node cannot be reached or some other error
102occurred.
103.RE
104.SH "Exit status"
105.PP
106.PP
107.RS +3
108\fB0
109\fR
110.RE
111.RS +9
112Successful completion.
113.RE
114.PP
115.RS +3
116\fBnonzero
117\fR
118.RE
119.RS +9
120A failure has occurred.
121.RE
122.SH "Security"
123.PP
124You must have root authority to run the \fBmmgetstate\fR command.
125.PP
126When using the \fBrcp\fR and \fBrsh\fR commands for remote
127communication, a properly configured \fB.rhosts\fR file must exist
128in the root user's home directory on each node in the GPFS
129cluster. If you have designated the use of a different remote
130communication program on the
131\fBmmcrcluster\fR or the
132\fBmmchcluster\fR command, you must ensure:
133.RS +3
134.HP 3
1351. Proper authorization is granted to all nodes in the GPFS cluster.
136.HP 3
1372. The nodes in the GPFS cluster can communicate without the use of a
138password, and without any extraneous messages.
139.RE
140.SH "Examples"
141.RS +3
142.HP 3
1431. To display the quorum, the number of nodes up, and the total number of
144nodes for the GPFS cluster, issue:
145.sp
146.nf
147mmgetstate -a -L
148.fi
149.sp
150.sp
151The system displays output similar to:
152.sp
153.nf
154Node number  Node name  Quorum  Nodes up Total nodes  GPFS state
155----------------------------------------------------------------
156       1      k154gn01      3        5        8       active
157       2      k154gn02      3        5        8       active
158       3      k154gn09      3        5        8       active
159       4      k154gn10      3        5        8       active
160       5      k155gn01      3        5        8       active
161       6      k154gn02      3        5        8       down
162       7      k154gn09      3        5        8       down
163       8      k154gn10      3        5        8       down
164.fi
165.sp
166.sp
167The 3 under the Quorum column means that you must have three quorum nodes
168up to achieve quorum.
169.HP 3
1702. This is an example of a cluster using node quorum with tiebreaker
171disks. Note the * in the Quorum field, which indicates that tiebreaker
172disks are being used:
173.sp
174.nf
175mmgetstate -a -L
176.fi
177.sp
178The system displays output similar to:
179.sp
180.nf
181Node    Node       Nodes Total GPFS
182number  name Quorum  up  nodes state   Remarks
183----------------------------------------------
184 1      k5n91   5*   8    21   active
185 2      k5n92   5*   8    21   active  quorum node
186 3      k5n94   5*   8    21   active
187 5      k5n96   5*   8    21   active
188 6      k5n97   5*   8    21   active  quorum node
189 7      k5n98   5*   8    21   active
190 8      k5n99   5*   8    21   active  quorum node                                                           
191.fi
192.sp
193.HP 3
1943. To displays summary information, issue this command:
195.sp
196.nf
197mmgetstate -s
198.fi
199.sp
200The system displays output similar to:
201.sp
202.nf
203Node number Node name GPFS state
204------------------------------------------
2051 k154n05 active
206Summary information
207---------------------
208Number of nodes defined in the cluster: 8
209Number of local nodes active in the cluster: 8
210Number of remote nodes joined in this cluster: 0
211Number of quorum nodes defined in the cluster: 2
212Number of quorum nodes active in the cluster: 2
213Quorum = 1*, Quorum achieved
214.fi
215.sp
216.RE
217.SH "See also"
218.PP
219mmchconfig Command
220.PP
221mmcrcluster Command
222.PP
223mmshutdown Command
224.PP
225mmstartup Command
226.SH "Location"
227.PP
228\fB/usr/lpp/mmfs/bin\fR
Note: See TracBrowser for help on using the repository browser.