Table of Contents
Advertisement
Start here
You can solve many problems without outside assistance by following the troubleshooting procedures in this
documentation and on the IBM Web site.
This Problem Determination and Service Guide describes the diagnostic tests that you can perform,
troubleshooting procedures, and explanations of error messages and error codes. The documentation that
comes with your operating system and software also contains troubleshooting information.
Diagnosing a problem
Before you contact IBM or an approved warranty service provider, follow these procedures in the order in
which they are presented to diagnose a problem with your blade server.
Step 1.
Determine what has changed.
Determine whether any of the following items were added, removed, replaced, or updated before
the problem occurred:
• Unified Extensible Firmware Interface (UEFI) code
• Device drivers
• Firmware
• Hardware components
• Software
If possible, return the blade server to the condition it was in before the problem occurred.
Step 2.
Collect data.
Thorough data collection is necessary for diagnosing hardware and software problems.
Note: Event messages that include links to descriptions and recommended actions can be viewed
in the advanced management module event log (see the Advanced Management Module User's
Guide for additional information). A listing of all general event information is in the BladeCenter
Advanced Management Module Messages Guide.
a.
Document error codes and light path diagnostics LEDs.
• System error codes: See "Event logs" on page 79 for information about a specific error
code.
• Software or operating-system error codes: See the documentation for the software or
operating system for information about a specific error code. See the manufacturer's Web
site for documentation.
• Light path diagnostics LEDs: See "Light path diagnostics" on page 204 for information
about LEDs that are lit.
b.
Collect system data.
Advertisement
Table of Contents
