IBM Books

Administration Guide

installnode Command

Name

installnode - Installs the operating system and CSM on all the nodes in a cluster.

Synopsis

installnode [-h] [-v | -V] [-P | -a | [ -N node_groups] [node_list]]

Description

The installnode command runs on the management server and performs a full installation on each node that is specified. The installnode command installs the operating system along with CSM on the nodes.

If given no arguments, the installnode command will display its usage statement. This prevents an unintended install of all the nodes. To install all the nodes whose Mode attribute is PreManaged, use the -P flag. To install all the nodes, use the -a flag. To install a specific set of nodes or node groups, specify the -N flag or give a list of nodes. Both a list of node groups and a list of nodes may be provided in the same invocation of installnode.

The installnode command only installs Linux nodes whose InstallMethod attribute is set to kickstart. All other nodes are skipped and a warning is displayed. The InstallMethod attribute is set to kickstart by csmsetupks, or can be changed with chnode.

The following logs provide a history of the installation process. The installnode.log is located on the management server in /var/log/csm. This log records the verbose output of the installnode command. A log is also created on each node in /var/log/csm/install.log. This log records the details of what happened to the node as it was installed. The monitorinstall command also displays install status.

As each node is installed, it is added to the cluster and becomes a managed node.

Before installnode can be run, the following prerequisites are needed:

  1. NFS must be available on the management server for mounting /csminstall and /tftpboot to the nodes.
  2. The installms, definenode and csmsetupks commands must have already been run.
  3. Before running a full installation, set each node's boot order to the following:

During a Kickstart install, installnode does the following:

  1. Sets up the /tftpboot/pxelinux.cfg/<node-ip-addr-in-hex> file for each node so that when the node reboots, it does a Kickstart install.
  2. Reboots the node.
  3. As the node reboots, broadcasts its MAC address.
  4. The dhcp server on the management server accepts the node's dhcp request and pxelinux is used to initiate a Kickstart install.
  5. Kickstart installs the Operating System on each node.
  6. After the Kickstart install of the OS is complete, the Kickstart post-install script (found in /csminstall/csm<InstallCSMVersion>kickstart.<InstallDistributionName> <InstallDistributionVersion>/<node-ipaddr>-kickstart) is run on the node. After some additional configuration, the Kickstart post-install script adds the csmfirstboot script (/csminstall/csm/<InstallCSMVersion>/csmfirstboot) to /etc/inittab. It then modifies the pxelinux configuration file on the management server (/tftboot/pxelinux.cfg/<node-ip-addr-in-hex>) so the next reboot of the node reboots from the local hard drive.
  7. The node reboots to the local hard drive.
  8. As the reboot completes, the csmfirstboot script (which was listed in /etc/inittab) is run on the node.
  9. The csmfirstboot script runs makenode (which installs CSM and its dependencies and sets its management server), and then removes itself from /etc/inittab.
  10. When the Mode attribute for this node is changed to Managed, the node is installed and ready for use in the cluster.

Options

-a
Install all nodes whose InstallMethod attribute is kickstart. This flag cannot be used with the -P or -N flags, or node_list.

-v | -V
Writes command's verbose messages to standard output.

-h
Display this usage information.

-P
Installs all nodes whose Mode attribute is PreManaged and whose InstallMethod attribute is kickstart. This flag cannot be used with the -a or -N flags or node_list.

-N [node_groups]
Provide a comma-separated list of node groups to install. This cannot be used with the -a or -P flags.

node_list
Space-separated list containing a list of nodes. This cannot be used with the -a or -P flags.

Environment

CSM_FANOUT
Sets the maximum number of concurrent reboots. If this is not set, 16 nodes are rebooted concurrently. If set to 0, all nodes are rebooted concurrently.

CSM_FANOUT_DELAY
Sets the delay in seconds between rebooting groups of nodes. If this is not set, the delay is 10 seconds.

Examples

  1. Install the operating system and CSM on all the ManagedNodes defined in the cluster whose InstallMethod attribute is kickstart:
    installnode -a
    
  2. Install all the nodes in the cluster whose Mode is PreManaged:
    installnode -P
    
  3. Install a list of nodes:
    installnode clsnode5 clsnode6 clsnode14 clsnode16
    
  4. Install all the nodes in nodegroup mynodes:
    installnode -N mynodes
    

Files

/csminstall/csm/status/<node-hostname>
Location of the installation status file. Used by monitorinstall.

/opt/csm/bin/installnode
Location of the installnode command.

/var/log/csm/installnode.log
Location of the log file on the management server for the installnode command. Up to five copies of this log are maintained. Old logs receive a numeric suffix up to 4. The oldest file is installnode.log.4.

/var/log/csm/install.log
Location of the log file on each node containing installation information. Up to five copies of this log are maintained. Old logs receive a numeric suffix up to 4. The oldest file is install.log.4

See Also

Author

Sean Safron - cluster@us.ibm.com


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]