IBM RS/6000 SP Handbook page 453

At this step the installation of the CWS is complete, we can go ahead and
enter our configuration details for the frame(s) and nodes into the SDR.
– Enter Site Environment Details
– Enter Frame Information and Reinitialize the SDR.
– Verify System Monitor Installation by running smitty SP_verify
– Enter the required Node Information.
There are many additional steps that can be followed to further customize the
nodes, most significantly setting up the switch (if your SP system has one).
However, at this point of the installation, we now have all the node and frame
information in the SDR.
Boot/Install server requirements
By default, a single frame SP system will configure the CWS as the only
Boot/Install server (BIS) - the NIM Master.
In a multiple frame SP system, by default, the CWS will act as the BIS for the first
frame and then the first node in each additional frame will be configured to act as
a BIS for the rest of the nodes in its own frame.
In a large CES configuration a BIS can always be selected to improve the
installation performance.
Netbooting
To netboot an RS/6000, we would turn the keyswitch and go into SMS or use a
ROM IPL disk, depending on the model. On the SP, this is all handled for us,
thanks to our connection with the frame supervisor card and serial connection. In
order to netboot a node, we simply need to click on netboot on the perspectives
panel or, from the command line, use the nodecond command. It is possible to
manually netboot the node if you wish to use the spmon command to change the
power or keyswitch setting and a writable s1term in order to enter the boot
address or, in the case of a PCI node, enter SMS mode.
Using the nodecond command, or perspectives to netboot a node, also provides a
log file to check for errors, although you can also watch the progress of a netboot
by using a read-only s1term. Do not use the open a console option from the
perspectives panel if you want to simply watch the netboot progress of a node
because this will open a writable console and stop automatic node conditioning.
Node customization
The customization of the SP nodes is performed by a Korn shell script called
pssp_script. This is used by NIM after a migration or installation of a node.
Appendix E. SP/CES Tools
429