mmaddnode command

Adds nodes to a GPFS cluster.

Synopsis

mmaddnode -N {NodeDesc[,NodeDesc...] | NodeFile} [--accept]

Availability

Available on all IBM Spectrum Scale editions.

Description

Use the mmaddnode command to add nodes to an existing IBM Spectrum Scale cluster. On each new node, a mount point directory and character mode device is created for each GPFS file system.

Follow these rules when adding nodes to an IBM Spectrum Scale cluster:
  • You may issue the command only from a node that already belongs to the IBM Spectrum Scale cluster.
  • While a node may mount file systems from multiple clusters, the node itself may only be added to a single cluster using the mmcrcluster or mmaddnode command.
  • The nodes 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.
  • After the nodes are added to the cluster, use the mmchlicense command to designate appropriate IBM Spectrum Scale licenses to the new nodes.

Parameters

-N NodeDesc[,NodeDesc...] | NodeFile
Specifies node descriptors, which provide information about nodes to be added to the cluster.
NodeFile
Specifies a file containing a list of node descriptors, one per line, to be added to the cluster.
NodeDesc[,NodeDesc...]
Specifies the list of nodes and node designations to be added to the IBM Spectrum Scale cluster. Node descriptors are defined as: 
NodeName:NodeDesignations:AdminNodeName:LicenseType
where:
NodeName
Specifies the host name or IP address of the node for GPFS daemon-to-daemon communication.
The host name or IP address must refer to the communication adapter over which the GPFS daemons communicate. Aliased interfaces are not allowed. Use the original address or a name that is resolved by the host command to that original address. You can specify a node using any of these forms:
  • Short host name (for example, h135n01)
  • Long, fully-qualified, host name (for example, h135n01.ibm.com)
  • IP address (for example, 7.111.12.102). IPv6 addresses must be enclosed in brackets (for example, [2001:192::192:168:115:124]).

Regardless of which form you use, GPFS will resolve the input to a host name and an IP address and will store these in its configuration files. It is expected that those values will not change while the node belongs to the cluster.

NodeDesignations
An optional, "-" separated list of node roles:
  • manager | client – Indicates whether a node is part of the node pool from which file system managers and token managers can be selected. The default is client.
  • quorum | nonquorum – Indicates whether a node is counted as a quorum node. The default is nonquorum.
    Note: If you are designating a new node as a quorum node, and adminMode central is in effect for the cluster, GPFS must be down on all nodes in the cluster. Alternatively, you may choose to add the new nodes as nonquorum and once GPFS has been successfully started on the new nodes, you can change their designation to quorum using the mmchnode command.
AdminNodeName
Specifies an optional field that consists of a node interface name to be used by the administration commands to communicate between nodes. If AdminNodeName is not specified, the NodeName value is used.
Note: AdminNodeName must be a resolvable network host name. For more information, see GPFS node adapter interface names.
LicenseType
Assigns a license of the specified type to the node. Valid values are server, client, and fpo. For information about these license types, see mmchlicense command.

The full text of the Licensing Agreement is provided with the installation media and can be found at the IBM® Software license agreements website (www.ibm.com/software/sla/sladb.nsf).

--accept
Specifies that you accept the terms of the applicable license agreement. If one or more node descriptors includes a LicenseType term, this parameter causes the command to skip the prompt for you to accept a license.

You must provide a NodeDesc for each node to be added to the IBM Spectrum Scale cluster.

Exit status

0
Successful completion.
nonzero
A failure has occurred.

Security

You must have root authority to run the mmaddnode command.

The node on which the command is issued must be able to execute remote shell commands on any other node in the cluster without the use of a password and without producing any extraneous messages. For more information, see Requirements for administering a GPFS file system.

Examples

  1. To add nodes k164n06 and k164n07 as quorum nodes, designating k164n06 to be available as a manager node, issue this command: 
    mmaddnode -N k164n06:quorum-manager,k164n07:quorum
    To confirm the addition, issue this command: 
    mmlscluster
    The system displays information as in the following example:
    GPFS cluster information
========================
  GPFS cluster name:       cluster1.kgn.ibm.com
  GPFS cluster id:         680681562214606028
  GPFS UID domain:         cluster1.kgn.ibm.com
  Remote shell command:      /usr/bin/ssh
  Remote file copy command:  /usr/bin/scp
  Repository type:           server-based

GPFS cluster configuration servers:
-----------------------------------
  Primary server:    k164n07.kgn.ibm.com
  Secondary server:  k164n04.kgn.ibm.com

Node Daemon node name      IP address    Admin node name  Designation
---------------------------------------------------------------------
 1   k164n04.kgn.ibm.com   198.117.68.68  k164n04.kgn.ibm.com  quorum
 2   k164n07.kgn.ibm.com   198.117.68.71  k164n07.kgn.ibm.com  quorum
 3   k164n06.kgn.ibm.com   198.117.68.70  k164n06.kgn.ibm.com  quorum-manager

  2. In the following example the mmaddnode command adds a node without specifying a license:
    (11:37:06) c34f2n03:~ # mmaddnode -N c6f2bc4n8:quorum
Tue Mar 12 11:37:13 EDT 2019: mmaddnode: Processing node c6f2bc4n8.gpfs.net
mmaddnode: Command successfully completed
mmaddnode: Warning: Not all nodes have proper GPFS license designations.
    Use the mmchlicense command to designate licenses as needed.
mmaddnode: Propagating the cluster configuration data to all
  affected nodes.  This is an asynchronous process.
    The command displays a warning message that some nodes do not have licenses.

  3. In the following example the mmaddnode command specifies a license to be designated to the node:
     # mmaddnode -N c6f2bc4n8:quorum::server
mmaddnode: Node c6f2bc4n8.gpfs.net will be designated as possessing server license.
Please confirm that you accept the terms of the IBM Spectrum Scale server Licensing Agreement.
The full text can be found at www.ibm.com/software/sla
Enter "yes" or "no": yes
Tue Mar 12 11:41:51 EDT 2019: mmaddnode: Processing node c6f2bc4n8.gpfs.net
mmaddnode: Command successfully completed
mmaddnode: Propagating the cluster configuration data to all
  affected nodes.  This is an asynchronous process.
    The command prompts the user to accept the terms of the licensing agreement.

  4. In the following example the mmaddnode command specifies a license and also specifies the --accept parameter:
     # mmaddnode -N c6f2bc4n8:quorum::server --accept
mmaddnode: Node c6f2bc4n8.gpfs.net will be designated as possessing server license.
Tue Mar 12 11:51:15 EDT 2019: mmaddnode: Processing node c6f2bc4n8.gpfs.net
mmaddnode: Command successfully completed
mmtrace: move /tmp/mmfs/lxtrace.trc.c34f2n03.cpu0 /tmp/mmfs/trcfile.2019-03-12_11.51.27.28959.c34f2n03.cpu0
mmtrace: formatting /tmp/mmfs/trcfile.2019-03-12_11.51.27.28959.c34f2n03 to /tmp/mmfs/trcrpt.2019-03-12_11.51.27.28959.c34f2n03.gz
mmaddnode: Propagating the cluster configuration data to all
  affected nodes.  This is an asynchronous process.
    Because the --accept parameter is specified, the command does not need to prompt for acceptance of the license agreement.

See also

Location

/usr/lpp/mmfs/bin