Lenovo 7X69 User manual

ThinkSystem SR860
Messages and Codes Reference
Machine Type: 7X69 and 7X70

Note
Before using this information and the product it supports be sure to read and understand the safety
information and the safety instructions which are available at:https://pubs.lenovo.com/safety_documentation/
In addition be sure that you are familiar with the terms and conditions of the Lenovo warranty for your server
which can be found at:
http://datacentersupport.lenovo.com/warrantylookup
Fifteenth Edition (December 2023)
© Copyright enovo 2017, 2023.
LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered pursuant to a General Services
Administration (GSA) contract use reproduction or disclosure is subject to restrictions set forth in Contract No. GS-35F-
05925.

Contents
Contents . . . . . . . . . . . . . . . . . i
Chapter 1. Introduction . . . . . . . . . 1
Chapter 2. XClarity Controller
events . . . . . . . . . . . . . . . . . . 3
XCC events that automatically notify Support . . . . 4
XCC events organized by severity. . . . . . . . . 5
List of XClarity Controller events . . . . . . . . 24
Chapter 3. UEFI events . . . . . . . . 145
UEFI events organized by severity . . . . . . . 145
List of UEFI events. . . . . . . . . . . . . . 151
Chapter 4. XClarity Provisioning
Manager events . . . . . . . . . . . . 193
LXPM events organized by severity . . . . . . . 193
List of XClarity Provisioning Manager events . . . 196
Appendix A. Getting help and
technical assistance . . . . . . . . . . 217
Before you call . . . . . . . . . . . . . . . 217
Collecting service data . . . . . . . . . . . . 218
Contacting Support . . . . . . . . . . . . . 219
Index . . . . . . . . . . . . . . . . . . 221
© Copyright Lenovo 2017 2023 i

ii ThinkSystem SR860 Messages and Codes Reference

Chapter 1. Introduction
When attempting to resolve issues with your server the best practice is to begin with the event log of the
application that is managing the server:
• If you are managing the server from the Lenovo XClarity Administrator begin with the Lenovo XClarity
Administrator event log.
• If you are using some other management application begin with the Lenovo XClarity Controller event log.
The event log contains server hardware events that are recorded by the Lenovo XClarity Controller or by
UEFI. In addition events can be generated when you perform diagnostic testing on hard drives or memory
through the Lenovo XClarity Provisioning Manager (although these events are not stored in the event log).
Use this section to view the events that can be generated by Lenovo XClarity Controller UEFI or the Lenovo
XClarity Provisioning Manager. For each event a user action is available to help you understand what must
be done to resolve the issue.
Important:
• Lenovo XClarity Controller (XCC) supported version varies by product. All versions of Lenovo XClarity
Controller are referred to as Lenovo XClarity Controller and XCC in this document unless specified
otherwise. To see the XCC version supported by your server go to https://pubs.lenovo.com/lxcc-overview/.
• Lenovo XClarity Provisioning Manager (LXPM) supported version varies by product. All versions of Lenovo
XClarity Provisioning Manager are referred to as Lenovo XClarity Provisioning Manager and LXPM in this
document unless specified otherwise. To see the LXPM version supported by your server go to https://
pubs.lenovo.com/lxpm-overview/.
© Copyright Lenovo 2017 2023 1

2ThinkSystem SR860 Messages and Codes Reference

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 FQXSPCA0017M and perform
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 https://pubs.lenovo.com/lxcc-overview/.
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
Similar events are grouped together in categories. The alert category is in the following format: sever ty -
dev ce where:
© Copyright Lenovo 2017 2023 3

• sever ty 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.
• dev ce is the specific device in the server that caused the event to be generated.
Serviceable
Specifies whether user action is required to correct the problem.
CIM Information
Provides the prefix of the message ID and the sequence number that is used by the CIM message
registry.
SNMP Trap ID
The SNMP trap ID that is found in the SNMP alert management information base (MIB).
Automatically contact Service
You can configure the Lenovo XClarity Administrator to automatically notify Support (also known as call
home) if certain types of errors are encountered. If you have configured this function and this field is set
to Yes Lenovo Support will be notified automatically if the event is generated. While you wait for Lenovo
Support to call you can perform the recommended actions for the event.
Note: This documentation includes references to IBM web sites products and information about
obtaining service. IBM is Lenovo's preferred service provider for the Lenovo server products.
For more information about enabling Call Home from Lenovo XClarity Administrator see http://
sysmgt.lenovofiles.com/help/topic/com.lenovo.lxca.doc/admin_setupcallhome.html. In addition see “XCC
events that automatically notify Support” on page 4 for a consolidated list of all Lenovo XClarity
Controller events that are called home to Lenovo Support.
User Action
Indicates what actions you should perform to solve the event. Perform the steps listed in this section in
the order shown until the problem is solved. If you cannot solve the problem after performing all steps
contact Lenovo Support.
XCC events that automatically notify Support
You can configure the XClarity Administrator to automatically notify Support (also known as call home) if
certain types of errors are encountered. If you have configured this function see the table for a list of events
that automatically notify Support.
Table 1. Events that automat cally not fy Support
Event ID Message String
FQXSPCA0002M Numeric sensor [NumericSensorElementName] going low (lower critical) has
asserted.
FQXSPEM4014I The RAID controller has problem with the battery. Please contact technical
support to resolve this issue.([arg1] [arg2] [arg3] [arg4] [arg5])
FQXSPEM4015I The RAID controller detected unrecoverable error. The controller needs
replacement.([arg1] [arg2] [arg3] [arg4] [arg5])
FQXSPEM4025I One or more virtual drive have problem. Please contact technical support to
resolve this issue.([arg1] [arg2] [arg3] [arg4] [arg5])
FQXSPEM4026I Drive error was detected by RAID controller. Please contact technical support
to resolve this issue.([arg1] [arg2] [arg3] [arg4] [arg5])
4ThinkSystem SR860 Messages and Codes Reference

Table 1. Events that automat cally not fy Support (cont nued)
Event ID Message String
FQXSPIO0001L The connector [PhysicalConnectorElementName] has encountered a
configuration error.
FQXSPIO0011N An Uncorrectable Error has occurred on [SensorElementName].
FQXSPIO0015M Fault in slot [PhysicalConnectorSystemElementName] on system
[ComputerSystemElementName].
FQXSPPW0035M Numeric sensor [NumericSensorElementName] going low (lower critical) has
asserted.
FQXSPPW0047M Numeric sensor [NumericSensorElementName] going high (upper critical) has
asserted.
FQXSPPW0063M Sensor [SensorElementName] has transitioned to critical from a less severe
state.
FQXSPSD0001L The [StorageVolumeElementName] has a fault.
FQXSPSD0002G Failure Predicted on [StorageVolumeElementName] for array
[ComputerSystemElementName].
FQXSPSD0005L Array [ComputerSystemElementName] is in critical condition.
FQXSPSD0006L Array [ComputerSystemElementName] has failed.
FQXSPSS4004I Test Call Home Generated by user [arg1].
FQXSPSS4005I Manual Call Home by user [arg1]: [arg2].
XCC events organized by severity
The following table lists all XCC events organized by severity (Information Error and Warning).
Table 2. Events organ zed by sever ty
Event ID Message String Severity
FQXSPBR4000I Management Controller [arg1]: Configuration restored from a file by
user [arg2] from [arg3] at IP address [arg4].
Informational
FQXSPBR4002I Management Controller [arg1] Reset was caused by restoring default
values.
Informational
FQXSPBR4004I Server timeouts set by user [arg1]: EnableOSWatchdog=[arg2]
OSWatchdogTimout=[arg3] EnableLoaderWatchdog=[arg4]
LoaderTimeout=[arg5].
Informational
FQXSPBR4005I Management Controller [arg1]: Configuration saved to a file by user
[arg2].
Informational
FQXSPBR4006I Management Controller [arg1]: Configuration restoration from a file by
user [arg2] completed from [arg3] at IP address [arg4].
Informational
FQXSPBR4009I Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by group name [arg3].
Informational
FQXSPBR400AI Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by group name [arg3] completed.
Informational
FQXSPBR400BI Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by group name [arg3] failed to complete.
Informational
Chapter 2.XClarity Controller events 5

Table 2. Events organ zed by sever ty (cont nued)
Event ID Message String Severity
FQXSPBR400CI Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by group name [arg3] failed to start.
Informational
FQXSPBR400DI Neighbor group clone configuration was initiated by user [arg1]. Informational
FQXSPBR400EI Neighbor group firmware update was initiated by user [arg1]. Informational
FQXSPBR400FI The neighbor group management is [arg1] by user [arg2] from [arg3] at
IP address [arg4].
Informational
FQXSPBT0007I No bootable media available for system
[ComputerSystemElementName].
Informational
FQXSPCA0013I Sensor [SensorElementName] has transitioned to normal state. Informational
FQXSPCA2002I Numeric sensor [NumericSensorElementName] going low (lower
critical) has deasserted.
Informational
FQXSPCA2007I Numeric sensor [NumericSensorElementName] going high (upper
non-critical) has deasserted.
Informational
FQXSPCA2009I Numeric sensor [NumericSensorElementName] going high (upper
critical) has deasserted.
Informational
FQXSPCA2011I Numeric sensor [NumericSensorElementName] going high (upper
non-recoverable) has deasserted.
Informational
FQXSPCA2015I Sensor [SensorElementName] has deasserted the transition from
normal to non-critical state.
Informational
FQXSPCA2017I Sensor [SensorElementName] has transitioned to a less severe state
from critical.
Informational
FQXSPCA2019I Sensor [SensorElementName] has deasserted the transition to non-
recoverable from a less severe state.
Informational
FQXSPCN4000I Serial Redirection set by user [arg1]: Mode=[arg2] BaudRate=[arg3]
StopBits=[arg4] Parity=[arg5] SessionTerminateSequence=[arg6].
Informational
FQXSPCN4001I Remote Control session started by user [arg1] in [arg2] mode. Informational
FQXSPCN4002I User [arg1] has terminated an active CLI console session. Informational
FQXSPCN4003I Remote Control session started by user [arg1] in [arg2] mode has
been closed.
Informational
FQXSPCN4004I User [arg1] has created an active [arg2] console session. Informational
FQXSPCN4005I A [arg1] console session is timeout. Informational
FQXSPCN4006I User [arg1] has terminated an active IPMI console session. Informational
FQXSPDM4000I Inventory data changed for device [arg1] new device data hash=
[arg2] new master data hash=[arg3] .
Informational
FQXSPDM4001I Storage [arg1] has changed. Informational
FQXSPDM4003I TKLM servers set by user [arg1]: TKLMServer1=[arg2] Port=[arg3]
TKLMServer2=[arg4] Port=[arg5] TKLMServer3=[arg6] Port=[arg7]
TKLMServer4=[arg8] Port=[arg9].
Informational
FQXSPDM4004I TKLM servers device group set by user [arg1]:
TKLMServerDeviceGroup=[arg2] .
Informational
6ThinkSystem SR860 Messages and Codes Reference