Lenovo ThinkSystem SR630 V2 Service manual

ThinkSystem SR630 V2
Messages and Codes Reference
Machine Types: 7Z70 and 7Z71

Note
Before sing this information and the prod ct it s pports, be s re to read and nderstand the safety
information and the safety instr ctions, which are available at:
http://thinksystem.lenovofiles.com/help/topic/safety_doc mentation/pdf_files.html
In addition, be s re that yo are familiar with the terms and conditions of the Lenovo warranty for yo r server,
which can be fo nd at:
http://datacenters pport.lenovo.com/warrantylook p
Fourth Edition (February 2022)
© Copyright Lenovo 2022
LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered p rs ant to a General Services
Administration (GSA) contract, se, reprod ction, or disclos re is s bject to restrictions set forth in Contract No. GS-35F-
05925.

Contents
Chapter 1 Messages 1
Chapter 2 XClarity Controller
events 3
XCC events that a tomatically notify S pport . . . . 4
XCC events organized by severity. . . . . . . . . 5
List of XClarity Controller events . . . . . . . . 22
Chapter 3 UEFI events 135
UEFI events organized by severity . . . . . . . 135
List of UEFI events. . . . . . . . . . . . . . 142
Chapter 4 XClarity Provisioning
Manager events 177
LXPM events organized by severity . . . . . . . 177
List of XClarity Provisioning Manager events . . . 180
Appendix A Getting help and
technical assistance 201
Before yo call . . . . . . . . . . . . . . . 201
Collecting service data . . . . . . . . . . . . 202
Contacting S pport . . . . . . . . . . . . . 203
Index 205
© Copyright Lenovo 2022 i

ii ThinkSystem SR630 V2 Messages and Codes Reference

Chapter 1 Messages
When attempting to resolve iss es with yo r server, the best practice is to begin with the event log of the
application that is managing the server:
• If yo are managing the server from the Lenovo XClarity Administrator, begin with the Lenovo XClarity
Administrator event log.
• If yo are sing 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 yo perform diagnostic testing on hard drives or memory
thro gh the LXPM (altho gh 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 LXPM.
For each event, a ser action is available to help yo nderstand what m st be done to resolve the iss e.
Important:
• Lenovo XClarity Controller (XCC) s pported version varies by prod ct. All versions of Lenovo XClarity
Controller are referred to as Lenovo XClarity Controller and XCC in this doc ment, nless specified
otherwise. To see the XCC version s pported by yo r server, go to https://sysmgt.lenovofiles.com/help/
topic/lxcc_frontend/lxcc_overview.html.
• Lenovo XClarity Provisioning Manager (LXPM) s pported version varies by prod ct. All versions of Lenovo
XClarity Provisioning Manager are referred to as Lenovo XClarity Provisioning Manager and LXPM in this
doc ment, nless specified otherwise. To see the LXPM version s pported by yo r server, go to https://
sysmgt.lenovofiles.com/help/topic/lxpm_frontend/lxpm_prod ct_page.html.
© Copyright Lenovo 2022 1

2ThinkSystem SR630 V2 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 niq e identifier sed to search for XCC events. The event message may
have one or more arg ments, which co ld be replaceable text of FRU name or sensor name to identify the
failed component. So one XCC event ID co ld represent a generic event or similar fa lts 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 arg ment 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. Yo can find the event by the event ID FQXSPCA0017M and perform
actions defined in User Action for the component.
For additional information abo t the Lenovo XClarity Controller event log, see “Viewing Event Logs” section
in the XCC doc mentation compatible with yo r server at https://sysmgt.lenovofiles.com/help/topic/lxcc_
frontend/lxcc_overview.html.
For each event code, the following fields are displayed:
Event identifier
An identifier that niq ely 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 s ch as a specific component is displayed. In this doc mentation, that additional
information appears as variables, which incl de b t not limited to the following:
• [SensorElementName], [ManagedElementName] , [ProcessorElementName],
[ComputerSystemElementName], [PowerSupplyElementName], ...
• [arg1], [arg2], [arg3], [arg4], [arg5]...
Explanation
Provides additional information to explain why the event occ rred.
Severity
An indication of the level of concern for the condition. The following severities can be displayed.
• Informational. The event was recorded for a dit p rposes, s ally a ser action or a change of states
that is normal behavior.
• Warning. The event is not as severe as an error, b t if possible, the condition sho ld be corrected
before it becomes an error. It might also be a condition that req ires additional monitoring or
maintenance.
• Error. The event is a fail re or critical condition that impairs service or an expected f nction.
Alert Category
© Copyright Lenovo 2022 3

Similar events are gro ped together in categories. The alert category is in the following format: sever ty -
dev ce, where:
• sever ty is one of the following severity levels:
– Critical. A key component in the server is no longer f nctioning.
– Warning. The event might progress to a critical level.
– System. The event is the res lt of a system error or a config ration change.
• dev ce is the specific device in the server that ca sed the event to be generated.
Serviceable
Specifies whether ser action is req ired to correct the problem.
CIM Information
Provides the prefix of the message ID and the seq ence n mber that is sed by the CIM message
registry.
SNMP Trap ID
The SNMP trap ID that is fo nd in the SNMP alert management information base (MIB).
Automatically contact Service
Yo can config re the Lenovo XClarity Administrator to a tomatically notify S pport (also known as call
home) if certain types of errors are enco ntered. If yo have config red this f nction and this field is set
to Yes, Lenovo S pport will be notified a tomatically if the event is generated. While yo wait for Lenovo
S pport to call, yo can perform the recommended actions for the event.
Note: This doc mentation incl des references to IBM web sites, prod cts, and information abo t
obtaining service. IBM is Lenovo's preferred service provider for the Lenovo server prod cts.
For more information abo t enabling Call Home from Lenovo XClarity Administrator, see http://
sysmgt.lenovofiles.com/help/topic/com.lenovo.lxca.doc/admin_set pcallhome.html. In addition, see “XCC
events that a tomatically notify S pport” on page 4 for a consolidated list of all Lenovo XClarity
Controller events that are called home to Lenovo S pport.
User Action
Indicates what actions yo sho ld perform to solve the event. Perform the steps listed in this section in
the order shown ntil the problem is solved. If yo cannot solve the problem after performing all steps,
contact Lenovo S pport.
XCC events that automatically notify Support
Yo can config re the XClarity Administrator to a tomatically notify S pport (also known as call home) if
certain types of errors are enco ntered. If yo have config red this f nction, see the table for a list of events
that a tomatically notify S pport.
Table 1. Events that automat cally not fy Support
Event ID Message String
FQXSPEM4014I The RAID controller has problem with the battery. Please contact technical
s pport to resolve this iss e.([arg1],[arg2],[arg3],[arg4],[arg5])
FQXSPEM4015I The RAID controller detected nrecoverable error. The controller needs
replacement.([arg1],[arg2],[arg3],[arg4],[arg5])
FQXSPEM4025I One or more virt al drive have problem. Please contact technical s pport to
resolve this iss e.([arg1],[arg2],[arg3],[arg4],[arg5])
FQXSPEM4026I Drive error was detected by RAID controller. Please contact technical s pport
to resolve this iss e.([arg1],[arg2],[arg3],[arg4],[arg5])
4ThinkSystem SR630 V2 Messages and Codes Reference

Table 1. Events that automat cally not fy Support (cont nued)
Event ID Message String
FQXSPIO0011N An Uncorrectable Error has occ rred on [SensorElementName].
FQXSPIO0015M Fa lt in slot [PhysicalConnectorSystemElementName] on system
[Comp terSystemElementName].
FQXSPPW0002L [PowerS pplyElementName] has Failed.
FQXSPPW0035M N meric sensor [N mericSensorElementName] going low (lower critical) has
asserted.
FQXSPPW0047M N meric sensor [N mericSensorElementName] going high ( pper critical) has
asserted.
FQXSPSD0001L The [StorageVol meElementName] has a fa lt.
FQXSPSD0002G Fail re Predicted on [StorageVol meElementName] for array
[Comp terSystemElementName].
FQXSPSD0002L Drive [arg1] in the enclos re/chassis(MTM-SN: [arg2]) has a fa lt.
FQXSPSD0003G Fail re Predicted on drive [arg1] in the enclos re/chassis (MTM-SN: [arg2]).
FQXSPSD0006L Array [Comp terSystemElementName] has failed.
FQXSPSD0008L Array failed on drive [arg1] in the enclos re/chassis (MTM-S/N: [arg2]).
FQXSPSS4004I Test Call Home Generated by ser [arg1].
FQXSPSS4005I Man al Call Home by ser [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]: Config ration restored from a file by
ser [arg2].
Informational
FQXSPBR4002I Management Controller [arg1] Reset was ca sed by restoring defa lt
val es.
Informational
FQXSPBR4004I Server timeo ts set by ser [arg1]: EnableOSWatchdog=[arg2],
OSWatchdogTimo t=[arg3], EnableLoaderWatchdog=[arg4],
LoaderTimeo t=[arg5].
Informational
FQXSPBR4005I Management Controller [arg1]: Config ration saved to a file by ser
[arg2].
Informational
FQXSPBR4006I Management Controller [arg1]: Config ration restoration from a file by
ser [arg2] completed.
Informational
FQXSPBT0007I No bootable media available for system
[Comp terSystemElementName].
Informational
FQXSPCA2002I N meric sensor [N mericSensorElementName] going low (lower
critical) has deasserted.
Informational
FQXSPCA2007I N meric sensor [N mericSensorElementName] going high ( pper
non-critical) has deasserted.
Informational
Chapter 2.XClarity Controller events 5

Table 2. Events organ zed by sever ty (cont nued)
Event ID Message String Severity
FQXSPCA2009I N meric sensor [N mericSensorElementName] going high ( pper
critical) has deasserted.
Informational
FQXSPCA2011I N meric sensor [N mericSensorElementName] going high ( pper
non-recoverable) has deasserted.
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 ser [arg1]: Mode=[arg2], Ba dRate=[arg3],
StopBits=[arg4], Parity=[arg5], SessionTerminateSeq ence=[arg6].
Informational
FQXSPCN4001I Remote Control session started by ser [arg1] in [arg2] mode. Informational
FQXSPCN4002I User [arg1] has terminated an active console session. Informational
FQXSPCN4003I Remote Control session started by ser [arg1] in [arg2] mode has
been closed.
Informational
FQXSPDA2000I The System [Comp terSystemElementName] has detected a POST
Error deassertion.
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 ser [arg1]: TKLMServer1=[arg2] Port=[arg3],
TKLMServer2=[arg4] Port=[arg5], TKLMServer3=[arg6] Port=[arg7],
TKLMServer4=[arg8] Port=[arg9].
Informational
FQXSPDM4004I TKLM servers device gro p set by ser [arg1]:
TKLMServerDeviceGro p=[arg2] .
Informational
FQXSPDM4005I User [arg1] has generated a new encryption key pair and installed a
self-signed certificate for the TKLM client.
Informational
FQXSPDM4006I User [arg1] has generated a new encryption key and certificate
signing req est for the TKLM client.
Informational
FQXSPDM4007I User [arg1] has imported a signed certificate for the TKLM client from
[arg2].
Informational
FQXSPDM4008I User [arg1] has imported a server certificate for the TKLM server. Informational
FQXSPDM4009I User [arg1] has [arg2] file [arg3] from [arg4]. Informational
FQXSPDM4010I Inventory data collecting and processing complete for [arg1],
seq ence n mber is [arg2].
Informational
FQXSPEA2001I Sensor [SensorElementName] has deasserted the transition from
normal to non-critical state.
Informational
FQXSPEA2002I Sensor [SensorElementName] has transitioned to a less severe state
from critical.
Informational
FQXSPEM0003I The Log [RecordLogElementName] has been cleared. Informational
FQXSPEM0004I The Log [RecordLogElementName] is f ll. Informational
FQXSPEM0005I The Log [RecordLogElementName] is almost f ll. Informational
6ThinkSystem SR630 V2 Messages and Codes Reference