A NIM debug SPOT (Shared Product Object Tree) contains trace output from NIM invocation on the node. To diagnose a hang during installation (LED 611), it may be necessary to create and use a NIM debug SPOT. This section describes how to do this.
/usr/lpp/ssp/bin/spmon -G -q -l frame#/node#/codeVersion/valueIf your card is not at microcode version 1294 or later versions, debug installation may loop issuing this message: 032-001 You entered a command command_name that is not valid.
splstdata -b -n node_number
spbootins -r disk 1 15 1
This will issue the necessary NIM commands to prepare for reallocation of the debug SPOT for frame 1 node 15.
nim -Fo check -a debug=yes spot_lppsource_name
lsnim -l spot_lppsource_name
Choose a line as follows:
The line chosen contains an address, such as 0x0013afa0. Omit the 0x part and record the remainder of the address.
For example, for frame 1 node 15 issue the command:
spbootins -r install 1 15 1
nodecond 1 15 &
s1term 1 15
This may take a few minutes to complete. Do not enter anything until it finishes with:
Trap instruction interrupt
and a 0> prompt is displayed. Type <Ctrl-c> to stop your s1term.
script filenamewhere filename is a name you choose for the file.
st hex_number 2(where hex_number is the address recorded in Step 5, omitting the 0x).
The netboot will now be displayed as live. Network installation progress and SP-specific LED/LCD values give the meanings of the LED/LCD codes and help determine approximately where in the boot process your node is.
As the node boots, it may hang with LED/LCD c46. This does not indicate a problem, but the debug netboot needs to be restarted by issuing <Ctrl-q>. If there is a hang at any other LED/LCD value, stop logging by going to Step 13.
kill pidTo get the pid, issue:
ps -ef | grep scriptIf there are two scripts, killing the child process will stop both of them, or the kill command may be used on both processes.
Now view the log file to determine what went wrong with the installation. If you contact the IBM Support Center, make sure that you have the log file available.
nim -Fo check spot_lppsource_namewhere lppsource_name is the same name used in Step 3.
NIM SPOT logs contain trace output from SPOT creation or update. The logs are located on the boot/install server. The trace is automatically activated when a SPOT is updated or created. These logs are located in: /tmp/spot.out.pid and /tmp/spot.updated.out.pid. Error messages give the exact file name.
NIM commands and their responses are recorded. Look for errors associated with command invocation, errors associated with file set installation, and errors associated with other NIM-related activities.