Table of Contents
Advertisement
The BMC log is limited in size. When the log is full, new entries will not overwrite
existing entries; therefore, you must periodically clear the BMC log through the
Configuration/Setup Utility program (the menu choices are described in the User's
Guide). When you are troubleshooting an error, be sure to clear the BMC log so
that you can find current errors more easily.
Entries that are written to the BMC log during the early phase of POST show an
incorrect date and time as the default time stamp; however, the date and time are
corrected as POST continues.
Each BMC log entry is displayed on its own page. To display all the data for an
entry, use the Up Arrow and Down Arrow keys or the Page Up and Page Down
keys. To move from one entry to the next, select Get Next Entry or Get Previous
Entry.
The log indicates an assertion event when an event has occurred. It indicates a
deassertion event when the event is no longer occurring.
Some of the error codes and messages in the BMC log are abbreviated.
If you view the BMC log through the Web interface of the optional Remote
Supervisor Adapter II SlimLine, the messages can be translated.
IPMI BMC system-event log messages
The following table describes the possible IPMI BMC system-event log messages
and suggested actions to correct the detected problems.
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, "Parts listing, Type 7940 and 7941 servers," on page 19 to determine which components
are customer replaceable units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by "(Trained service technician only)," that step must be performed only by a
trained service technician.
BMC log message
Fan 1 Tach LC Asserted
Fan 1 Tach LNR Asserted
Fan 2 Tach LC Asserted
Fan 2 Tach LNR Asserted
Fan 3 Tach LC Asserted
Fan 3 Tach LNR Asserted
110
IBM System x3455 Type 7940 and 7941: Problem Determination and Service Guide
Event Direction and Type: The first position of the field is the direction.
0: Assertion
1: Deassertion
The remaining 7 positions identify the type of threshold crossing or trigger that
produced the event. This field also identifies the class of the event (discrete,
threshold, or OEM).
Event Data: This field shows additional information about the entry.
Sensor
type
04h
04h
04h
04h
04h
04h
Sensor
number
Action
40h
1. Make sure that the air baffle is in place
40h
and installed correctly.
41h
2. Make sure that fan n is fully seated (press
41h
down on the fan).
42h
3. Reseat fan n cable.
42h
4. Replace fan n.
5. (Trained service technician only) Replace
the power supply.
Advertisement
Table of Contents
