System Monitor Problems - IBM RS/6000 SP Problem Determination Manual

This soft copy for use by IBM employees only.
LED 260-262
LED 231-239
LED 610-612
If you do not find any of the problems mentioned above, a good solution would
be reset the NIM client and start all over again.
The final step of the installation process is customization. This is done by the
pssp_script script. Many problems can be found if you look at the console log
file for the particular node.
7.2 Isolating System Monitor Problems
The following section discusses how to isolate system monitor problems.
Figure 78. System Monitor Problems
These numbers indicate that the node is displaying the boot menu
but there must be something wrong with the serial link, because
nodecond cannot get messages from there.
This is a booting problem. The node is intending to boot from the
network, but no one is responding. It could be that the inetd is not
responding, or the bootp or tftp daemons are not responding.
Also, it can be a NIM problem, or an inconsistency between NIM
and the SDR.
This means that the node was unable to mount a remote resource
using NFS. It is difficult to determine which resource mount failed.
•
On the NIM master, verify that NFS is functioning correctly and
that the appropriate resources have been exported correctly.
•
If you have a gateway between the NIM client and NIM server,
verify that the route defined in the NIM configuration is correct.
Chapter 7. Isolating Problems on the SP System
197