Scripts Involved In Network Boot - IBM RS/6000 SP Problem Determination Manual

3. diag
4. customize
5. disk

2.10.1 Scripts Involved in Network Boot

The main script involved in the network boot process is /sbin/rc.boot. This script
is called first in boot phase one (/sbin/rc.boot 1). Basically the following steps
are performed at that time:
1. Read the IPL control block (
2. Configure the given network device by use of the received IP parameters. If
3. Now the / t f p t b o o t / < h o s t n a m e > . i n f o file is tftp' d from the installation server
4. A more likely step to fail is the mount which is performed now. The SPOT is
5. Depending on the reason for the network boot, the next step may vary. If
62
SP PD Guide
Similar to the install mode the files /tftpboot/<hostname>.info,
/tftpboot/<hostname>.install_info, and /tftpboot/<hostname>.config_info
are created and /etc/bootptab is updated to enable this machine to act as
boot server. The bootp_response maintenance requires a network boot.
The selection of the diag bootp_response allocates the following resources to
the NIM machine object: psspspot, prompt, and boot. The same file as in
the two other boot response modes are being created. The bootp_response
diag requires a network boot.
The bootp_response customize deallocates all resources of a given NIM
client, removes the NIM client, and recreates it. No resources are allocated.
The files /tftpboot/<hostname>.install_info and
/tftpboot/<hostname>.config_info are created beside
/ t f t p b o o t / < h o s t n a m e > - n e w - s r v t a b . No network boot is required.
This bootp_response mode finally changes the bootp_response field in the
SDR to disk and removes the resource allocations of a NIM client. The file
/tftpboot/<hostname>.info is removed, as well as the entry in the
/etc/bootptab file for that client. No network boot is required.
address, the boot server address, gateway information, the network adapter
to use, the bootfile name, and others.
this fails, you see LED code 607, a failure that is quite unlikely.
to the local file /SPOT/niminfo. When this tftp transfer fails, the client node
stops with a LED code of 608. This file contains a set of environment
variables which define the current installation environment. This file is
sourced (/SPOT/niminfo) and the environment variables are set in the
current shell. If this fails, you see the LED error code 609.
mounted in the RS/6000 SP environment by the command
bootserver:/usr /SPOT/usr
configuration on the installation server. The typical LED error code is 611.
Sometimes, there is a routing problem between the client node and the
Control Workstation. Even when the client node is installing from a
boot/install server other than the Control Workstation, a route is required
from the Control Workstation to the client node. If this is the case, 610 is the
LED code where the node will stop. If you see the 612, the mount was
successful. We discuss this situation later in this chapter.
you perform an installation, the script /usr/lib/boot/network/rc.bos_inst is
copied from the SPOT into the local /etc: directory and also sourced. If you
This soft copy for use by IBM employees only.
bootinfo -b
) to get information such as client
. This step sometimes fails due to incorrect NFS
mount