Post; Event Logs - Lenovo ThinkServer TS200 Hardware Maintenance Manual
Hardware maintenance manual for ts200
Hide thumbs
Also See for ThinkServer TS200:
- Installation and user manual (258 pages) ,
- Manual d’installation et d’utilisation (254 pages) ,
- Installations- und benutzerhandbuch (252 pages)
Table of Contents
Advertisement
server information locally through a generated text report file. You can also copy the log to removable
media and view the log from a Web browser. See "Running the diagnostic programs" on page 67 and
"Diagnostic messages" on page 68 for more information.
• Server LEDs
Use the LEDs on the server to diagnose system errors quickly. See "Error LEDs" on page 61 for more
information.
POST
When you turn on the server, it performs a series of tests to check the operation of the server components
and some optional devices in the server. This series of tests is called the power-on self-test, or POST.
Note: This server does not use beep codes for server status.
If a power-on password is set, you must type the password and press Enter, when prompted, for POST to run.
If POST detects a problem, an error message is displayed. See "POST error codes" on page 22 for more
information.
Event logs
Error codes and messages are displayed in the following types of event logs. Some of the error codes and
messages in the logs are abbreviated. When you are troubleshooting PCI-X slots, note that the event logs
report the PCI-X buses numerically. The numerical assignments vary depending on the configuration.
You can check the assignments by running the Setup utility (see "Using the Setup Utility" on page 255
for more information).
• POST event log: This log contains the three most recent error codes and messages that were generated
during POST. You can view the contents of the POST event log from the Setup utility (see "Using the
Setup Utility" on page 255).
• System-event log: This log contains messages that were generated during POST and all system status
messages from the service processor. You can view the contents of the system-event log from the Setup
utility (see "Viewing event logs from the Setup utility" on page 20 for more information).The system-event
log is limited in size. When it is full, new entries will not overwrite existing entries; therefore, you must
periodically 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 an error, be sure to clear the
system-event log so that you can find current errors more easily.
Each system-event log entry is displayed on its own page. 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.
The system-event log indicates an assertion event when an event has occurred. It indicates a deassertion
event when the event is no longer occurring.
• Integrated management module (IMM) event log: This log contains a superset of IMM, POST, and
system management interrupt (SMI) information that is in the system-event log. You can only access the
event log through the IMM Web interface. For more information, see "Event logs" on page 20.
• DSA log: This log is generated by the Dynamic System Analysis (DSA) Preboot program, and it contains
merged contents of the system-event log and the IMM system event log. You can view the DSA log
from the DSA Preboot program.
Viewing event logs from the Setup utility
To view the event logs, complete the following steps:
Step 1.
Turn on the server.
20
Hardware Maintenance Manual
Advertisement
Table of Contents
