UEFI diagnostic codes can be generated when the compute
node starts or while the compute node is running. UEFI diagnostic
codes are logged in the IMM event log in the compute node.
For each event code, the following fields are displayed:
- Event identifier
- An identifier that uniquely identifies an event.
- Event description
- The logged message string that appears for an event.
- Explanation
- Additional information to explain why the event occurred.
- Severity
- An indication of the level of concern for the condition. In the
event log, the severity is abbreviated to the first character.
-
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.
- Alert Category
- Similar events are grouped in categories. The alert category is
in the following format:
severity - device
severity is
one of the following severity levels:
-
Critical: A key component in the server is no longer functioning.
-
Warning: The event might progress to a critical level.
-
System: The event is the result of a system error or a
configuration change.
device component is the specific device in the
compute node that caused the event to be generated.
- User response
- The actions that you should perform to resolve the event.
Perform
the steps listed in this section in the order shown until the problem
is solved. After you perform all of the actions that are described
in this field, if you cannot solve the problem, contact IBM Support.