mmdelcluster - Deletes nodes from a GPFS cluster.
Synopsis
mmdelcluster {-n NodeFile | NodeName[,NodeName ...]}
Description
Use the mmdelcluster command to delete nodes from a GPFS cluster. You must follow these rules when deleting nodes:
Upon successful completion of the mmdelcluster command, the specified nodes are deleted from the GPFS cluster. The nodes can no longer be used by GPFS file systems within the GPFS cluster.
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 |
Options
NONE
Exit status
Security
You must have root authority to run the mmdelcluster command.
You may only issue the mmdelcluster command from a node that will remain in the GPFS cluster.
When using rcp and rsh for remote communication, 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:
Examples
To delete the nodes k145n08, k145n09, and k145n10, enter:
mmdelcluster k145n08,k145n09,k145n10
To confirm the deletion, 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 1:
-------------------
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 2:
---------------------
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
See also
Location
/usr/lpp/mmfs/bin