Table of Contents
Advertisement
Chapter 2. XClarity Controller events
When a hardware event is detected by the Lenovo XClarity Controller on the server, the Lenovo XClarity
Controller writes that event in the system-event log on the server.
Notes: Event identifier (ID) is a unique identifier used to search for XCC events. The event message may
have one or more arguments, which could be replaceable text of FRU name or sensor name to identify the
failed component. So one XCC event ID could represent a generic event or similar faults that happened on
different hardware components. The general way of problem determination is to locate the event by ID,
identify the hardware component by message argument if it contains hardware component name, and then
perform actions defined in User Action.
Example:
FQXSPCA0017M: Sensor [SensorElementName] has transitioned to critical from a less severe state
where:
FQXSPCA0017M
•
is the event ID.
• [SensorElementName] is a sensor variable, indicating the name of hardware component. It can be CPU,
PCI adapter, OCP card or chipset. You can find the event by the event ID
actions defined in User Action for the component.
For additional information about the Lenovo XClarity Controller event log, see "Viewing Event Logs" section
in the XCC documentation compatible with your server at
frontend/lxcc_overview.html
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. When the event string is displayed in the event
log, information such as a specific component is displayed. In this documentation, that additional
information appears as variables, which include but not limited to the following:
• [SensorElementName], [ManagedElementName] , [ProcessorElementName],
[ComputerSystemElementName], [PowerSupplyElementName], ...
• [arg1], [arg2], [arg3], [arg4], [arg5]...
Explanation
Provides additional information to explain why the event occurred.
Severity
An indication of the level of concern for the condition. The following severities can be displayed.
• Informational. 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
© Copyright Lenovo 2022
.
FQXSPCA0017M
https://sysmgt.lenovofiles.com/help/topic/lxcc_
and perform
5
Advertisement
Table of Contents
