Appendix A. Integrated Management Module Ii (Imm2) Error Messages - IBM x3550 M4 Type 7914 Installation And Service Manual

Appendix A. Integrated management module II (IMM2) error
messages
When a hardware event is detected by the IMM on the server, the IMM logs that
event in the system-event log in the server.
For each event code, the following fields are displayed:
Event identifier
Event description
Explanation
Severity
Alert Category
Serviceable
© Copyright IBM Corp. 2012, 2014
A hexadecimal identifier that uniquely identifies an event or class of
events. In this documentation, the event identifiers are prefixed with 0x
and followed by eight characters.
The logged message string that appears for an event. When the event
string is displayed in the system-event log, information such as a specific
component is displayed. In this documentation, that additional information
appears as variables, such as [arg1] or [arg2].
Additional information to explain why the event occurred.
An indication of the level of concern for the condition. In the system-event
log, severity is abbreviated to the first character. The following severities
can be displayed.
Info: The event was recorded for audit purposes, usually a user action
or a change of states that is normal behavior.
Warning:
The event is not as severe as an error, but if possible, the condition
should be corrected before it becomes an error. It might also be a
condition that requires additional monitoring or maintenance.
Error: The event is a failure or critical condition that impairs service or an
expected function.
Similar events are grouped together in categories. The alert category is in
the following format:
severity - device
severity is one of the following severity levels:
v Critical: A key component in the server is no longer functioning.
v Warning: The event might progress to a critical level.
v System: The event is the result of a system error or a configuration
change.
device is the specific device in the server that caused the event to be
generated.
Whether user action is required to correct the problem.
335