Chapter 5. Diagnostics; Diagnostic Tools; Event Logs - Lenovo ThinkServer TD200x Hardware Maintenance Manual

Hardware maintenance manual for td200x
Hide thumbs Also See for ThinkServer TD200x:
Table of Contents

Advertisement

Chapter 5. Diagnostics

This chapter describes the diagnostic tools that are available to help you solve problems that might occur in
the server.
If you cannot diagnose and correct a problem by using the information in this chapter, see Getting help and
technical assistance for more information.

Diagnostic tools

The following tools are available to help you diagnose and solve hardware-related problems:
• POST error messages
The power-on self-test (POST) generates messages to indicate successful test completion or the
detection of a problem. See POST error codes for more information.

• Event logs

For information about the POST event log, the system-event log, the integrated management module
(IMM) event log, and the DSA log, see Event logs and System-event log.
• Troubleshooting tables
These tables list problem symptoms and actions to correct the problems. See Troubleshooting tables.
• EasyLED diagnostics
Use the EasyLED diagnostics to diagnose system errors quickly. See EasyLED diagnostics for more
information.
• Diagnostic programs, messages, and error codes
The diagnostic programs are the primary method of testing the major components of the server. See
Diagnostic programs, messages, and error codes for more information.
Event logs
Error codes and messages are displayed in the following types of event logs:
• POST event log:
This log contains the three most recent error codes and messages that were generated during POST. You
can view the POST event log through the Setup utility.
• System-event log:
This log contains all IMM, POST, and system management interrupt (SMI) events. You can view the
system-event log through the Setup utility and through the Dynamic System Analysis (DSA) program (as
the IPMI event log).
The system-event log is limited in size. When it is full, new entries will not overwrite existing entries;
therefore, you must periodically save and then clear the system-event log through the Setup utility when
the IMM logs an event that indicates that the log is more than 75% full. When you are troubleshooting,
you might have to save and then clear the system-event log to make the most recent events available
for analysis.
Messages are listed on the left side of the screen, and details about the selected message are displayed
on the right side of the screen. To move from one entry to the next, use the Up Arrow (-) and Down
Arrow (¯) keys.
Some IMM sensors cause assertion events to be logged when their setpoints are reached. When a
setpoint condition no longer exists, a corresponding deassertion event is logged. However, not all events
are assertion-type events.
© Copyright Lenovo 2009, 2010
21

Advertisement

Table of Contents
loading

Table of Contents