| 1 | .TH mmchmgr 02/16/06 |
|---|
| 2 | mmchmgr Command |
|---|
| 3 | .SH "Name" |
|---|
| 4 | .PP |
|---|
| 5 | \fBmmchmgr\fR - Assigns a file system manager node. |
|---|
| 6 | .SH "Synopsis" |
|---|
| 7 | .PP |
|---|
| 8 | \fBmmchmgr\fR \fIDevice\fR [\fINode\fR] |
|---|
| 9 | .SH "Description" |
|---|
| 10 | .PP |
|---|
| 11 | The \fBmmchmgr\fR command assigns a file system manager node. |
|---|
| 12 | .SH "Parameters" |
|---|
| 13 | .PP |
|---|
| 14 | .RS +3 |
|---|
| 15 | \fB\fIDevice\fR |
|---|
| 16 | \fR |
|---|
| 17 | .RE |
|---|
| 18 | .RS +9 |
|---|
| 19 | The device name of the file system for which the file system manager node |
|---|
| 20 | is to be changed. File system names need not be fully-qualified. |
|---|
| 21 | \fBfs0\fR is just as acceptable as \fB/dev/fs0\fR. |
|---|
| 22 | .PP |
|---|
| 23 | This must be the first parameter. |
|---|
| 24 | .RE |
|---|
| 25 | .PP |
|---|
| 26 | .RS +3 |
|---|
| 27 | \fB\fINode\fR |
|---|
| 28 | \fR |
|---|
| 29 | .RE |
|---|
| 30 | .RS +9 |
|---|
| 31 | The target node to be appointed as the new file system manager. If |
|---|
| 32 | no \fINode\fR is specified, the configuration manager selects the new file |
|---|
| 33 | system manager node. |
|---|
| 34 | .PP |
|---|
| 35 | For information on how to specify node names, see \fISpecifying nodes as input to GPFS commands\fR |
|---|
| 36 | in \fIGPFS: Administration and Programming Reference\fR. |
|---|
| 37 | .RE |
|---|
| 38 | .SH "Options" |
|---|
| 39 | .PP |
|---|
| 40 | NONE |
|---|
| 41 | .SH "Exit status" |
|---|
| 42 | .PP |
|---|
| 43 | .PP |
|---|
| 44 | .RS +3 |
|---|
| 45 | \fB0 |
|---|
| 46 | \fR |
|---|
| 47 | .RE |
|---|
| 48 | .RS +9 |
|---|
| 49 | Successful completion. |
|---|
| 50 | .RE |
|---|
| 51 | .PP |
|---|
| 52 | .RS +3 |
|---|
| 53 | \fBnonzero |
|---|
| 54 | \fR |
|---|
| 55 | .RE |
|---|
| 56 | .RS +9 |
|---|
| 57 | A failure has occurred. |
|---|
| 58 | .RE |
|---|
| 59 | .SH "Security" |
|---|
| 60 | .PP |
|---|
| 61 | You must have root authority to run the \fBmmchmgr\fR command. |
|---|
| 62 | .PP |
|---|
| 63 | You may issue the \fBmmchmgr\fR command from any node in the GPFS |
|---|
| 64 | cluster. |
|---|
| 65 | .PP |
|---|
| 66 | When using the \fBrcp\fR and \fBrsh\fR commands for remote |
|---|
| 67 | communication, a properly configured \fB.rhosts\fR file must exist |
|---|
| 68 | in the root user's home directory on each node in the GPFS |
|---|
| 69 | cluster. If you have designated the use of a different remote |
|---|
| 70 | communication program on either the |
|---|
| 71 | \fBmmcrcluster\fR |
|---|
| 72 | or the |
|---|
| 73 | \fBmmchcluster\fR command, you must |
|---|
| 74 | ensure: |
|---|
| 75 | .RS +3 |
|---|
| 76 | .HP 3 |
|---|
| 77 | 1. Proper authorization is granted to all nodes in the GPFS cluster. |
|---|
| 78 | .HP 3 |
|---|
| 79 | 2. The nodes in the GPFS cluster can communicate without the use of a |
|---|
| 80 | password, and without any extraneous messages. |
|---|
| 81 | .RE |
|---|
| 82 | .SH "Examples" |
|---|
| 83 | .PP |
|---|
| 84 | Assume the file system manager for the file system \fBgpfs1\fR is |
|---|
| 85 | currently \fBk164n05\fR. To migrate the file system manager |
|---|
| 86 | responsibilities to \fBk164n06\fR, issue this command: |
|---|
| 87 | .sp |
|---|
| 88 | .nf |
|---|
| 89 | mmchmgr gpfs1 k164n06 |
|---|
| 90 | .fi |
|---|
| 91 | .sp |
|---|
| 92 | .PP |
|---|
| 93 | The system displays information similar to: |
|---|
| 94 | .sp |
|---|
| 95 | .nf |
|---|
| 96 | GPFS: 6027-628 Sending migrate request to current manager node |
|---|
| 97 | 9.114.68.69 (k164n05). |
|---|
| 98 | GPFS: 6027-629 Node 9.14.68.69 (k164n05) resigned as manager for gpfs1 |
|---|
| 99 | GPFS: 6027-630 Node 9.14.68.70 (k164n06) appointed as manager for gpfs1 |
|---|
| 100 | .fi |
|---|
| 101 | .sp |
|---|
| 102 | .SH "See also" |
|---|
| 103 | .PP |
|---|
| 104 | mmlsmgr Command |
|---|
| 105 | .SH "Location" |
|---|
| 106 | .PP |
|---|
| 107 | \fB/usr/lpp/mmfs/bin\fR |
|---|
| 108 | .PP |
|---|
