Lenovo ThinkSystem SR850 Service manual

ThinkSystem SR850
Messages and Codes Reference
Machine Types: 7X18 and 7X19

Note
Before using this information and the roduct it su orts, be sure to read and understand the safety
information and the safety instructions, which are available at:htt s:// ubs.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:
htt ://datacentersu ort.lenovo.com/warrantylooku
Fifteenth Edition (November 2022)
© Copyright enovo 2017, 2022.
IMITED 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 Su ort . . . . 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 . . . . . . . . . . . . 191
LXPM events organized by severity . . . . . . . 191
List of XClarity Provisioning Manager events . . . 194
Appendix A. Getting help and
technical assistance . . . . . . . . . . 215
Before you call . . . . . . . . . . . . . . . 215
Collecting service data . . . . . . . . . . . . 216
Contacting Su ort . . . . . . . . . . . . . 217
Index . . . . . . . . . . . . . . . . . . 219
© Co yright Lenovo 2017, 2022 i

ii ThinkSystem SR850 Messages and Codes Reference

Chapter 1. Introduction
When attem ting to resolve issues with your server, the best ractice is to begin with the event log of the
a lication 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 a lication, 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 erform 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 hel you understand what must
be done to resolve the issue.
Important:
• Lenovo XClarity Controller (XCC) su orted version varies by roduct. All versions of Lenovo XClarity
Controller are referred to as Lenovo XClarity Controller and XCC in this document, unless s ecified
otherwise. To see the XCC version su orted by your server, go to htt s:// ubs.lenovo.com/lxcc-overview/.
• Lenovo XClarity Provisioning Manager (LXPM) su orted version varies by roduct. All versions of Lenovo
XClarity Provisioning Manager are referred to as Lenovo XClarity Provisioning Manager and LXPM in this
document, unless s ecified otherwise. To see the LXPM version su orted by your server, go to htt s://
ubs.lenovo.com/lx m-overview/.
© Co yright Lenovo 2017, 2022 1

2ThinkSystem SR850 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 re laceable text of FRU name or sensor name to identify the
failed com onent. So one XCC event ID could re resent a generic event or similar faults that ha ened on
different hardware com onents. The general way of roblem determination is to locate the event by ID,
identify the hardware com onent by message argument if it contains hardware com onent name, and then
erform actions defined in User Action.
Exam le:
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 com onent. It can be CPU,
PCI ada ter, OCP card or chi set. You can find the event by the event ID FQXSPCA0017M and erform
actions defined in User Action for the com onent.
For additional information about the Lenovo XClarity Controller event log, see “Viewing Event Logs” section
in the XCC documentation com atible with your server at htt s:// ubs.lenovo.com/lxcc-overview/.
For each event code, the following fields are dis layed:
Event identifier
An identifier that uniquely identifies an event.
Event description
The logged message string that a ears for an event. When the event string is dis layed in the event
log, information such as a s ecific com onent is dis layed. In this documentation, that additional
information a ears 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 ex lain why the event occurred.
Severity
An indication of the level of concern for the condition. The following severities can be dis layed.
• Informational. The event was recorded for audit ur oses, 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 ossible, 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 im airs service or an ex ected function.
Alert Category
Similar events are grou ed together in categories. The alert category is in the following format: sever ty -
dev ce, where:
© Co yright Lenovo 2017, 2022 3

• sever ty is one of the following severity levels:
– Critical. A key com onent in the server is no longer functioning.
– Warning. The event might rogress to a critical level.
– System. The event is the result of a system error or a configuration change.
• dev ce is the s ecific device in the server that caused the event to be generated.
Serviceable
S ecifies whether user action is required to correct the roblem.
CIM Information
Provides the refix of the message ID and the sequence number that is used by the CIM message
registry.
SNMP Trap ID
The SNMP tra 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 Su ort (also known as call
home) if certain ty es of errors are encountered. If you have configured this function and this field is set
to Yes, Lenovo Su ort will be notified automatically if the event is generated. While you wait for Lenovo
Su ort to call, you can erform the recommended actions for the event.
Note: This documentation includes references to IBM web sites, roducts, and information about
obtaining service. IBM is Lenovo's referred service rovider for the Lenovo server roducts.
For more information about enabling Call Home from Lenovo XClarity Administrator, see htt ://
sysmgt.lenovofiles.com/hel /to ic/com.lenovo.lxca.doc/admin_setu callhome.html. In addition, see “XCC
events that automatically notify Su ort” on age 4 for a consolidated list of all Lenovo XClarity
Controller events that are called home to Lenovo Su ort.
User Action
Indicates what actions you should erform to solve the event. Perform the ste s listed in this section in
the order shown until the roblem is solved. If you cannot solve the roblem after erforming all ste s,
contact Lenovo Su ort.
XCC events that automatically notify Support
You can configure the XClarity Administrator to automatically notify Su ort (also known as call home) if
certain ty es of errors are encountered. If you have configured this function, see the table for a list of events
that automatically notify Su ort.
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 roblem with the battery. Please contact technical
su ort to resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
FQXSPEM4015I The RAID controller detected unrecoverable error. The controller needs
re lacement.([arg1],[arg2],[arg3],[arg4],[arg5])
FQXSPEM4025I One or more virtual drive have roblem. Please contact technical su ort to
resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
FQXSPEM4026I Drive error was detected by RAID controller. Please contact technical su ort
to resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
4ThinkSystem SR850 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
[Com uterSystemElementName].
FQXSPPW0035M Numeric sensor [NumericSensorElementName] going low (lower critical) has
asserted.
FQXSPPW0047M Numeric sensor [NumericSensorElementName] going high (u er 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
[Com uterSystemElementName].
FQXSPSD0005L Array [Com uterSystemElementName] is in critical condition.
FQXSPSD0006L Array [Com uterSystemElementName] 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] com leted from [arg3] at IP address [arg4].
Informational
FQXSPBR4009I Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by grou name [arg3].
Informational
FQXSPBR400AI Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by grou name [arg3] com leted.
Informational
FQXSPBR400BI Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by grou name [arg3] failed to com lete.
Informational
Cha ter 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 grou name [arg3] failed to start.
Informational
FQXSPBR400DI Neighbor grou clone configuration was initiated by user [arg1]. Informational
FQXSPBR400EI Neighbor grou firmware u date was initiated by user [arg1]. Informational
FQXSPBR400FI The neighbor grou management is [arg1] by user [arg2] from [arg3] at
IP address [arg4].
Informational
FQXSPBT0007I No bootable media available for system
[Com uterSystemElementName].
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 (u er
non-critical) has deasserted.
Informational
FQXSPCA2009I Numeric sensor [NumericSensorElementName] going high (u er
critical) has deasserted.
Informational
FQXSPCA2011I Numeric sensor [NumericSensorElementName] going high (u er
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],
Sto Bits=[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 grou set by user [arg1]:
TKLMServerDeviceGrou =[arg2] .
Informational
6ThinkSystem SR850 Messages and Codes Reference