User Manual

Troubleshooting 65
Troubleshooting
Troubleshooting resources
The HP ProLiant Servers Troubleshooting Guide provides procedures for resolving common problems and
comprehensive courses of action for fault isolation and identification, error message interpretation, issue
resolution, and software maintenance on ProLiant servers and server blades. This guide includes problem-
specific flowcharts to help you navigate complex troubleshooting processes. To view the guide, select a
language:
English (http://www.hp.com/support/ProLiant_TSG_en)
French (http://www.hp.com/support/ProLiant_TSG_fr)
Italian (http://www.hp.com/support/ProLiant_TSG_it)
Spanish (http://www.hp.com/support/ProLiant_TSG_sp)
German (http://www.hp.com/support/ProLiant_TSG_gr)
Dutch (http://www.hp.com/support/ProLiant_TSG_nl)
Japanese (http://www.hp.com/support/ProLiant_TSG_jp)
Server diagnostic steps
This section covers the steps to take in order to diagnose a problem quickly.
To effectively troubleshoot a problem, HP recommends that you start with the first flowchart in this section,
"Start diagnosis flowchart (on page 69)," and follow the appropriate diagnostic path. If the other
flowcharts do not provide a troubleshooting solution, follow the diagnostic steps in "General diagnosis
flowchart (on page 70)." The General diagnosis flowchart is a generic troubleshooting process to be used
when the problem is not server-specific or is not easily categorized into the other flowcharts.
IMPORTANT: This guide provides information for multiple servers. Some information may not
apply to the server you are troubleshooting. Refer to the server documentation for information
on procedures, hardware options, software tools, and operating systems supported by the
server.
WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary
information in the server documentation before removing, replacing, reseating, or modifying
system components.
Important safety information
Familiarize yourself with the safety information in the following sections before troubleshooting the server.