IBM RS/6000 SP, Руководство по определению проблем

Страница: 89 / 316

This soft copy for use by IBM employees only.
The
/etc/bootptab
was checked, and now it had an entry for sp2n08 as
follows:
sp2n08:bf=/tftpboot/sp2n08:ip=9.12.20.8:
ht=ethernet:ha=10005AFA1B12:sa=9.12.20.1:
sm=255.255.255.0:
7. Net Boot was tried again and now it worked.
2.11 Node Customization Problems
When a node is installed, its bootp_response option in the SDR is set to
install.
With this option, the node is network-booted and the installation process begins
with the AIX BOS installation. After the first part of the installation is finished,
the customization process takes place. This customization process consists of
running the pssp_script on the node just installed. This script is the heart of the
customization process.
The output of this script is sent to /var/adm/SPlogs/sysman/<node>.config.PID.
The variables used by this script are set in <node reliable
hostname>.install_info file in /tftpboot on the boot install server at the node
being customized or installed. Also, some variables are taken from /sbin/rc.boot
file on the node.
The pssp_script installs any additional lpp and device drivers needed on the
node, and finally, executes the /tftpboot/script.cust and /tftpboot/tuning.cust
scripts after transferring them from the boot install server.
The same script sets back to disk the bootp_response option in the SDR and
resets the NIM machine object for that node.
2.11.1 Why a Node Is Not Being Customized
The reasons why a node is not customized are many. However, the reasons will
vary, depending on whether the node was being installed, or customized.
•
If This is an Installation
Since during the post-install process some lpps are installed along with
device drivers needed in the node, the post-install process can fail due to
some lpps or device drivers being missing in the lppsource directory. Some
times those lpps are deleted to save space, and the problem arises
whenever you recreate the SPOT or are trying to install a new node.
The SPOT must be created with the original lpp sources. For example, if a
system was originally installed at AIX 4.1.2 level, and then was later updated
to AIX 4.1.4, the AIX 4.1.2 install images must be used as the source to
create the /usr SPOT. The resultant /usr SPOT will be at the proper AIX 4.1.4
level when the SPOT creation is complete.
Alternatively, it is also possible to first create the /usr SPOT at the original
level, and then apply all updates to bring the /usr SPOT to the latest level.
Another problem that can be present during installation or even just
customization is the use of short names instead of long names. After
applying PTF 12, pssp_script had a problem handling short names. Nodes
were stopping with LED u73.
• If This is a Customization
Chapter 2. The Installation Process
69