2.See “Diagnostic programs and error messages” on page 25 for more information.
v Error symptom charts
These charts list problem symptoms and steps to correct the problems. See “Error symptoms” on page 87 for more information.
vLight path diagnostics
Use the light path diagnostics to diagnose system errors quickly. See “Diagnosing problems using the light path diagnostics feature” on page 27 for more information.
POST error logs
When you turn on the server, it performs a series of tests to check the operation of server components and some of the options that are installed in the blade server. This series of tests is called the
If POST finishes without detecting any problems, the first screen of the operating system or application program appears.
If POST detects a problem, one or more beeps sound, and an error message appears on the screen. See “Beep codes” on page 77 and “POST error codes” on page 79 for more information.
Notes:
1.If a
2.A single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After you correct the cause of the first error message, the other error messages usually will not occur the next time you run the test.
Viewing the System Event Log (SEL)
The System Setup Utility (SSU) is used to view the System Event Log (SEL) records. Running the ssu.bat file provided on the SSU media invokes the SSU environment by running the Application Framework (AF). If the system starts up directly from the SSU media, this batch file starts automatically. If the system starts up from a different media, the SSU can be started manually. When started in local execution mode (the default mode), the SSU accepts user input from the keyboard and or mouse and presents a graphical user interface (GUI) on the primary monitor.
The SSU can run on writable or
The SSU automatically launches the SEL Manager after initializing the main window of the AF.
The SEL Manager
vExamine all SEL entries stored in the
Chapter 3. Diagnostics 23