Installation Manual

• Automatic shutdown started
• Automatic shutdown canceled
• Drive failure
Viewing the IML
1. Navigate to the Information→Integrated Management Log page.
2. Optional: Use the IML filters to customize the log view.
IML details
• The first column on the left side of the web interface displays a check box next to each event
with Critical or Caution status. Use this check box to select an event to mark as repaired.
For information about marking events as repaired, see “Marking an IML entry as repaired”
(page 186).
• ID—The event ID number. Events are numbered in the order in which they are generated.
By default, the IML is sorted by the ID, with the most recent event at the top. A factory reset
will reset the counter.
• Severity—The importance of the detected event.
• Class—Identifies the type of event that occurred, for example, network, maintenance, or
system revision.
• Last Update—The date and time when the latest event of this type occurred. This value is
based on the date and time stored by the iLO firmware.
If iLO did not recognize the date and time when an event was updated, [NOT SET] is
displayed.
• Initial Update—The date and time when the first event of this type occurred. This value is
based on the date and time stored by the iLO firmware.
If iLO did not recognize the date and time when the event was first created, [NOT SET] is
displayed.
• Count—The number of times this event has occurred (if supported).
In general, important events generate an IML entry each time they occur. They are not
consolidated into one event log entry.
When less important events are repeated, they are consolidated into one IML entry, and the
Count and Last Update values are updated. Each event type has a specific time interval
that determines whether repeated events are consolidated or a new event is logged.
• Description—The description identifies the component and detailed characteristics of the
recorded event.
If the iLO firmware is rolled back, the description UNKNOWN EVENT TYPE might be displayed
for events recorded by the newer firmware. You can resolve this issue by updating the
firmware to the latest supported version, or by clearing the log.
Integrated Management Log 185