IBM General Parallel File System for AIX: Administration and Programming Reference

mmcrcluster Command

Name

mmcrcluster - Creates a GPFS cluster from a set of nodes.

Synopsis

mmcrcluster -t cltype -n NodeFile -p PrimaryServer [-s SecondaryServer] [-r RemoteShellCommand] [-R RemoteFileCopyCommand]

Description

Use the mmcrcluster command to create a GPFS cluster from an existing HACMP cluster. There can only be one GPFS cluster per HACMP cluster.

Upon successful completion of the mmcrcluster command, the /var/mmfs/gen/mmsdrfs and the /var/mmfs/gen/mmfsNodeData files are created on each of the nodes in the cluster. These files should not be deleted under any circumstances. For further information, see the IBM General Parallel File System for AIX: Concepts, Planning, and Installation Guide.

Parameters

-n NodeFile: NodeFile consists of a list of nodes, one per line, to be included in the GPFS cluster.
-p PrimaryServer: Specifies the primary GPFS cluster data server node used to store the GPFS cluster data. This node must be a member of the GPFS cluster.
-s SecondaryServer: Specifies the secondary GPFS cluster data server node used to store the GPFS cluster data. This node must be a member of the GPFS cluster.
It is suggested that you specify a secondary GPFS cluster data server to prevent the loss of configuration data in the event your primary GPFS cluster data server goes down.

You must follow these rules when creating your cluster:

The node must be available for the command to be successful. If any of the nodes listed are not available when the command is issued, a message listing those nodes is displayed. You must correct the problem on each node and reissue the mmaddcluster command to add those nodes.
A node may only belong to one GPFS cluster at a time.
The node must be a properly configured member of your HACMP cluster.

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

Format	Example
Short hostname	k145n01
Long hostname	k145n01.kgn.ibm.com
IP address	9.119.19.102

Options

-r RemoteShellCommand: Specifies the fully qualified pathname for the remote shell program to be used by GPFS. The default value is /usr/bin/rsh.
The remote shell command must adhere to the same syntax form as rsh but may implement an alternate authentication mechanism.
-R RemoteFileCopy: Specifies the fully qualified pathname for the remote file copy program to be used by GPFS. The default value is /usr/bin/rcp.
The remote copy command must adhere to the same syntax form as rcp but may implement an alternate authentication mechanism.
-t cltype: Specifies the type of cluster. The only valid value is hacmp .

Exit status

0: Successful completion.
1: A failure has occurred.

Security

You must have root authority to run the mmcrcluster command.

You may issue the mmcrcluster command from any node in the GPFS cluster.

A properly configured /.rhosts file must exist in the root user's home directory on each node in the GPFS cluster. If you have designated the use of a different remote communication program on either the mmcrcluster or the mmchcluster command, you must insure:

Proper authorization is granted to all nodes in the GPFS cluster.
The nodes in the GPFS cluster can communicate without the use of a password.

Examples

To create a GPFS cluster made of all of the nodes listed in the file nodelist.e100, using node k145n08 as the primary server, and node k145n06 as the secondary server, issue:

mmcrcluster -t hacmp -p k145n08 -s k145n06 -n /u/cladmin/hacmp/installs/nodelist.e100

To confirm the creation, enter:

mmlscluster

The system displays information similar to:

GPFS cluster information                           
========================                           
  Cluster id:  gpfs0103263/15/01M03                
  Remote shell command:      /usr/bin/rsh          
  Remote file copy command:  /usr/bin/rcp          
                                                   
GPFS cluster data repository servers:              
-------------------------------------              
  Primary server:    k145n08.kgn.ibm.com        
  Secondary server:  k145n06.kgn.ibm.com        
                                                                                                      
Cluster nodes that are not assigned to a nodeset:  
-------------------------------------------------  
  1  k145n06  9.114.133.06  k145n06.kgn.ibm.com  
  2  k145n08  9.114.133.08  k145n08.kgn.ibm.com  
  3  k145n31  9.114.133.31  k145n31.kgn.ibm.com  
  4  k145n32  9.114.133.32  k145n32.kgn.ibm.com  
  5  k145n33  9.114.133.33  k145n33.kgn.ibm.com  
  6  k145n34  9.114.133.34  k145n34.kgn.ibm.com  
  7  k145n35  9.114.133.35  k145n35.kgn.ibm.com  
  8  k145n36  9.114.133.36  k145n36.kgn.ibm.com  
  9  k145n37  9.114.133.37  k145n37.kgn.ibm.com  
  10  k145n38  9.114.133.38  k145n38.kgn.ibm.com 
  11  k145n39  9.114.133.39  k145n39.kgn.ibm.com 
  12  k145n40  9.114.133.40  k145n40.kgn.ibm.com 
  13  k145n41  9.114.133.41  k145n41.kgn.ibm.com 
  14  k145n42  9.114.133.42  k145n42.kgn.ibm.com 
  15  k145n43  9.114.133.43  k145n43.kgn.ibm.com 
  16  k145n44  9.114.133.44  k145n44.kgn.ibm.com 
  17  k145n45  9.114.133.45  k145n45.kgn.ibm.com 
  18  k145n46  9.114.133.46  k145n46.kgn.ibm.com 
  19  k145n47  9.114.133.47  k145n47.kgn.ibm.com

See also

Location

/usr/lpp/mmfs/bin

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]