IBM Books

Installation and Migration Guide

Detailed overview of the network installation of a node

The information in this section is optional. Read this section if you want to understand the details of the network installation described in Install PSSP on the nodes (externals).

NIM-specific terminology and concepts

Network installation

When a node boots over the network, it issues a bootp request on that network specifying its network device hardware address. (For the RS/6000 SP, this is the node's |SP Ethernet administrative LAN adapter). The boot/install server has a list of nodes it boots and their associated hardware Ethernet addresses.

The bootp daemon on the boot/install server gets the request and looks in its table (/etc/bootptab) for this node's hardware Ethernet address. If it finds the address in its table, it responds by sending the node's IP address.

The node's IPL Read-Only Storage (ROS) requests a boot image transferred to the node using tftp. The boot image is run, the rootvg gets created, and NIM performs the installation of the mksysb image. After the mksysb installation is complete, NIM invokes the pssp_script script resource which transfers the install information files from the boot/install server to the node and performs the customization. These install files contain information necessary to successfully complete the netinstall.

Customization for network install

pssp_script transfers the following netinstall information files from the boot/install server to the node and then performs the customization:

Fields in the install_info file contain the following information:

Fields in the config_info file contain the following information:

After a node is installed, pssp_script gets a copy of the config_info file from its master. The information in the config_info file is used to define the adapters, set the hostname, define the default route, and to customize the adapters with information such as host name and default route. This file is transferred from the server to the node during customization. The file is read at this time and the node is configured.

The PSSP file sets ssp.basic, ssp.perlpkg, ssp.sysctl, ssp.ha, ssp.clients, and ssp.sysman are installed if they are not already installed. The ssp.css file set is always installed on systems with a switch. The option is installed if the node's boot/install server has it installed.

As part of completing the network install, NIM modifies the boot/install server's /etc/bootptab file so that the node does not perform a netinstall again on the next boot. PSSP changes the SDR node object bootp_response attribute to disk.

Boot processing

After customization, a bootable image is written to the node's disk. The node is then shut down and rebooted. When it is rebooted, PSSP checks the SDR to determine if any of the PSSP Site Environment options were chosen. If an option is selected, the node configuration for that system management option is performed now. When the node reboots, if it is a boot/install server, setup_server is run.

Configuring boot/install servers as NIM masters

When you run /usr/lpp/ssp/bin/setup_server to configure a boot/install server, it does the following:

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