Lenovo ThinkSystem SR850 V2 User manual

ThinkSystem SR850 V2
System Events Service Guide
Machine Types: 7D31 and 7D32

Note
Be ore using this in ormation and the product it supports, be sure to read and understand the sa ety
in ormation and the sa ety instructions, which are available at:
http://thinksystem.lenovo iles.com/help/topic/sa ety_documentation/pd _ iles.html
In addition, be sure that you are amiliar with the terms and conditions o the Lenovo warranty or your server,
which can be ound at:
http://datacentersupport.lenovo.com/warrantylookup
Third Edition (July 2021)
© Copyright Leno o 2020, 2021.
LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is deli ered pursuant to a General Ser ices
Administration (GSA) contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No.
GS-35F-05925.

Contents
Chapter 1. Introduction . . . . . . . . . 1
Chapter 2. XClarity Controller
e ents . . . . . . . . . . . . . . . . . . 3
XCC events that automatically noti y Support . . . . 4
XCC events organized by severity. . . . . . . . . 5
List o XClarity Controller events . . . . . . . . 22
Chapter 3. UEFI e ents . . . . . . . . 183
UEFI events organized by severity . . . . . . . 183
List o UEFI events. . . . . . . . . . . . . . 189
Chapter 4. XClarity Pro isioning
Manager e ents . . . . . . . . . . . . 241
LXPM events organized by severity . . . . . . . 241
List o XClarity Provisioning Manager events . . . 244
Appendix A. Getting help and
technical assistance . . . . . . . . . . 277
Be ore you call . . . . . . . . . . . . . . . 277
Collecting service data . . . . . . . . . . . . 278
Contacting Support . . . . . . . . . . . . . 279
Index . . . . . . . . . . . . . . . . . . 281
© Copyright Lenovo 2020, 2021 i

ii ThinkSystem SR850 V2 System Events Service Guide

Chapter 1. Introduction
When attempting to resolve issues with your server, the best practice is to begin with the event log o the
application that is managing the server:
• I you are managing the server rom the Lenovo XClarity Administrator, begin with the Lenovo XClarity
Administrator event log.
• I 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 per orm diagnostic testing on hard drives or memory
through the Lenovo XClarity Provisioning Manager V3 (although these events are not stored in the event log).
Follow the instructions in this section to view the events that can be generated by Lenovo XClarity Controller,
UEFI, or the Lenovo XClarity Provisioning Manager V3. For each event, a user action is available to help you
understand what must be done to resolve the issue.
© Copyright Lenovo 2020, 2021 1

2ThinkSystem SR850 V2 System Events Service Guide

Chapter 2. XClarity Controller e ents
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 identi ier (ID) is a unique identi ier used to search or XCC events. The event message may
have one or more arguments, which could be replaceable text o FRU name or sensor name to identi y the
ailed component. So one XCC event ID could represent a generic event or similar aults that happened on
di erent hardware components. The general way o problem determination is to locate the event by ID,
identi y the hardware component by message argument i it contains hardware component name, and then
per orm actions de ined 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 o hardware component. It can be CPU,
PCI adapter, OCP card or chipset. You can ind the event by the event ID FQXSPCA0017M and per orm
actions de ined in User Action or the component.
For additional in ormation about the Lenovo XClarity Controller event log, see http://sysmgt.lenovo iles.com/
help/topic/com.lenovo.systems.management.xcc.doc/event_log.html.
For each event code, the ollowing ields are displayed:
E ent identifier
An identi ier that uniquely identi ies an event.
E ent description
The logged message string that appears or an event. When the event string is displayed in the event
log, in ormation such as a speci ic component is displayed. In this documentation, that additional
in ormation appears as variables, which include but not limited to the ollowing:
• [SensorElementName], [ManagedElementName] , [ProcessorElementName],
[ComputerSystemElementName], [PowerSupplyElementName], ...
• [arg1], [arg2], [arg3], [arg4], [arg5]...
Explanation
Provides additional in ormation to explain why the event occurred.
Se erity
An indication o the level o concern or the condition. The ollowing severities can be displayed.
• Informational. The event was recorded or audit purposes, usually a user action or a change o states
that is normal behavior.
• Warning. The event is not as severe as an error, but i possible, the condition should be corrected
be ore it becomes an error. It might also be a condition that requires additional monitoring or
maintenance.
• Error. The event is a ailure or critical condition that impairs service or an expected unction.
Alert Category
Similar events are grouped together in categories. The alert category is in the ollowing ormat: sever ty -
dev ce, where:
© Copyright Lenovo 2020, 2021 3

• sever ty is one o the ollowing severity levels:
– Critical. A key component in the server is no longer unctioning.
– Warning. The event might progress to a critical level.
– System. The event is the result o a system error or a con iguration change.
• dev ce is the speci ic device in the server that caused the event to be generated.
Ser iceable
Speci ies whether user action is required to correct the problem.
CIM Information
Provides the pre ix o the message ID and the sequence number that is used by the CIM message
registry.
SNMP Trap ID
The SNMP trap ID that is ound in the SNMP alert management in ormation base (MIB).
Automatically contact Ser ice
You can con igure the Lenovo XClarity Administrator to automatically noti y Support (also known as call
home) i certain types o errors are encountered. I you have con igured this unction and this ield is set
to Yes, Lenovo Support will be noti ied automatically i the event is generated. While you wait or Lenovo
Support to call, you can per orm the recommended actions or the event.
Note: This documentation includes re erences to IBM web sites, products, and in ormation about
obtaining service. IBM is Lenovo's pre erred service provider or the Lenovo server products.
For more in ormation about enabling Call Home rom Lenovo XClarity Administrator, see http://
sysmgt.lenovo iles.com/help/topic/com.lenovo.lxca.doc/admin_setupcallhome.html. In addition, see “XCC
events that automatically noti y Support” on page 4 or a consolidated list o all Lenovo XClarity
Controller events that are called home to Lenovo Support.
User Action
Indicates what actions you should per orm to solve the event. Per orm the steps listed in this section in
the order shown until the problem is solved. I you cannot solve the problem a ter per orming all steps,
contact Lenovo Support.
XCC e ents that automatically notify Support
You can con igure the XClarity Administrator to automatically noti y Support (also known as call home) i
certain types o errors are encountered. I you have con igured this unction, see the table or a list o events
that automatically noti y Support.
Table 1. Events that automat cally not fy Support
E ent ID Message String
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])
FQXSPIO0001L The connector [PhysicalConnectorElementName] has encountered a
con iguration error.
4ThinkSystem SR850 V2 System Events Service Guide

Table 1. Events that automat cally not fy Support (cont nued)
E ent ID Message String
FQXSPIO0011N An Uncorrectable Error has occurred on [SensorElementName].
FQXSPIO0015M Fault in slot [PhysicalConnectorSystemElementName] on system
[ComputerSystemElementName].
FQXSPMA0007L Scrub Failure or [PhysicalMemoryElementName] on Subsystem
[MemoryElementName].
FQXSPMA0008N Uncorrectable error detected or [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
FQXSPMA0011G Memory Logging Limit Reached or [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
FQXSPPU0004M [ProcessorElementName] has Failed with FRB1/BIST condition.
FQXSPPW0002L [PowerSupplyElementName] has Failed.
FQXSPPW0035M Numeric sensor [NumericSensorElementName] going low (lower critical) has
asserted.
FQXSPPW0047M Numeric sensor [NumericSensorElementName] going high (upper critical) has
asserted.
FQXSPSD0001L The [StorageVolumeElementName] has been disabled due to a detected ault.
FQXSPSD0002G Failure Predicted on [StorageVolumeElementName] or array
[ComputerSystemElementName].
FQXSPSD0002L Drive [arg1] in the enclosure/chassis(MTM-SN: [arg2]) has been disabled due
to a detected ault.
FQXSPSD0003G Failure Predicted on drive [arg1] in the enclosure/chassis (MTM-SN: [arg2]).
FQXSPSD0006L Array [ComputerSystemElementName] has ailed.
FQXSPSD0008L Array ailed on drive [arg1] in the enclosure/chassis (MTM-S/N: [arg2]).
FQXSPSS4004I Test Call Home Generated by user [arg1].
FQXSPSS4005I Manual Call Home by user [arg1]: [arg2].
XCC e ents organized by se erity
The ollowing table lists all XCC events, organized by severity (In ormation, Error, and Warning).
Table 2. Events organ zed by sever ty
E ent ID Message String Se erity
FQXSPBR4000I Management Controller [arg1]: Con iguration restored rom a ile by
user [arg2].
In ormational
FQXSPBR4002I Management Controller [arg1] Reset was caused by restoring de ault
values.
In ormational
FQXSPBR4004I Server timeouts set by user [arg1]: EnableOSWatchdog=[arg2],
OSWatchdogTimout=[arg3], EnableLoaderWatchdog=[arg4],
LoaderTimeout=[arg5].
In ormational
FQXSPBR4005I Management Controller [arg1]: Con iguration saved to a ile by user
[arg2].
In ormational
Chapter 2.XClarity Controller events 5

Table 2. Events organ zed by sever ty (cont nued)
E ent ID Message String Se erity
FQXSPBR4006I Management Controller [arg1]: Con iguration restoration rom a ile by
user [arg2] completed.
In ormational
FQXSPBT0007I No bootable media available or system
[ComputerSystemElementName].
In ormational
FQXSPCA2002I Numeric sensor [NumericSensorElementName] going low (lower
critical) has deasserted.
In ormational
FQXSPCA2007I Numeric sensor [NumericSensorElementName] going high (upper
non-critical) has deasserted.
In ormational
FQXSPCA2009I Numeric sensor [NumericSensorElementName] going high (upper
critical) has deasserted.
In ormational
FQXSPCA2011I Numeric sensor [NumericSensorElementName] going high (upper
non-recoverable) has deasserted.
In ormational
FQXSPCA2015I Sensor [SensorElementName] has deasserted the transition rom
normal to non-critical state.
In ormational
FQXSPCA2017I Sensor [SensorElementName] has transitioned to a less severe state
rom critical.
In ormational
FQXSPCA2019I Sensor [SensorElementName] has deasserted the transition to non-
recoverable rom a less severe state.
In ormational
FQXSPCN4000I Serial Redirection set by user [arg1]: Mode=[arg2], BaudRate=[arg3],
StopBits=[arg4], Parity=[arg5], SessionTerminateSequence=[arg6].
In ormational
FQXSPCN4001I Remote Control session started by user [arg1] in [arg2] mode. In ormational
FQXSPCN4002I User [arg1] has terminated an active console session. In ormational
FQXSPCN4003I Remote Control session started by user [arg1] in [arg2] mode has
been closed.
In ormational
FQXSPCR2001I Sensor [SensorElementName] has deasserted the transition to non-
recoverable rom a less severe state.
In ormational
FQXSPDA2000I The System [ComputerSystemElementName] has detected a POST
Error deassertion.
In ormational
FQXSPDM4000I Inventory data changed or device [arg1], new device data hash=
[arg2], new master data hash=[arg3] .
In ormational
FQXSPDM4001I Storage [arg1] has changed. In ormational
FQXSPDM4003I TKLM servers set by user [arg1]: TKLMServer1=[arg2] Port=[arg3],
TKLMServer2=[arg4] Port=[arg5], TKLMServer3=[arg6] Port=[arg7],
TKLMServer4=[arg8] Port=[arg9].
In ormational
FQXSPDM4004I TKLM servers device group set by user [arg1]:
TKLMServerDeviceGroup=[arg2] .
In ormational
FQXSPDM4005I User [arg1] has generated a new encryption key pair and installed a
sel -signed certi icate or the TKLM client.
In ormational
FQXSPDM4006I User [arg1] has generated a new encryption key and certi icate
signing request or the TKLM client.
In ormational
FQXSPDM4007I User [arg1] has imported a signed certi icate or the TKLM client rom
[arg2].
In ormational
6ThinkSystem SR850 V2 System Events Service Guide