After the management server is installed, (via the installms command), you need to define all of the nodes in the cluster. To define the nodes of the cluster, you use the definenode command on the management server node. Before running the definenode command, you should have:
Note that the definenode command simply creates definitions for the nodes in the cluster. It does not actually install the nodes. Node installation is done later with the updatenode command.
To define nodes with a nodedef file, issue the definenode command, on the management server, and specify the full path name of the nodedef file. For example:
definenode -f /tmp/nodedef
To define a node from the command line, without hardware control and with all the default attributes, issue the definenode command, on the management server, and specify the host name:
definenode -n hostname
For example, to define a node with a host name of clsn02.ppd.pok.ibm.com, you would type:
definenode -n clsn02.ppd.pok.ibm.com
To define a node's hardware attributes from the command line, issue the definenode command, followed by the attributes you want to assign. The sample of a completed Hardware Node Attributes Template, from the CSM for Linux: Hardware Planning and Control Guide, was used to create the example below.
Setting a node's HWControlNodeID attribute to the short host name of the node can simplify the node definition process. The following definenode command example defines the node short host names as the HWControlNodeID attribute values. If the HWControlNodeID attribute values were not set to the node short host names, then the nodedef file would be used to specify each attribute value. If a node's HWControlNodeID is the short host name, then the following command can be run once to define all nodes attached to the hardware control point:
definenode -n clsn01.pok.ibm.com -c 20 -H mgtn03.pok.ibm.com:10,- mgtn04.pok.ibm.com:10 \ -C mgtn02.pok.ibm.com:1:0:16,mgtn05.pok.ibm.com:2:0:16 PowerMethod=netfinity ConsoleMethod=esp
All HWControlNodeID node attribute values attached to a hardware control point must be unique. For Netfinity xSeries 330 and 342 nodes, the HWControlNodeID value must match the Netfinity text ID set in the hardware. If the HWControlNodeID values are changed to the short host names of the nodes, then the systemid command must be subsequently run to correctly set the new user ID and password information in the CSM database.
See the man page or CSM for Linux: Administration Guide for details on definenode command line syntax and more examples of using the command.