Administration Guide
Name
definenode - Defines the nodes in a cluster.
Synopsis
definenode [-h]
definenode [-v |
-V][-s] [-U]
-f nodedef _file
definenode [-v |
-V][-s] [-U]
[-n starting_node] [-c
count] [-H HWControlPoints ]
[-C ConsoleServers ] [Attr=value
[Attr=value...] ]
Description
The definenode command runs on the management server and is
used to define all of the nodes of a cluster. Before running this
command, you must run the installms command to install the cluster
management server. The definenode command creates node
definitions in the CSM database.
This command provides several different techniques that may be used to
create cluster node definitions. A user could:
- Create one definition at a time.
- Use the node definition file as input to the command to define
multiple nodes.
- Use the starting_node and count values to automatically
generate a set of node definitions with consecutive IP addresses.
- Use either of the previous two techniques to create a node definition file
(use the -s option and redirect to a file) that could be easily
modified and then used as input to the definenode command.
The basic information that is needed when defining a node is:
- The host name or IP address of the node.
To enable hardware control, the following information must be provided:
- The HWControlPoint attribute, which is set with the
-H flag.
- The PowerMethod attribute.
- The HWControlNodeID attribute.
- The ConsoleServer attribute, which is set with the
-C flag.
- The hostname of the ESP console server.
- The ConsoleMethod attribute.
- The ConsoleServerNumber attribute.
- The ConsolePortNumber.
- The InstallCSMVersion and InstallOSName
attributes. The values for these attributes both default to whatever is
installed on the management server. For information about the
attributes that do not have defaults, see the nodeattributes man page or nodeattributes File.
To define a node whose Hardware Control Point is an ASM adapter on a
netfinity node, whose service processor is the short hostname of the node, and
which uses an ESP console server:
definenode -n <node_name> -H <asm_hostname> -C <esp_hostname>:<console_server_number>:
<esp_port> PowerMethod=netfinity ConsoleMethod=esp InstallCSMVersion=1.2.0
InstallDistributionVesion=7.2
You can define multiple nodes by using the starting_node and count
method. The starting_node and count technique of
defining nodes will define the starting_node, and the increment the
node's IP address to determine the name of the next node. The IP
addresses are incremented up to the count number of nodes.
The nodes are assigned to hardware control points in order, up to the
number of service processors for each hardware control point. In this
example, there are 10 service processors connected to each hardware control
point. So, the first hardware control point (asm1) is
assigned to the first 10 nodes (node1 - node10), the
second hardware control point (asm2) is assigned to the next 10
nodes (node11 - node20), and so on. The nodes are
assigned to the console servers in order, up to the number of ports for each
console server. For this method to work correctly the nodes to be
defined must be set up with consecutive IP addresses. To define thirty
nodes, starting with node1, you could issue the following:
definenode -n node1 -c 30 -H asm1:10,asm2:10,asm3:10 -C esp1:1:0:12,
esp2:2:0:12,esp3:3:0:12 -s PowerMethod=netfinity ConsoleMethod=esp
InstallCSMVersion=1.2.0 InstallOSName=Linux > nodedef
In this case the list of node definitions that would be created is
displayed to standard out and is redirected to a node definition file.
The definitions are not actually created in the CSM database. This is a
good way to check the correctness of the definitions or to make modifications
before actually creating the definition. Once the file is checked and
edited if necessary it can be used as input to the definenode
command.
When the node definition file is ready, rerun the definenode
command as follows:
definenode -f nodedef
See the nodedef File man page for a description of the node definition file
format.
Options
- -C ConsoleServers
- Specifies the list of console server definitions. Multiple console
server definitions are separated by commas. The ConsoleMethod attribute
must be specified when using this flag. This information will be used
to set the ConsoleServerName, ConsoleServerNumber, and
ConsolePortNum attributes of the node definition. The entries
must have the following format:
-C console_server_name[::console_server_num[:starting_port_num
[:num_console_ports]]][, ...]
where:
- console_server_name
- Represents the host name or IP address of the console server.
- console_server_num
- Represents the console server number. The default is 1.
- starting_portnum
- Represents the starting console port number. The default is
0.
- num_console_ports
- The total number of ports on the console server.
- -c count
- Specifies how many nodes to define. The IP addresses are
determined by incrementing the starting node IP address by one. To use
this option it is necessary to set up the nodes to define with consecutive IP
addresses and to enter that in formation into the nameserver.
- -f nodedef_file
- Represents the node definition file. A sample node definition file
is supplied in /opt/csm/install/nodedef.sample. See the
nodedef File for more information.
- -H HWControlPoints
- Specifies the list of hardware control points. Multiple hardware
control point definitions are separated by commas. The
PowerMethod attribute must be specified when using this flag.
This information will be used to set the HWControlPoint, and
HWControlNodeId attributes of the node definition. Each
definition must be specified using the following format:
-H HWCtrlPt[:num_nodes][,... ]
where:
- HWCtrlPt
- Represents a hardware control point by host name or IP address.
- num_nodes
- The total number of nodes controlled by this hardware control
point.
- -h
- Writes the command's usage statement to standard output.
- -U
- Runs updatenode to install the nodes once they are
defined.
- -n starting_node
- Specifies the IP address or host name for the first node to be
added. A list of nodes is generated by incrementing IP addresses up to
the value specified by the -c count value.
- -s
- Send the list of node definitions that the definenode command
would be creating to standard output. This output can be redirected to
a file that can be used as a node definition file.
- -v | -V
- Writes the command's verbose messages to standard output.
Examples
- Create CSM node definitions for the 18 nodes that are controlled by
the ASM adapters asm06 and asm07. Set the
InstallDistributionName attribute of all the node definitions to
RedHat and the InstallCSMVersion to
1.2.0.
definenode -n clsn01 -c 18 -H asm06:10,asm07:10 -C esp1:0:0:16,esp2:1:0:16 PowerMethod=netfinity
ConsoleMethod=esp InstallDistributionName=RedHat InstallCSMVersion=1.2.0 InstallOSName=Linux
- Add two nodes to the cluster that was defined in the previous
example. The nodes use hardware control point asm07 and
console server esp2, ports 2 and 3. The
InstallDistributionName, InstallCSMVersion, and
InstallOSName values are taken from the management server.
definenode -n clsn19 -c 2 -H asm07:10 -C esp2:1:2:16 PowerMethod=netfinity ConsoleMethod=esp
- Create a node definition file by redirecting the output of the definenode
command to a file:
definenode -s -n clsn01 -n 10 -H asm06:10 -C esp1:0:0:16 PowerMethod=netfinity ConsoleMethod=esp
InstallCSMVersion=1.2.0 > /tmp/mynodes
- Create node definitions for each node described in a node definition
file:
definenode -f /tmp/mynodes
- Create four cluster node definitions:
definenode -n cls18 -c 4 -H asm04:10 -C esp02 PowerMethod=netfinity InstallDistributionName=RedHat
InstallCSMVersion=1.2.0 InstallOSName=Linux
Exit Status
- 0
- The command has run successfully.
- 1
- An error has occurred.
Files
- /opt/csm/bin/definenode
- Location of the definenode command.
- /opt/csm/install/nodedef.sample
- Location of sample node definition file.
See Also
- The chnode, installms, lsnode,
nodeattributes, nodedefrmnode, and
updatenode man pages.
- IBM CSM for Linux: Software Planning and Installation
Guide, IBM CSM for Linux: Hardware Planning and Control Guide
Author
Sean Safron - cluster@us.ibm.com
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]