1 | .TH mmpmon 02/16/06 |
---|
2 | mmpmon Command |
---|
3 | .SH "Name" |
---|
4 | .PP |
---|
5 | \fBmmpmon\fR - Manages performance monitoring and displays |
---|
6 | performance information. |
---|
7 | .SH "Synopsis" |
---|
8 | .PP |
---|
9 | \fBmmpmon\fR [\fB-i\fR \fICommandFile\fR] |
---|
10 | [\fB-d\fR \fIIntegerDelayValue\fR] [\fB-p\fR] |
---|
11 | [\fB-r\fR \fIIntegerRepeatValue\fR] [\fB-s\fR] |
---|
12 | [\fB-t\fR \fIIntegerTimeoutValue\fR] |
---|
13 | .SH "Description" |
---|
14 | .PP |
---|
15 | Before attempting to use \fBmmpmon\fR, IBM suggests that you |
---|
16 | review this command entry, then read the entire chapter, |
---|
17 | \fIMonitoring GPFS I/O performance with the mmpmon |
---|
18 | command\fR in |
---|
19 | \fIGeneral Parallel File |
---|
20 | System: Advanced Administration Guide\fR. |
---|
21 | .PP |
---|
22 | Use the \fBmmpmon\fR command to manage GPFS performance monitoring |
---|
23 | functions and display performance monitoring data. The \fBmmpmon\fR |
---|
24 | command reads requests from an input file or standard input (stdin), and |
---|
25 | writes responses to standard output (stdout). Error messages go to |
---|
26 | standard error (stderr). Prompts, if not suppressed, go to |
---|
27 | stderr. |
---|
28 | .PP |
---|
29 | When running \fBmmpmon\fR in such a way that it continually reads input |
---|
30 | from a pipe (the driving script or application never intends to send an |
---|
31 | end-of-file to \fBmmpmon\fR), set the \fB-r\fR option value to 1 (or use |
---|
32 | the default value of 1) to prevent \fBmmpmon\fR from caching the input |
---|
33 | records. This avoids unnecessary memory consumption. |
---|
34 | .PP |
---|
35 | \fBResults\fR |
---|
36 | .PP |
---|
37 | The performance monitoring request is sent to the GPFS daemon running on |
---|
38 | the same node that is running the \fBmmpmon\fR command. |
---|
39 | .PP |
---|
40 | All results from the request are written to stdout. |
---|
41 | .PP |
---|
42 | There are two output formats: |
---|
43 | .RS +3 |
---|
44 | .HP 3 |
---|
45 | \(bu Human readable, intended for direct viewing. |
---|
46 | .sp |
---|
47 | In this format, the results are keywords that describe the value presented, |
---|
48 | followed by the value. For example: |
---|
49 | .sp |
---|
50 | .nf |
---|
51 | disks: 2 |
---|
52 | .fi |
---|
53 | .sp |
---|
54 | .HP 3 |
---|
55 | \(bu Machine readable, an easily parsed format intended for further analysis by |
---|
56 | scripts or applications. |
---|
57 | .sp |
---|
58 | In this format, the results are strings with values presented as |
---|
59 | keyword/value pairs. The keywords are delimited by underscores (_) and |
---|
60 | blanks to make them easier to locate. |
---|
61 | .RE |
---|
62 | .PP |
---|
63 | For details on how to interpret the \fBmmpmon\fR command results, |
---|
64 | see |
---|
65 | \fIMonitoring GPFS I/O performance with the |
---|
66 | mmpmon command\fR in |
---|
67 | \fIGeneral |
---|
68 | Parallel File System: Advanced Administration |
---|
69 | Guide\fR. |
---|
70 | .SH "Parameters" |
---|
71 | .PP |
---|
72 | .RS +3 |
---|
73 | \fB-i \fICommandFile\fR |
---|
74 | \fR |
---|
75 | .RE |
---|
76 | .RS +9 |
---|
77 | The input file contains \fBmmpmon\fR command requests, one per |
---|
78 | line. Use of the \fB-i\fR flag implies use of the \fB-s\fR |
---|
79 | flag. For interactive use, just omit the \fB-i\fR flag. In |
---|
80 | this case, the input is then read from stdin, allowing \fBmmpmon\fR to take |
---|
81 | keyboard input or output piped from a user script or application |
---|
82 | program. |
---|
83 | .PP |
---|
84 | Leading blanks in the input file are ignored. A line beginning with |
---|
85 | a pound sign (#) is treated as a comment. Leading blanks in a line |
---|
86 | whose first non-blank character is a pound sign (#) are ignored. |
---|
87 | .PP |
---|
88 | This table describes the \fBmmpmon\fR requests. |
---|
89 | .br |
---|
90 | .PP |
---|
91 | \fBTable 7. Input requests to the mmpmon command\fR |
---|
92 | .br |
---|
93 | .sp |
---|
94 | .RS +0.1i |
---|
95 | .nf |
---|
96 | .TS |
---|
97 | tab(~); |
---|
98 | l l. |
---|
99 | Request Description |
---|
100 | -------------------------------------------------------- |
---|
101 | fs_io_s Display I/O statistics |
---|
102 | per mounted file system |
---|
103 | io_s Display I/O statistics |
---|
104 | for the entire node |
---|
105 | nlist add \fIname\fR[\fIname\fR...] Add node names to a list |
---|
106 | of nodes for processing |
---|
107 | nlist del Delete a node list |
---|
108 | nlist new \fIname\fR[\fIname\fR...] Create a new node list |
---|
109 | nlist s Show the contents of the |
---|
110 | current node list |
---|
111 | nlist sub \fIname\fR[\fIname\fR...] Delete node names from a |
---|
112 | list of nodes for processing |
---|
113 | once \fIrequest\fR Indicates that the request |
---|
114 | is to be performed only once |
---|
115 | reset Reset statistics to zero |
---|
116 | rhist nr Change the request histogram |
---|
117 | facility request size and |
---|
118 | latency ranges |
---|
119 | rhist off Disable the request histogram |
---|
120 | facility. This is the default. |
---|
121 | rhist on Enable the request histogram |
---|
122 | facility |
---|
123 | rhist p Display the request histogram |
---|
124 | facility pattern |
---|
125 | rhist reset Reset the request histogram |
---|
126 | facility data to zero |
---|
127 | rhist s Display the request histogram |
---|
128 | facility statistics values |
---|
129 | source \fIfilename\fR Read \fBmmpmon\fR requests from |
---|
130 | a file |
---|
131 | ver Display \fBmmpmon\fR version |
---|
132 | .TE |
---|
133 | .sp |
---|
134 | .fi |
---|
135 | .RE |
---|
136 | .RE |
---|
137 | .SH "Options" |
---|
138 | .PP |
---|
139 | .RS +3 |
---|
140 | \fB-d \fIIntegerDelayValue\fR |
---|
141 | \fR |
---|
142 | .RE |
---|
143 | .RS +9 |
---|
144 | Specifies a number of milliseconds to sleep after one invocation of all |
---|
145 | the requests in the input file. The default value is 1000. This |
---|
146 | value must be an integer greater than or equal to 500 and less than or equal |
---|
147 | to 8000000. |
---|
148 | .PP |
---|
149 | The input file is processed as follows: The first request is |
---|
150 | processed, it is sent to the GPFS daemon, the responses for this request are |
---|
151 | received and processed, the results for this request are displayed, and then |
---|
152 | the next request is processed and so forth. When all requests from the |
---|
153 | input file have been processed once, the \fBmmpmon\fR command sleeps for |
---|
154 | the specified number of milliseconds. When this time elapses, |
---|
155 | \fBmmpmon\fR wakes up and processes the input file again, depending on the |
---|
156 | value of the \fB-r\fR flag. |
---|
157 | .RE |
---|
158 | .PP |
---|
159 | .RS +3 |
---|
160 | \fB-p |
---|
161 | \fR |
---|
162 | .RE |
---|
163 | .RS +9 |
---|
164 | Indicates to generate output that can be parsed by a script or |
---|
165 | program. If this option is not specified, human readable output is |
---|
166 | produced. |
---|
167 | .RE |
---|
168 | .PP |
---|
169 | .RS +3 |
---|
170 | \fB-r \fIIntegerRepeatValue\fR |
---|
171 | \fR |
---|
172 | .RE |
---|
173 | .RS +9 |
---|
174 | Specifies the number of times to run all the requests in the input |
---|
175 | file. |
---|
176 | .PP |
---|
177 | The default value is one. Specify an integer between zero and |
---|
178 | 8000000. Zero means to run forever, in which case processing continues |
---|
179 | until it is interrupted. This feature is used, for example, by a |
---|
180 | driving script or application program that repeatedly reads the result from a |
---|
181 | pipe. |
---|
182 | .PP |
---|
183 | The \fBonce\fR prefix directive can be used to override the |
---|
184 | \fB-r\fR flag. See the description of \fBonce\fR in |
---|
185 | \fIMonitoring GPFS I/O performance with the mmpmon |
---|
186 | command\fR in |
---|
187 | \fIGeneral Parallel File |
---|
188 | System: Advanced Administration Guide\fR. |
---|
189 | .RE |
---|
190 | .PP |
---|
191 | .RS +3 |
---|
192 | \fB-s |
---|
193 | \fR |
---|
194 | .RE |
---|
195 | .RS +9 |
---|
196 | Indicates to suppress the prompt on input. |
---|
197 | .PP |
---|
198 | Use of the \fB-i\fR flag implies use of the \fB-s\fR flag. For |
---|
199 | use in a pipe or with redirected input (<), the \fB-s\fR flag is |
---|
200 | preferred. If not suppressed, the prompts go to standard error |
---|
201 | (stderr). |
---|
202 | .RE |
---|
203 | .PP |
---|
204 | .RS +3 |
---|
205 | \fB-t \fIIntegerTimeoutValue\fR |
---|
206 | \fR |
---|
207 | .RE |
---|
208 | .RS +9 |
---|
209 | Specifies a number of seconds to wait for responses from the GPFS daemon |
---|
210 | before considering the connection to have failed. |
---|
211 | .PP |
---|
212 | The default value is 60. This value must be an integer greater than |
---|
213 | or equal to 1 and less than or equal to 8000000. |
---|
214 | .RE |
---|
215 | .SH "Exit status" |
---|
216 | .PP |
---|
217 | .PP |
---|
218 | .RS +3 |
---|
219 | \fB0 |
---|
220 | \fR |
---|
221 | .RE |
---|
222 | .RS +9 |
---|
223 | Successful completion. |
---|
224 | .RE |
---|
225 | .PP |
---|
226 | .RS +3 |
---|
227 | \fB1 |
---|
228 | \fR |
---|
229 | .RE |
---|
230 | .RS +9 |
---|
231 | Various errors (insufficient memory, input file not found, incorrect |
---|
232 | option, and so forth). |
---|
233 | .RE |
---|
234 | .PP |
---|
235 | .RS +3 |
---|
236 | \fB3 |
---|
237 | \fR |
---|
238 | .RE |
---|
239 | .RS +9 |
---|
240 | Either no commands were entered interactively, or there were no |
---|
241 | \fBmmpmon\fR commands in the input file. The input file was empty, |
---|
242 | or consisted of all blanks or comments. |
---|
243 | .RE |
---|
244 | .PP |
---|
245 | .RS +3 |
---|
246 | \fB4 |
---|
247 | \fR |
---|
248 | .RE |
---|
249 | .RS +9 |
---|
250 | \fBmmpmon\fR terminated due to a request that was not valid. |
---|
251 | .RE |
---|
252 | .PP |
---|
253 | .RS +3 |
---|
254 | \fB5 |
---|
255 | \fR |
---|
256 | .RE |
---|
257 | .RS +9 |
---|
258 | An internal error has occurred. |
---|
259 | .RE |
---|
260 | .PP |
---|
261 | .RS +3 |
---|
262 | \fB111 |
---|
263 | \fR |
---|
264 | .RE |
---|
265 | .RS +9 |
---|
266 | An internal error has occurred. A message will follow. |
---|
267 | .RE |
---|
268 | .PP |
---|
269 | \fBRestrictions\fR |
---|
270 | .RS +3 |
---|
271 | .HP 3 |
---|
272 | 1. Up to five instances of \fBmmpmon\fR may be run on a given node |
---|
273 | concurrently. However, concurrent users may interfere with each |
---|
274 | other. See |
---|
275 | \fIMonitoring GPFS I/O |
---|
276 | performance with the mmpmon command\fR in |
---|
277 | \fIGeneral Parallel File System: Advanced |
---|
278 | Administration Guide\fR. |
---|
279 | .HP 3 |
---|
280 | 2. Do not alter the input file while \fBmmpmon\fR is running. |
---|
281 | .HP 3 |
---|
282 | 3. The input file must contain valid input requests, one per line. |
---|
283 | When an incorrect request is detected by \fBmmpmon\fR, it issues an error |
---|
284 | message and terminates. Input requests that appear in the input file |
---|
285 | before the first incorrect request are processed by \fBmmpmon\fR. |
---|
286 | .RE |
---|
287 | .SH "Security" |
---|
288 | .PP |
---|
289 | The \fBmmpmon\fR command must be run by a user with root authority, on |
---|
290 | the node for which statistics are desired. |
---|
291 | .SH "Examples" |
---|
292 | .RS +3 |
---|
293 | .HP 3 |
---|
294 | 1. Assume that \fBinfile\fR contains these requests: |
---|
295 | .sp |
---|
296 | .nf |
---|
297 | ver |
---|
298 | io_s |
---|
299 | fs_io_s |
---|
300 | rhist off |
---|
301 | .fi |
---|
302 | .sp |
---|
303 | and this command is issued: |
---|
304 | .sp |
---|
305 | .nf |
---|
306 | mmpmon -i infile -r 10 -d 5000 |
---|
307 | .fi |
---|
308 | .sp |
---|
309 | The output (sent to stdout) is similar to this: |
---|
310 | .sp |
---|
311 | .nf |
---|
312 | mmpmon node 192.168.1.8 name node1 version 3.1.0 |
---|
313 | mmpmon node 192.168.1.8 name node1 io_s OK |
---|
314 | timestamp: 1083350358/935524 |
---|
315 | bytes read: 0 |
---|
316 | bytes written: 0 |
---|
317 | opens: 0 |
---|
318 | closes: 0 |
---|
319 | reads: 0 |
---|
320 | writes: 0 |
---|
321 | readdir: 0 |
---|
322 | inode updates: 0 |
---|
323 | mmpmon node 192.168.1.8 name node1 fs_io_s status 1 |
---|
324 | no file systems mounted |
---|
325 | mmpmon node 192.168.1.8 name node1 rhist off OK |
---|
326 | .fi |
---|
327 | .sp |
---|
328 | .sp |
---|
329 | The requests in the input file are run 10 times, with a delay of 5000 |
---|
330 | milliseconds (5 seconds) between invocations. |
---|
331 | .HP 3 |
---|
332 | 2. Here is the previous example with the \fB-p\fR flag: |
---|
333 | .sp |
---|
334 | .nf |
---|
335 | mmpmon -i infile -p -r 10 -d 5000 |
---|
336 | .fi |
---|
337 | .sp |
---|
338 | The output (sent to stdout) is similar to this: |
---|
339 | .sp |
---|
340 | .nf |
---|
341 | _ver_ _n_ 192.168.1.8 _nn_ node1 _v_ 2 _lv_ 3 _vt_ 0 |
---|
342 | _io_s_ _n_ 192.168.1.8 _nn_ node1 _rc_ 0 _t_ 1084195701 _tu_ 350714 _br_ 0 _bw_ 0 _oc_ 0 |
---|
343 | _cc_ 0 _rdc_ 0 _wc_ 0 _dir_ 0 _iu_ 0 |
---|
344 | _fs_io_s_ _n_ 192.168.1.8 _nn_ node1 _rc_ 1 _t_ 1084195701 _tu_ 364489 _cl_ - _fs_ -_rhist_\ |
---|
345 | _n_ 192.168.1.8 _nn_ node1 _req_ off _rc_ 0 _t_ 1084195701 _tu_ 378217 |
---|
346 | .fi |
---|
347 | .sp |
---|
348 | .HP 3 |
---|
349 | 3. This is an example of \fBfs_io_s\fR with a mounted file system: |
---|
350 | .sp |
---|
351 | .nf |
---|
352 | mmpmon node 198.168.1.8 name node1 fs_io_s OK |
---|
353 | cluster: node1.localdomain |
---|
354 | filesystem: gpfs1 |
---|
355 | disks: 1 |
---|
356 | timestamp: 1093352136/799285 |
---|
357 | bytes read: 52428800 |
---|
358 | bytes written: 87031808 |
---|
359 | opens: 6 |
---|
360 | closes: 4 |
---|
361 | reads: 51 |
---|
362 | writes: 83 |
---|
363 | readdir: 0 |
---|
364 | inode updates: 11 |
---|
365 | mmpmon node 198.168.1.8 name node1 fs_io_s OK |
---|
366 | cluster: node1.localdomain |
---|
367 | filesystem: gpfs2 |
---|
368 | disks: 2 |
---|
369 | timestamp: 1093352136/799285 |
---|
370 | bytes read: 87031808 |
---|
371 | bytes written: 52428800 |
---|
372 | opens: 4 |
---|
373 | closes: 3 |
---|
374 | reads: 12834 |
---|
375 | writes: 50 |
---|
376 | readdir: 0 |
---|
377 | inode updates: 9 |
---|
378 | .fi |
---|
379 | .sp |
---|
380 | .HP 3 |
---|
381 | 4. Here is the previous example with the \fB-p\fR flag: |
---|
382 | .sp |
---|
383 | .nf |
---|
384 | _fs_io_s_ _n_ 198.168.1.8 _nn_ node1 _rc_ 0 _t_ 1093352061 _tu_ 93867 _cl_ node1.localdomain |
---|
385 | _fs_ gpfs1 _d_ 1 _br_ 52428800 _bw_ 87031808 _oc_ 6 _cc_ 4 _rdc_ 51 _wc_ 83 _dir_ 0 _iu_ 10 |
---|
386 | _fs_io_s_ _n_ 198.168.1.8 _nn_ node1 _rc_ 0 _t_ 1093352061 _tu_ 93867 _cl_ node1.localdomain |
---|
387 | _fs_ gpfs2 _d_ 2 _br_ 87031808 _bw_ 52428800 _oc_ 4 _cc_ 3 _rdc_ 12834 _wc_ 50 _dir_ 0 _iu_ 8 |
---|
388 | .fi |
---|
389 | .sp |
---|
390 | This output consists of two strings. |
---|
391 | .HP 3 |
---|
392 | 5. This is an example of \fBio_s\fR with a mounted file system: |
---|
393 | .sp |
---|
394 | .nf |
---|
395 | mmpmon node 198.168.1.8 name node1 io_s OK |
---|
396 | timestamp: 1093351951/587570 |
---|
397 | bytes read: 139460608 |
---|
398 | bytes written: 139460608 |
---|
399 | opens: 10 |
---|
400 | closes: 7 |
---|
401 | reads: 12885 |
---|
402 | writes: 133 |
---|
403 | readdir: 0 |
---|
404 | inode updates: 14 |
---|
405 | .fi |
---|
406 | .sp |
---|
407 | .HP 3 |
---|
408 | 6. Here is the previous example with the \fB-p\fR flag: |
---|
409 | .sp |
---|
410 | .nf |
---|
411 | _io_s_ _n_ 198.168.1.8 _nn_ node1 _rc_ 0 _t_ 1093351982 _tu_ 356420 _br_ 139460608\ |
---|
412 | _bw_ 139460608 _oc_ 10 _cc_ 7 _rdc_ 0 _wc_ 133 _dir_ 0 _iu_ 14 |
---|
413 | .fi |
---|
414 | .sp |
---|
415 | This output consists of one string. |
---|
416 | .RE |
---|
417 | .PP |
---|
418 | For several more examples, see |
---|
419 | \fIMonitoring GPFS I/O performance with the mmpmon |
---|
420 | command\fR in |
---|
421 | \fIGeneral Parallel File |
---|
422 | System: Advanced Administration Guide\fR. |
---|
423 | .SH "Location" |
---|
424 | .PP |
---|
425 | \fB/usr/lpp/mmfs/bin\fR |
---|
426 | .PP |
---|