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

Adding nodes to a GPFS cluster

You can add nodes to an existing GPFS cluster by issuing the mmaddcluster command. When adding nodes to a GPFS cluster it is not necessary to manually import the existing volume groups. The mmaddcluster command ensures the nodes being added inherit the volume groups of the GPFS cluster. You must follow these rules when adding nodes to a GPFS cluster:

• You may only issue the command from a node that already belongs to the GPFS 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 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.

To add nodes k145n06 and k145n08 to the GPFS cluster, enter:

mmaddcluster k145n06,k145n08

The system displays information similar to:

mmaddcluster: Command successfully completed 

To confirm the addition of the nodes, 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:    k145n43.kgn.ibm.com        
  Secondary server:  k145n44.kgn.ibm.com        
                                                   
Nodes in nodeset set1:                                
----------------------                                
  1  k145n29  9.114.133.29  k145n29.kgn.ibm.com  
  2  k145n30  9.114.133.30  k145n30.kgn.ibm.com  
  3  k145n31  9.114.133.31  k145n31.kgn.ibm.com  
  4  k145n32  9.114.133.32  k145n32.kgn.ibm.com  
                                                   
Nodes in nodeset set2:                              
----------------------                              
  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 
                                                   
Cluster nodes that are not assigned to a nodeset:  
-------------------------------------------------  
  19  k145n47  9.114.133.47  k145n47.kgn.ibm.com 
  20  k145n06  9.114.133.06  k145n06.kgn.ibm.com
  21  k145n08  9.114.133.08  k145n08.kgn.ibm.com
                                                   
 

See the mmaddcluster Command and the mmlscluster Command for complete usage information.