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

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

This soft copy for use by IBM employees only.
•
Determine the NIM master host name.
• Login to NIM master.
•
List the objects in the NIM database.
•
While still on the NIM master, list the NIM client definition for the
node having a problem.
•
Compare the values of the
bootp_response and Cstate attributes for
the client node.
•
If the comparison is ok, then the NIM configuration is correct, and
all that needs to be done is to reconfigure boot/install/usr server
information for the node in question. If the comparison does not
match, then you will have to reconfigure NIM.
5. If the node is listed in this file, continue to Step 2 below:
Step 2: Check Console Messages
1. At the Control Workstation, open a write tty to the node with the install
problem by issuing:
#s1term -w <frame_number> <node_number>
2. Wait several minutes to see if any error messages are displayed on the
tty that you opened. An error message might tell you what the problem
is. Also look for NIM messages on the tty that might suggest that the
installation is proceeding. An example of a NIM progress message is:
/ step_number, of total_steps complete
Step 3: Check Image Availability
Check to see if the image is available and the permissions are appropriate.
Issue:
# /usr/lpp/ssp/bin/splstdata -b
The next_install_image field lists the name of the image to be installed. If
the field for this node is set to
default
, the default image (specified by the
install_image attribute of the SP object) will be installed. The images are
found in the /spdata/sys1/install/images directory.
Step 4: Check NIM Configuration for the Node
How to check NIM configuration for a node has already been explained.
Example of resolving Node Install Problem
Here is an example of a problem when installation of node 8, sp2n08,
failed. Previously the installation process was interrupted for this node.
Later Net Boot stopped on LED 231, which means
attempting a normal
mode IPL from Ethernet specified in IPL ROM. After several retries, the
LED code 239 appears, meaning that the boot/install server is not
responding. Then an install was tried through
node conditioning.
Ping
between boot/install server
sp2n01 and client sp2n08 succeeded, but the
install process got stuck on LED 260, which means displaying information
on the display console.
1.
splstdata -b -l 8
pointed to node 1 as the boot/install server for client
node 8.
2.
splstdata -b -l 1
provided boot/install server
′
s host name sp2n01 for
boot/install node 1.
Chapter 2. The Installation Process
67