Software problems
Use this information to recognize software problem symptoms and to take corrective actions.
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
v See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine
which components are CRUs and which components are FRUs.
v If an action step is preceded by Trained service technician only, that step must be performed only by a trained
service technician.
Symptom Action
You suspect a software
problem.
1. To determine whether the problem is caused by the software, complete the
following items:
v The compute node has the minimum memory that is needed to use the
software. For memory requirements, see the information that comes with the
software.
Note: If you have just installed an adapter or memory, the compute node
might have a memory-address conflict.
v The software is designed to operate on the compute node.
v Other software works on the compute node.
v The software works on another compute node.
2. If you received any error messages when using the software, see the
information that comes with the software for a description of the messages and
suggested solutions to the problem.
3. Contact your place of purchase of the software.
4. To check the operating system logs for information about the source of the
error, first check the ServerProven plan and then complete the following items:
a. For AIX: To view a summary of the error log, use the errpt command. To
view a formatted report of the data for the errors in the log, use the
errpt-a command.
b. For Linux: The /var/log/messages text file should be retrieved and filtered
or viewed as necessary. There are no standardized analysis tools, but
scripts can be written to simplify the view to what you need.
c. For IBM i: Existing problem log entries are available through the WRKPRB
command. To create a new log entry, use the ANZPRB command.
Light path diagnostics
Light path diagnostics is a system of LEDs on the control panel and on the system board of the compute
node. When an error occurs, LEDs are lit throughout the compute node. If the control panel indicates an
error, use the descriptions of the LEDs to diagnose the problem and to take corrective action.
Chapter 8. Troubleshooting 485
To Next Page
Loading...
Need help?
General