IBM Books

Diagnosis Guide

Error symptoms, responses, and recoveries

Use the following table to diagnose problems with the NIM component. Locate the symptom and perform the action described in the following table.

If you have a symptom that is not in the table, or the recovery action does not correct the problem, see Information to collect before contacting the IBM Support Center and contact the IBM Support Center.

Table 8. NIM symptoms

Symptom Recovery
SPOT creation failure message from setup_server. See Action 1 - Check SPOT creation.
lppsource creation failure message from setup_server. See Action 2 - Check lppsource creation.
Node LED/LCD stops at 611. See Action 3 - Verify exports.

See Action 4 - Update SPOT.

Node LED/LCD stops at 623. See Action 4 - Update SPOT.
setup_server, allnimres, create_krb_files, delnimclient, delnimmastr, spgetdesc or unallnimres fail with an authorization problem. In Diagnosing boot problems, see Action 5 - Check for multiple Boot/Install servers in RRA mode, secure shell mode, or with AIX Authorization for Remote Commands set to none.

Actions

Action 1 - Check SPOT creation

The problem is that NIM failed to create a SPOT. Refer to the NIM log files listed in the error message. These files contain a trace of the SPOT creation and will contain any errors that occurred. This error is usually caused by one or more file sets that are required to create a SPOT being missing from the lppsource.

Verify that all file sets listed in PSSP: Installation and Migration Guide are present in the lppsource, and run setup_server again. Once the problem is corrected, setup_server should proceed normally.

Action 2 - Check lppsource creation

The problem is that NIM failed to create an lppsource. This error is usually caused by one or more missing file sets in the lppsource directory. Refer to PSSP: Installation and Migration Guide and ensure that all file sets listed are present. After correcting the problem, run setup_server. Once the problem is corrected, setup_server should proceed normally.

Action 3 - Verify exports

This problem is caused by an NFS mount failure. This problem may occur if there is an export or NFS problem on the boot/install server or the control workstation.

  1. Verify that the client's resources are exported on the boot/install server.

    Issue exportfs and look for lines for the spot, pssplpp, and bosinst_data directories. If any are not present, issue setup_server and look for errors.

    If there are any errors, refer to the entries for the message numbers given in PSSP: Messages Reference and follow the instructions there. If the export still does not exist, see Information to collect before contacting the IBM Support Center and contact the IBM Support Center.

  2. Verify that the lppsource is exported from the control workstation.

    If it is not present, issue setup_server and look for errors.

    If there are any errors, refer to the entries for the message numbers given in PSSP: Messages Reference and follow the instructions there. If the export still does not exist, see Information to collect before contacting the IBM Support Center and contact the IBM Support Center.

  3. If the exports appear in the exportfs output, you may be experiencing an NFS problem. Follow the AIX procedures for diagnosing NFS problems.

Once the problem is corrected, reinstall the node. It should complete the installation.

Action 4 - Update SPOT

This is a Bos install fatal error. This problem is usually caused by a SPOT, mksysb, and lppsource being out of sync. Use the command: 

nim -o cust

to update the SPOT from the lppsource and reinstall the node.

Once the problem is corrected, the node should complete the installation.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]