mmconfig - Defines a new GPFS nodeset and configures GPFS prior to creating file systems.
Synopsis
mmconfig {-a | -n NodeFile } [-A] [-C NodesetId] [-D dataStructureDump] [-M maxFilesToCache] [-p pagepool] [-U{yes | no}] [-V {yes | no}]
Description
The mmconfig command defines a new GPFS nodeset and configures GPFS prior to creating file systems. Before creating a GPFS nodeset, all of the nodes that are to be included in the nodeset must be part of the GPFS cluster. For further information see the mmcrcluster Command and the mmaddcluster Command.
Upon successful completion of the mmconfig command these tasks are performed on all specified nodes:
Parameters
The hostname or IP address used for a node must refer to the adapter port
over which the GPFS daemons communicate. Alias interfaces are not
allowed. Use the original address or a name that is resolved by the
host command to that original address. You may specify a node
using any of these forms:
| Format | Example |
|---|---|
| Short hostname | k145n01 |
| Long hostname | k145n01.kgn.ibm.com |
| IP address | 9.119.19.102 |
NodeName may be optionally followed by a use designation. All nodes in the nodeset may not be designated as client nodes. The designation specifies whether or not the node should be included in the pool of nodes from which the File System Manager node is chosen. For further information on the roles of nodes as File System Managers, see the IBM General Parallel File System for AIX: Concepts, Planning, and Installation Guide and search for File System Manager. The default is to have the node included in the pool.
Options
If you do not provide an identifier, the system assigns one. The system assigns each nodeset an integer identifier, beginning with one and increasing sequentially.
It is suggested that you create a directory for the placement of certain problem determination information. This can be a symbolic link to another location if more space can be found there. It should not be placed in a GPFS file system as it might not be available should GPFS fail. If a problem should occur, GPFS may write 200MB or more of problem determination data into the directory. These files must be manually removed when any problem determination is complete. This should be done promptly so that a NOSPACE condition is not encountered during the next failure.
Exit status
If a node is down or is not a member of the GPFS cluster, the mmconfig command fails. If the node is not a member of the GPFS cluster, you must:
Security
You must have root authority to run the mmconfig command.
In an SP environment:
For further information, see the latest IBM Parallel System Support Programs for AIX: Administration Guide, IBM Parallel System Support Programs for AIX: Command and Technical Reference, and RS/6000: Planning Volume 2, Control Workstation and Software Environment manuals at www.rs6000.ibm.com/resource/aix_resource/sp_books/pssp. Search for information on sysctl.
In an HACMP environment:
Examples
To configure all of the nodes listed in the file, system_1, for the new nodeset, set1, and have GPFS automatically started when the nodes come up, enter:
mmconfig -n /gpfsAdmin/system_1 -A -C set1
To confirm what the GPFS configuration is, enter:
mmlsconfig set1
The system displays information similar to:
Configuration data for nodeset set1:
-----------------------------------
pagepool 20M
dataStructureDump /log/mmfs
multinode yes
autoload yes
useSingleNodeQuorum no
wait4RVSD no
comm_protocol TCP
clusterType sp
group Gpfs.set1
recgroup GpfsRec.set1
useDiskLease no
File systems in nodeset set1:
----------------------------
(none)
See also
Location
/usr/lpp/mmfs/bin