Name

nodeset - set the boot state for a noderange


Synopsis

nodeset [noderange] [boot|install|state|stat]

nodeset [noderange] [stage2|stage3|shell]

nodeset [noderange] [clone|cloneserver|image]

nodeset [noderange] [flash={image}]

nodeset [-h|--help|-v|--version]


Description

nodeset sets the next cold or warm boot state for a single or range of nodes or groups. This tells xCAT what you want to happen the next time the nodes are booted up. See noderange(3). nodeset accomplishes this by changing the network boot files. Each xCAT node always boots from the network and downloads a boot file with instructions on what action to take next.

nodeset only supports PXELINUX, Etherboot, Etherboot/NBGRUB, and ELILO as network boot loaders. nodeset calls nodeset.pxe, nodeset.eb, node- set.nbgrub, and nodeset.elilo to perform the updates.

Assume that /tftpboot is the root for tftpd (set in site(5)).

nodeset.pxe makes changes to /tftpboot/pxelinux.0/{node hex ip}

nodeset.eb makes changes to /etc/dhcpd.conf

nodeset.nbgrub makes changes to /tftpboot/grub/{node hostname}.grub

nodeset.elilo makes changes to /tftpboot/elilo/{node ip}.conf and /tftpboot/elilo/{node hex ip}.conf

nodeset.elilo support both formats for xCAT patch elilo 2.5 and xCAT patched elilo 3.x.

nodeset only sets the next boot state, but does not reboot.

nodeset is called by rinstall and winstall and is also called by the installation process remotely to set the boot state back to ``boot''.

When nodeset is called to set a node for an installation state, a NODE- TYPE-RESOURCE.BOOTTYPE template must exist in /tftpboot/xcat (or the appropriate directory as defined in site(5)), where NODETYPE is defined per node in nodetype(5), RESOURCE is defined per node or group in noderes(5), and BOOTTYPE is defined per node in nodehm(5).


Options

boot

Instruct node to boot local harddisk 0 on next boot.

install

Instruct node to boot from network. This usually involves TFTP downloading a kernel, initrd, and kernel options, then booting the downloaded images to facilitate automated unattended installation.

state|stat

Display the next boot state.

stage2

Instruct node to boot from network image stage2. This involves TFTP downloading a special prebuilt kernel, initrd, and kernel options used for MAC address collection. For a new node this is the default action and cannot be changed until a node entry exists in dhcpd.conf(5). It is not necessary to explicitly set stage2, unless it is used for testing and development purposes.

stage3

Instruct node to boot from network image stage3. This involves TFTP downloading a special prebuilt kernel, initrd, and kernel options used for the automated programming of IBM service pro- cessors.

shell

Instruct node to boot from a network maintainance shell image. This involves TFTP downloading a special prebuilt kernel, ini- trd, and kernel options used for a limited RAMdisk-based main- tainance shell. Only available for IA64 systems.

clone

Instruct node to boot from network into clone mode. In clone mode the node will poll the management node for nodes in clone- server mode, once a clone lock is established the clone node clones the cloneserver node. Usually called from rclone(1).

cloneserver

Instruct node to boot from network into cloneserver mode. In cloneserver mode the node will wait for a node to attempt a clone lock. Once a clone lock is established the clone node clones the cloneserver node. All other requested will be refused until node cloning is completed.

image Instruct node to boot from network and run Partition Imager to create partition images.
flash=image

Instruct node to boot from network load DOS and flash image. Usually called from rflash(1).

-h|--help

Print help.

-v|--version

Print version.


Files

nodehm table - xCAT node hardware management file. See nodehm(5) for fur- ther details. This is used to determine the network boot type: PXE, Etherboot, ELILO, or NA.

noderes table - xCAT node resources file. See noderes(5) for further details. This is used to determine the node's resource group.

nodetype table - xCAT node installation type file. See nodetype(5) for fur- ther details. This is used to determine the node installation image type.

site table - xCAT main configuration file. See site(5) for further details. This is used to determine the location of the TFTP root directory and the TFTP xCAT subdirectory. /tftpboot and /tftpboot/xcat is the default.

/etc/dhcpd.conf file - xCAT dhcpd configuration file. See dhcpd.conf(5) for further details. This is used by nodeset to determine if a node will only boot stage2 because no statically assigned IP exists for that node. Also used by nodeset.eb to set the boot state for Etherboot enabled nodes.


Examples

nodeset node5 install

node5: install compute62-compute

Install node5 with the compute62 image using resources from the compute resource group.


Author

Egan Ford <egan@us.ibm.com>


See Also

noderange(3), nodels(1), nodestat(1), rinstall(1), rflash(1), makedhcp(8)