The response includes all of the events
recorded, in the order that they occurred. Events are not sorted by
severity or other criteria. Each event includes a common set of
attributes:
SEVERITY indicates the importance of the
error and how it might impact server or iLO 3 availability.
FAILED indicates a problem or component
failure that might impact operational time if it is not
addressed.
CAUTION indicates an event that is not
expected during normal system operation. This might not indicate a
platform issue.
REPAIRED indicates that an event or
component failure has been addressed.
INFORMATIONAL indicates that something
noteworthy occurred, but operational time is not impacted.
CLASS indicates the subsystem that generated
the event, and can include iLO 3, environment, power, system error,
rack infrastructure, and more.
LAST_UPDATE indicates the most recent time
this event was modified.
INITIAL_UPDATE indicates when this event
first occurred.
COUNT indicates the number of times a
duplicate event happened.
DESCRIPTION indicates the nature of the
event and all recorded details.
The following response is typical of the data
returned from the iLO 3 Event Log:
<EVENT_LOG DESCRIPTION="iLO Event
Log">
<EVENT
SEVERITY="Caution"
CLASS="iLO"
LAST_UPDATE="04/04/2004 12:34"
INITIAL_UPDATE="04/04/2004 12:34"
COUNT="1"
DESCRIPTION="Server reset."
/>
...
</EVENT_LOG>
The following response is typical of the data
returned from the Integrated Management Log: