would prefer to start by examining the logs, you can go directly to the subsection entitled “Errors and Reading Error Logs” (page 154).

Table 5-1lists the troubleshooting entry points.

Table 5-1 Troubleshooting Entry Points

Entry Point

Subsection or Location

 

 

Front panel/Diagnostic panel LEDs

“Troubleshooting Tools” (page 147)

 

 

System Event Log and Forward Progress Logs

“Errors and Reading Error Logs” (page 154)

 

 

offline and online Diagnostics/INIT button

“Troubleshooting Tools” (page 147)

 

 

System Event Analyzer (SEA)

“Troubleshooting Tools” (page 147)

 

 

Basic and Advanced Troubleshooting Tables

The following troubleshooting tables are designed for use by both trained and untrained support personnel. They should be the first tool used to determine the symptom(s) or condition of a suspect server. Be aware that the state of the front panel LEDs can be viewed either locally, or remotely by using the vfp command from the iLO 2 MP.

The tables are designed to cover troubleshooting symptoms from ac power on up to booting the operating system (OS), specifically in Steps 1-5. In most cases, the Table 5-2identifies the step number in Table 5-3where troubleshooting should begin. Alternatively, you can skip Table 5-2, and start with Step 1 in Table 5-3, sequencing through the table steps to locate the symptom/condition most descriptive of your current server status; this will become the first step in your troubleshooting procedure. Where appropriate, an action or actions prescribed in the “Action” column of Table 5-3will be followed by a reference to a corresponding subsection of this chapter for further information.

Figure 5-1 Front Panel LEDs

Initialization Button

External Health

 

 

 

 

 

 

System Health

 

System

 

Power LED/Button

Unit Identifier

 

 

Internal Health

 

 

Methodology 141