System Event Log - Lenovo TD200 - ThinkServer - 3809 Hardware Maintenance Manual

Hardware maintenance manual
Hide thumbs Also See for TD200 - ThinkServer - 3809:
Table of Contents

Advertisement

• Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
• See Chapter 8 "Parts listing, TD200 Machine Types 3724, 3808, 3809, 3815, 3817, 3824, 3826, 3836" on page
257 to determine which components are customer replaceable units (CRU) and which components are
field replaceable units (FRU).
• If an action step is preceded by "(Trained service technician only)," that step must be performed only by
a trained service technician.
• Go to the Lenovo support Web site at http://www.lenovo.com/support/ to check for technical information,
hints, tips, and new device drivers or to submit a request for information.
Error code
Description
3818006
Opposite bank CRTM capsule signature
invalid
3818007
CRTM update capsule signature invalid
3828004
AEM power capping disabled

System event log

The system event log contains messages of three types:
Information
Warning
Error
Each message contains date and time information, and it indicates the source of the message (POST
or the IMM).
32
ThinkServer TD200 Hardware Maintenance Manual
Action
1. Switch the server firmware bank to the backup
bank.
2. Run the Setup utility, select Load Default Settings,
and save the settings.
3. Switch the bank back to the primary bank.
4. (Trained service technician only) Replace the
system board.
1. Run the Setup utility, select Load Default Settings,
and save the settings.
2. (Trained service technician only) Replace the
system board.
1. Check the settings and the event logs.
2. Make sure that the Active Energy Manager feature
is enabled in the Setup utility. Select System
Settings, Power, Active Energy, and Capping
Enabled.
3. Update the server firmware to the latest level (see
"Updating the firmware" on page 306).
4. Update the IMM firmware to the latest level (see
"Updating the firmware" on page 306).
Information messages do not require action; they
record significant system-level events, such as
when the server is started.
Warning messages do not require immediate action;
they indicate possible problems, such as when the
recommended maximum ambient temperature is
exceeded.
Error messages might require action; they indicate
system errors, such as when a fan is not detected.

Advertisement

Table of Contents
loading

Table of Contents