Lenovo System x3500 M5 Type 5464, Инструкция по установке и обслуживанию

Страница: 155 / 1236

Table 14. System pulse LEDs
LED Description Action
IMM2.1 heartbeat IMM2.1 heartbeat boot process. The following steps describe the different stages
of the IMM2.1 heartbeat sequencing process.
1. When this LED is blinking fast
(approximately 4Hz), this indicates,
that the IMM2.1 code is in the loading
process.
2. When this LED goes off momentarily, this
indicates that the IMM2.1 code has loaded
completely.
3. When this LED goes off momentarily and
then starts blinking slowing (approximately
1Hz), this indicates that IMM2.1 is fully
operational. You can now press the
power-control button to power-on the
server.
4. If this LED does not blink within 30 seconds
of connecting a power source to the server,
(trained technician only) replace the system
board.
Event logs
Error codes and messages are displayed in POST event log, system-event log, Integrated Management
Module II (IMM2) event log, and DSA event log.
• POST event log: This log contains the 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 “Starting the Setup
utility” on page 107). For more information about POST error codes, see Appendix B “UEFI (POST)
error codes” on page 1017.
• System-event log: This log contains POST and system management interrupt (SMI) events and all
events that are generated by the baseboard management controller that is embedded in the Integrated
Management Module II (IMM2). You can view the contents of the system-event log through the Setup
utility and through the Dynamic System Analysis (DSA) program (as 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 clear the system-event log through the Setup utility. When you are troubleshooting an error,
you might have to save and then clear the system-event log to make the most recent events available for
analysis. For more information about the system-event log, see Appendix A “Integrated Management
Module II (IMM2) error messages” on page 295.
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 IMM2.1 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.
• Integrated Management Module II (IMM2) event log: This log contains a filtered subset of all IMM2.1,
POST, and system management interrupt (SMI) events. You can view the IMM2.1 event log through the
IMM2.1 web interface. For more information, see “Logging on to the web interface” on page 115. You
can also view the IMM2.1 event log through the Dynamic System Analysis (DSA) program (as the ASM
event log). For more information about IMM2.1 error messages, see Appendix A “Integrated Management
Module II (IMM2) error messages” on page 295.
Chapter 4
.
Troubleshooting
139