To perform the checkout procedure, complete the following steps:
Step 1. If the blade server is running, turn off the blade server.
Step 2. Turn on the blade server. Make sure that the blade server has control of the video (the LED on the
keyboard/video/mouse button is lit). If the blade server does not start, see “Troubleshooting tables”
on page 253.
Step 3. Record any POST error messages that are displayed on the monitor. If an error is displayed, look
up the first error in the “POST error codes” on page 149.
Step 4. Check the control panel blade-error LED; if it is lit, check the light path diagnostics LEDs (see “Light
path diagnostics” on page 202).
Step 5. Check for the following results:
• Successful completion of POST, indicated by beginning the startup of the operating system.
• Successful completion of startup, indicated by a readable display of the operating-system
desktop.
Diagnostic tools overview
Use this overview to locate specific diagnostic tools to diagnose and solve hardware-related problems.
The following tools are available to help you diagnose and solve hardware-related problems:
•
POST codes, error messages, and error logs
The POST error codes indicate the detection of a problem. For more information, see “POST error codes”
on page 149.
•
Troubleshooting tables
These tables list problem symptoms and actions to correct the problems. See “Troubleshooting tables”
on page 253
•
Light path diagnostics
Use light path diagnostics LEDs on the system board to diagnose system errors. If
the system-error LED on the system LED panel on the front or rear of the BladeCenter chassis is lit, one or
more error LEDs on the BladeCenter chassis components also might be lit. These LEDs help identify the
cause of the problem. For more information about the blade server error LEDs, see “Light path diagnostics
LEDs” on page 207.
•
Dynamic System Analysis (DSA) Portable Edition diagnostic program
DSA tests the major
components of the BladeCenter unit, including the management modules, I/O modules, removable-media
drives, and the blade servers, while the operating system is running. For documentation and download
information for DSA, see http://www.ibm.com/systems/management/. For more information about
diagnostic programs and error messages, see “IBM Dynamic System Analysis ” on page 211.
Note:
If you are unable to find the system error logs in the blade server firmware code, view the advanced
management module event log.
•
Dynamic System Analysis (DSA) Preboot diagnostic program
The DSA Preboot diagnostic programs
are stored in read-only memory. DSA Preboot collects and analyzes system information, as well as offers
a rich set of diagnostic tests to aid in diagnosing server problems. The diagnostic programs collect the
following information about the server:
– Drive health information
– Event logs for ServeRAID controllers and service processors
– Hardware inventory, including PCI and USB information
– Light path diagnostics status
146
BladeCenter HX5 Blade ServerProblem Determination and Service Guide
Содержание BladeCenter HX5 1909
Страница 6: ...iv BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 16: ......
Страница 34: ...18 BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 72: ...56 BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 292: ...276 BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 296: ...280 BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 303: ...Taiwan Class A compliance statement Appendix B Notices 287 ...
Страница 304: ...288 BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 310: ...294 BladeCenter HX5 Blade ServerProblem Determination and Service Guide ...
Страница 311: ......
Страница 312: ...Part Number 46W8208 Printed in China 1P P N 46W8208 ...
Страница 313: ... 1P46W8208 ...