Lenovo 7Y45 User manual

ThinkSystem ST250
Messages and Codes Reference
Machine Types: 7Y45 and 7Y46

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
Twelfth Edition (July 2023)
© Copyri ht Lenovo 2018, 2023.
LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered ursuant to a General Services
Administration (GSA) contract, use, re roduction, or disclosure is subject to restrictions set forth in Contract No. GS-35F-
05925.

Contents
Chapter 1. Messa es . . . . . . . . . . 1
Event and alert message format . . . . . . . . . 1
Chapter 2. XClarity Controller
events . . . . . . . . . . . . . . . . . . 5
XCC events that automatically notify Su ort . . . . 6
XCC events organized by severity. . . . . . . . . 7
List of XClarity Controller events . . . . . . . . 26
Chapter 3. UEFI events . . . . . . . . 149
UEFI events organized by severity . . . . . . . 149
List of UEFI events. . . . . . . . . . . . . . 152
Chapter 4. XClarity Provisionin
Mana er events . . . . . . . . . . . . 171
LXPM events organized by severity . . . . . . . 171
List of XClarity Provisioning Manager events . . . 174
Appendix A. Gettin help and
technical assistance . . . . . . . . . . 195
Before you call . . . . . . . . . . . . . . . 195
Collecting service data . . . . . . . . . . . . 196
Contacting Su ort . . . . . . . . . . . . . 197
Index . . . . . . . . . . . . . . . . . . 199
© Co yright Lenovo 2018, 2023 i

ii ThinkSystem ST250 Messages and Codes Reference

Chapter 1. Messa es
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/.
Event and alert messa e format
You can use the following content to hel you understand the event and alert message format.
The following information is rovided for each event message.
Event identifier
A string that uniquely identifies the event or class of events. This is a 12 character string in the following
format:
FQXppnnxxxxc
where:
• pp indicates the roduct where the event originate, as follows.
– CM. Chassis Management.
– HM. Hardware manager.
– PM. XClarity Provisioning manger - LXPM (LEPT).
– SF. System Firmware.
– SP. Service Processor.
• nn identifies the com onent or system management where the event originated, as follows:
Components
– AA. Canister/A liance - Contains system com onents not ex ected to be serviced by a
customer.
© Co yright Lenovo 2018, 2023 1

– CA. Cooling - Fans, blowers, mux cards, olicies, chillers/refrigeration, water management units,
water um s, water filtration, air flow sensors, thermal monitors.
– DA. Dis lay - Gra hics ada ters, o anel, monitor/console (including front/back anel, control
anel, LCD anel etc).
– IO. I/O connectivity - PCI/USB hub, bridge, bus, risers, configuration settings, interconnect,
keyboard, mouse, KVM.
– MA. Memory - Includes DIMMs, memory card, configuration settings, memory controller,
redundant modes (mirroring, s are, etc), RAID memory, NVRAM, EPROM.
– PU. Processing - Involves the rocessor, rocessor cards and system board, configuration
settings, and microcode, cache, Trusted Com uting Module, rocessor interconnect (QPI cables).
– PW. Power - Can be ower su lies, VRMs, VRDs, voltage levels, system ower state, olicies,
batteries, AT ower width, TPMD, ower controllers, external ower, Battery Backu Unit (UPS),
PDUs.
– SB. System Board - Main system board, associated risers, system lanar, mid- lanes,
back lanes, interconnects.
– SD. Client Data Storage Device - Flash storage ada ters, drives, cd/dvd drives, SSD, SAS, DASD,
Flash storage, ta e, volumes, remoteCo y, flashCo y, managed Storage Systems.
– SR. Storage RAID - Ada ters, configuration, settings, interconnect, arrays, drive enclosures.
– VD. VPD - Configuration settings, EPROMs, communication.
Systems Management - FSM, PSM, HMC, FDMC UEFI, CMM, IOMC, CCE, PMC, DPSM, SVC,
management of storage, services, IMM, FSP, systems management networking.
– BR. Systems Management - Backu /Restore & Failover (HA).
– BT. System management - Boot, reboot, hard/warm reset, shutdown.
– CL. LEPT Clone.
– CN. Systems Management - Console.
– CP. Systems Management - Config Patterns.
– CR. Systems Management - Core / Virtual A liance.
– DD. Device Driver - AIX, IBM I, Subsystem Device Driver (SDD), IPMI Service.
– DM. Systems Management - Data Management.
– EA. Vendor Events.
– EM. Events Monitoring - LEPT Dash Board.
– EM. Systems Management - Events / Monitoring.
– FC. Systems Management - FlexCat OS/Config de loyment.
– FW. System management - Firmware.
– HA. Hy ervisor - Virtual Com onents, Boots, Crashes, SRIOV, LPARs.
– IF. Interconnect (Fabric) - common, odm, icm, lrim (SWFW major, various minors & functions).
– II. Interconnect (Interfaces) - cim , smis, cli, ma i (SCFG major).
– IM. Interconnect (PCI Manager) - cim (SWFW major, various minors and functions).
– IN. Interconnect (Networking) - bos, ethm, fcf, n iv (FCF major lus SWFW major, various minors &
functions) data network, network settings, orts, security, ada ters, switches, fiber channel,
o tical orts, Ethernet.
– IP. Interconnect (PIE) - tbd.
– IU. Interconnect (Utilities / Infrastructure) - util, infr, serv, isds (IBIS major), remote co y (storage).
– NM. Network Management - LEPT Welcom age.
– NM. Systems Management - Network Management.
– OH. OS/Hy ervisor Interface - Passing of error logs, artition management, services (time, etc).
– OS. LEPT OS De loy.
– OS. OS - Power Linux, AIX IPL, AIX, crash and dum codes, IBM i kernal code, IBM i OS,
management of storage.
– PR. System management - Entity resence.
– RC. Systems Management - Remote Control.
– SD. LEPT Storage Test.
– SE. Systems Management - Security.
– SR. LEPT Raid Setu .
2ThinkSystem ST250 Messages and Codes Reference

– SS. Service & Su ort - LEPT FFDC Collection.
– SS. Systems Management - Service & Su ort.
– TR. Time Reference - RTC, Master clock, drawer clocks, NTP.
– UN. Unknown/any entity.
– UP. LEPT Firmware U date.
– UP. Systems Management - U dates.
– WD. System management - Watchdog.
• xxxx is an incrementing number of the Sub-System events set.
• c identifies the severity, as follows.
– A. Reserved as Immediate Action.
– B. Unknown / No action.
– D. Reserved - Immediate Decision.
– E. Reserved - Eventual Action.
– F. Warning / No Action.
– G. Warning / Deferred Action.
– H. Minor / Deferred Action.
– I. Information / No Action.
– J. Minor / Immediate Action.
– K. Major / Deferred Action.
– L. Major / Immediate Action.
– M. Critical / Immediate Action.
– N. Fatal / Immediate Action.
– W. Reserved - System Wait.
Cha ter 1.Messages 3

4ThinkSystem ST250 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.
• Warnin . 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 Cate ory
Similar events are grou ed together in categories. The alert category is in the following format: se erity -
de ice, where:
© Co yright Lenovo 2018, 2023 5

• se erity is one of the following severity levels:
– Critical. A key com onent in the server is no longer functioning.
– Warnin . The event might rogress to a critical level.
– System. The event is the result of a system error or a configuration change.
• de ice 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 6 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. E ents that automatically notify Support
Event ID Messa e Strin
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])
FQXSPIO0001L The connector [PhysicalConnectorElementName] has encountered a
configuration error.
6ThinkSystem ST250 Messages and Codes Reference

Table 1. E ents that automatically notify Support (continued)
Event ID Messa e Strin
FQXSPIO0011N An Uncorrectable Error has occurred on [SensorElementName].
FQXSPIO0015M Fault in slot [PhysicalConnectorSystemElementName] on system
[Com uterSystemElementName].
FQXSPPW0002L [PowerSu lyElementName] has Failed.
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].
FQXSPSD0006L Array [Com uterSystemElementName] has failed.
FQXSPSS4004I Test Call Home Generated by user [arg1].
FQXSPSS4005I Manual Call Home by user [arg1]: [arg2].
XCC events or anized by severity
The following table lists all XCC events, organized by severity (Information, Error, and Warning).
Table 2. E ents organized by se erity
Event ID Messa e Strin 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
FQXSPBR400CI Management Controller [arg1]: cloning configuration from neighbor
server [arg2] by grou name [arg3] failed to start.
Informational
Cha ter 2.XClarity Controller events 7

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
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
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
FQXSPCR2001I Sensor [SensorElementName] has deasserted the transition to non-
recoverable from a less severe state.
Informational
FQXSPDA2000I The System [Com uterSystemElementName] 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 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
FQXSPDM4005I User [arg1] has generated a new encry tion key air and installed a
self-signed certificate for the TKLM client.
Informational
8ThinkSystem ST250 Messages and Codes Reference

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPDM4006I User [arg1] has generated a new encry tion key and certificate
signing request for the TKLM client.
Informational
FQXSPDM4007I User [arg1] has im orted a signed certificate for the TKLM client from
[arg2].
Informational
FQXSPDM4008I User [arg1] has im orted a server certificate for the TKLM server. Informational
FQXSPDM4009I User [arg1] has [arg2] file [arg3] from [arg4]. Informational
FQXSPDM4010I Inventory data collecting and rocessing com lete for [arg1],
sequence number is [arg2].
Informational
FQXSPDM4011I EKMS server rotocol set by user [arg1]: TKLMServerProtocol=[arg2]
.
Informational
FQXSPDM4012I User [arg1] has changed the olling configuration for the key
management server.: Polling enabled=[arg2] Interval=[arg3]
Informational
FQXSPDM4013I User [arg1] has changed the caching configuration for the key
management server: Caching enabled=[arg2] Interval=[arg3]
Informational
FQXSPEM0003I The Log [RecordLogElementName] has been cleared. Informational
FQXSPEM0004I The Log [RecordLogElementName] is full. Informational
FQXSPEM0005I The Log [RecordLogElementName] is almost full. Informational
FQXSPEM0009I The System [Com uterSystemElementName] has generated an
auxiliary Log Entry in Log [RecordLogElement].
Informational
FQXSPEM4000I The [arg1] on system [arg2] cleared by user [arg3]. Informational
FQXSPEM4001I The [arg1] on system [arg2] is 75% full. Informational
FQXSPEM4002I The [arg1] on system [arg2] is 100% full. Informational
FQXSPEM4003I LED [arg1] state changed to [arg2] by [arg3]. Informational
FQXSPEM4004I SNMP [arg1] enabled by user [arg2] . Informational
FQXSPEM4005I SNMP [arg1] disabled by user [arg2] . Informational
FQXSPEM4006I Alert Configuration Global Event Notification set by user [arg1]:
RetryLimit=[arg2], RetryInterval=[arg3], EntryInterval=[arg4].
Informational
FQXSPEM4007I Alert Reci ient Number [arg1] u dated: Name=[arg2],
DeliveryMethod=[arg3], Address=[arg4], IncludeLog=[arg5], Enabled=
[arg6], EnabledAlerts=[arg7], AllowedFilters=[arg8] by user [arg9] from
[arg10] at IP address [arg11].
Informational
FQXSPEM4008I SNMP Tra s enabled by user [arg1]: EnabledAlerts=[arg2],
AllowedFilters=[arg3] .
Informational
FQXSPEM4009I The UEFI Definitions have been changed. Informational
FQXSPEM4010I UEFI Re orted: [arg1]. Informational
FQXSPEM4011I XCC failed to log revious event [arg1]. Informational
FQXSPEM4012I User [arg1] made system [arg2] Enca sulation lite Mode. Informational
FQXSPEM4013I Battery error was detected by RAID controller. The battery unit needs
re lacement.([arg1],[arg2],[arg3],[arg4],[arg5])
Informational
Cha ter 2.XClarity Controller events 9

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPEM4014I The RAID controller has roblem with the battery. Please contact
technical su ort to resolve this issue.([arg1],[arg2],[arg3],[arg4],
[arg5])
Informational
FQXSPEM4015I The RAID controller detected unrecoverable error. The controller
needs re lacement.([arg1],[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4016I The RAID controller detected one or more roblems. Please contact
technical su ort for additional assistance.([arg1],[arg2],[arg3],[arg4],
[arg5])
Informational
FQXSPEM4017I The RAID controller detected one or more ossible configuration
changes within the subsystem. Please check the drive LED status. If
necessary, contact technical su ort for additional assistance.([arg1],
[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4018I Enclosure/Chassis issue detected with one or more units. Please
check the enclosure/chassis units to re air the roblem.([arg1],[arg2],
[arg3],[arg4],[arg5])
Informational
FQXSPEM4019I Connectivity issue detected with the enclosure/chassis. Please check
your cable configurations to re air the roblem.([arg1],[arg2],[arg3],
[arg4],[arg5])
Informational
FQXSPEM4020I Fan roblem detected with the enclosure/chassis. Please check the
enclosure/chassis unit fan for correct o eration.([arg1],[arg2],[arg3],
[arg4],[arg5])
Informational
FQXSPEM4022I Enclosure/Chassis ower su ly has roblem. Please check the
enclosure/chassis unit ower su ly for correct o eration.([arg1],
[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4023I One or more virtual drive are in abnormal status that may cause
unavailable virtual drive. Please check the event logs and if events are
targeted to the same disk then re lace the drive. If necessary, contact
technical su ort for additional assistance.([arg1],[arg2],[arg3],[arg4],
[arg5])
Informational
FQXSPEM4024I The RAID controller detected one or more ossible configuration
roblem within the subsystem. Please check the event logs and if
events are targeted to the same disk then re lace the drive. If
necessary, contact technical su ort for additional assistance.([arg1],
[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4025I One or more virtual drive have roblem. Please contact technical
su ort to resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4026I Drive error was detected by RAID controller. Please contact technical
su ort to resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4027I Drive error was detected by RAID controller. Please check the event
logs and if events are targeted to the same disk then re lace the drive.
If necessary, contact technical su ort for additional assistance.
([arg1],[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4028I The ort [arg1] of PCIe device [arg2] at [arg3] has link [arg4]. Informational
FQXSPEM4029I All PCIe slots on [arg1] may not be functional based u on your current
CPU o ulation.
Informational
10 ThinkSystem ST250 Messages and Codes Reference

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPEM4030I A scheduled o eration on the RAID controller has encountered an
issue. Refer to RAID Logs under Server Management, Local Storage,
for details.([arg1],[arg2],[arg3],[arg4],[arg5])
Informational
FQXSPEM4031I SSD wear threshold setting is changed from [arg1] to [arg2] by user
[arg3] from [arg4] at IP address [arg5].
Informational
FQXSPEM4032I Acoustic Mode [arg1] has been engaged. Fan s eed limits are in
lace.
Informational
FQXSPEM4033I Acoustic Mode [arg1] has been disengaged to allow adequate
cooling.
Informational
FQXSPEM4036I Dust filter measurement schedule is configured on server [arg1] by
user [arg2] from [arg3] at IP address [arg4].
Informational
FQXSPEM4037I Attem ting to erform scheduled dust filter measurement on server
[arg1].
Informational
FQXSPEM4038I Dust filter measurement schedule is disabled on server [arg1] by user
[arg2] from [arg3] at IP address [arg4].
Informational
FQXSPEM4039I Attem ting to erform an immediate dust filter measurement on
server [arg1] by user [arg2] from [arg3] at IP address [arg4].
Informational
FQXSPEM4041I The SmartNIC in slot [arg1] encountered boot timeout. Informational
FQXSPEM4042I The SmartNIC in slot [arg1] went through a crash dum . Informational
FQXSPEM4044I Dust filter measurement was successfully com leted, no action is
needed.
Informational
FQXSPFC4000I The bare metal connection rocess has been started. Informational
FQXSPFC4001I The bare metal u date a lication re orts a status of [arg1]. Informational
FQXSPFC4002I System running in setu . Informational
FQXSPFC4003I UEFI de loyment boot mode is enabled for NextBoot. Informational
FQXSPFC4004I UEFI de loyment boot mode is enabled for NextAc. Informational
FQXSPFC4005I UEFI de loyment boot mode has been disabled. Informational
FQXSPFW0003I The System [Com uterSystemElementName] encountered firmware
rogress.
Informational
FQXSPFW2000I The System [Com uterSystemElementName] has detected a POST
Error deassertion.
Informational
FQXSPFW2001I The System [Com uterSystemElementName] has detected a POST
Error deassertion.
Informational
FQXSPFW2002I The System [Com uterSystemElementName] has recovered from a
firmware hang.
Informational
FQXSPIO0010I A Correctable Bus Error has occurred on bus [SensorElementName]. Informational
FQXSPIO2001I The connector [PhysicalConnectorElementName] configuration error
has been re aired.
Informational
FQXSPIO2002I The System [Com uterSystemElementName] has detected a POST
Error deassertion.
Informational
Cha ter 2.XClarity Controller events 11

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPIO2003I System [Com uterSystemElementName] has recovered from a
diagnostic interru t.
Informational
FQXSPIO2004I Bus [SensorElementName] has recovered from a bus timeout. Informational
FQXSPIO2006I System [Com uterSystemElementName] has recovered from an NMI. Informational
FQXSPIO2010I Bus [SensorElementName] has recovered from a Correctable Bus
Error.
Informational
FQXSPIO2011I Bus [SensorElementName] has recovered from an Uncorrectable
Error.
Informational
FQXSPIO2013I Bus [SensorElementName] has recovered from a Fatal Bus Error. Informational
FQXSPIO2015I Fault condition removed on slot [PhysicalConnectorElementName] on
system [Com uterSystemElementName].
Informational
FQXSPIO4002I GPU Board Status was recovered by [arg1] of [arg1]. Informational
FQXSPMA0004I [PhysicalMemoryElementName] Disabled on Subsystem
[MemoryElementName].
Informational
FQXSPMA0009I Memory s aring initiated for [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
Informational
FQXSPMA2002I Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName] has deasserted.
Informational
FQXSPMA2004I [PhysicalMemoryElementName] Enabled on Subsystem
[MemoryElementName].
Informational
FQXSPMA2005I The System [Com uterSystemElementName] has detected a POST
Error deassertion.
Informational
FQXSPMA2007I Scrub Failure for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName] has recovered.
Informational
FQXSPMA2008I Uncorrectable error recovery detected for
[PhysicalMemoryElementName] on Subsystem
[MemoryElementName].
Informational
FQXSPMA2010I [PhysicalMemoryElementName] on Subsystem
[MemoryElementName] is no longer Throttled.
Informational
FQXSPMA2011I Memory Logging Limit Removed for [PhysicalMemoryElementName]
on Subsystem [MemoryElementName].
Informational
FQXSPMA2012I An Over-Tem erature Condition has been removed on the
[PhysicalMemoryElementName] on Subsystem
[MemoryElementName].
Informational
FQXSPMA2013I The System [Com uterSystemElementName] has detected a POST
Error deassertion.
Informational
FQXSPMA2015I Redundancy Lost for [RedundancySetElementName] has deasserted. Informational
FQXSPMA2017I Non-redundant:Sufficient Resources from Redundancy Degraded or
Fully Redundant for [RedundancySetElementName] has deasserted.
Informational
FQXSPMA2019I Non-redundant:Insufficient Resources for
[RedundancySetElementName] has deasserted.
Informational
FQXSPNM4000I Management Controller [arg1] Network Initialization Com lete. Informational
12 ThinkSystem ST250 Messages and Codes Reference

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPNM4001I Ethernet Data Rate modified from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4002I Ethernet Du lex setting modified from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4003I Ethernet MTU setting modified from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4004I Ethernet locally administered MAC address modified from [arg1] to
[arg2] by user [arg3].
Informational
FQXSPNM4005I Ethernet interface [arg1] by user [arg2]. Informational
FQXSPNM4006I Hostname set to [arg1] by user [arg2]. Informational
FQXSPNM4007I IP address of network interface modified from [arg1] to [arg2] by user
[arg3].
Informational
FQXSPNM4008I IP subnet mask of network interface modified from [arg1] to [arg2] by
user [arg3].
Informational
FQXSPNM4009I IP address of default gateway modified from [arg1] to [arg2] by user
[arg3].
Informational
FQXSPNM4011I ENET[[arg1]] DHCP-HSTN=[arg2], DN=[arg3], IP@=[arg4], SN=[arg5],
GW@=[arg6], DNS1@=[arg7] .
Informational
FQXSPNM4012I ENET[[arg1]] IP-Cfg:HstName=[arg2], IP@=[arg3] ,NetMsk=[arg4],
GW@=[arg5] .
Informational
FQXSPNM4013I LAN: Ethernet[[arg1]] interface is no longer active. Informational
FQXSPNM4014I LAN: Ethernet[[arg1]] interface is now active. Informational
FQXSPNM4015I DHCP setting changed to [arg1] by user [arg2]. Informational
FQXSPNM4016I Domain name set to [arg1] by user [arg2]. Informational
FQXSPNM4017I Domain Source changed to [arg1] by user [arg2]. Informational
FQXSPNM4018I DDNS setting changed to [arg1] by user [arg2]. Informational
FQXSPNM4019I DDNS registration successful. The domain name is [arg1]. Informational
FQXSPNM4020I IPv6 enabled by user [arg1] . Informational
FQXSPNM4021I IPv6 disabled by user [arg1] . Informational
FQXSPNM4022I IPv6 static IP configuration enabled by user [arg1]. Informational
FQXSPNM4023I IPv6 DHCP enabled by user [arg1]. Informational
FQXSPNM4024I IPv6 stateless auto-configuration enabled by user [arg1]. Informational
FQXSPNM4025I IPv6 static IP configuration disabled by user [arg1]. Informational
FQXSPNM4026I IPv6 DHCP disabled by user [arg1]. Informational
FQXSPNM4027I IPv6 stateless auto-configuration disabled by user [arg1]. Informational
FQXSPNM4028I ENET[[arg1]] IPv6-LinkLocal:HstName=[arg2], IP@=[arg3] ,Pref=[arg4]. Informational
FQXSPNM4029I ENET[[arg1]] IPv6-Static:HstName=[arg2], IP@=[arg3] ,Pref=[arg4],
GW@=[arg5] .
Informational
FQXSPNM4030I ENET[[arg1]] DHCPv6-HSTN=[arg2], DN=[arg3], IP@=[arg4], Pref=
[arg5], DNS1@=[arg5].
Informational
Cha ter 2.XClarity Controller events 13

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPNM4031I IPv6 static address of network interface modified from [arg1] to [arg2]
by user [arg3].
Informational
FQXSPNM4033I Telnet ort number changed from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4034I SSH ort number changed from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4035I Web-HTTP ort number changed from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4036I Web-HTTPS ort number changed from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4037I CIM/XML HTTP ort number changed from [arg1] to [arg2] by user
[arg3].
Informational
FQXSPNM4038I CIM/XML HTTPS ort number changed from [arg1] to [arg2] by user
[arg3].
Informational
FQXSPNM4039I SNMP Agent ort number changed from [arg1] to [arg2] by user
[arg3].
Informational
FQXSPNM4040I SNMP Tra s ort number changed from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4041I Syslog ort number changed from [arg1] to [arg2] by user [arg3]. Informational
FQXSPNM4042I Remote Presence ort number changed from [arg1] to [arg2] by user
[arg3].
Informational
FQXSPNM4043I SMTP Server set by user [arg1] to [arg2]:[arg3]. Informational
FQXSPNM4044I Telnet [arg1] by user [arg2]. Informational
FQXSPNM4045I DNS servers set by user [arg1]: UseAdditionalServers=[arg2],
PreferredDNSty e=[arg3], IPv4Server1=[arg4], IPv4Server2=[arg5],
IPv4Server3=[arg6], IPv6Server1=[arg7], IPv6Server2=[arg8],
IPv6Server3=[arg9].
Informational
FQXSPNM4046I LAN over USB [arg1] by user [arg2]. Informational
FQXSPNM4047I LAN over USB Port Forwarding set by user [arg1]: ExternalPort=
[arg2], USB-LAN ort=[arg3].
Informational
FQXSPNM4048I PXE boot requested by user [arg1]. Informational
FQXSPNM4049I User [arg1] has initiated a TKLM Server Connection Test to check
connectivity to server [arg2].
Informational
FQXSPNM4050I User [arg1] has initiated an SMTP Server Connection Test. Informational
FQXSPNM4051I User [arg1] has set the SMTP Server reverse- ath to [arg2]. Informational
FQXSPNM4052I DHCP s ecified hostname is set to [arg1] by user [arg2]. Informational
FQXSPNM4053I DNS discovery of Lenovo XClarity Administrator has been [arg1] by
user [arg2].
Informational
FQXSPNM4054I The hostname from DHCP is [arg1] by user [arg2]. Informational
FQXSPNM4055I The hostname from DHCP is invalid. Informational
FQXSPNM4056I The NTP server address [arg1] is invalid. Informational
FQXSPNM4057I Security: IP address: [arg1] had [arg2] login failures, it will be blocked
to access for [arg3] minutes.
Informational
14 ThinkSystem ST250 Messages and Codes Reference

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPNM4058I IP address of network interface [arg1] is modified from [arg2] to [arg3]
by user [arg4].
Informational
FQXSPNM4059I IP subnet mask of network interface [arg1] is modified from [arg2] to
[arg3] by user [arg4].
Informational
FQXSPNM4060I IP address of default gateway of network interface [arg1] is modified
from [arg2] to [arg3] by user [arg4].
Informational
FQXSPOS4000I OS Watchdog res onse [arg1] by [arg2] . Informational
FQXSPOS4001I Watchdog [arg1] Screen Ca ture Occurred . Informational
FQXSPOS4004I O erating System status has changed to [arg1]. Informational
FQXSPOS4005I Host Power-On assword changed by user [arg1] from [arg2] at IP
address [arg3].
Informational
FQXSPOS4006I Host Power-On assword cleared by user [arg1] from [arg2] at IP
address [arg3].
Informational
FQXSPOS4007I Host Admin assword changed by user [arg1] from [arg2] at IP
address [arg3].
Informational
FQXSPOS4008I Host Admin assword cleared by user [arg1] from [arg2] at IP address
[arg3].
Informational
FQXSPOS4009I OS Crash Video Ca tured. Informational
FQXSPOS4011I OS failure screen ca ture with hardware error is [arg1] by user [arg2]
from [arg3] at IP address [arg4].
Informational
FQXSPOS4012I POST watchdog Screen Ca ture Occurred. Informational
FQXSPPP4000I Attem ting to [arg1] server [arg2] by user [arg3]. Informational
FQXSPPP4001I Server Power Off Delay set to [arg1] by user [arg2]. Informational
FQXSPPP4002I Server [arg1] scheduled for [arg2] at [arg3] by user [arg4]. Informational
FQXSPPP4003I Server [arg1] scheduled for every [arg2] at [arg3] by user [arg4]. Informational
FQXSPPP4004I Server [arg1] [arg2] cleared by user [arg3]. Informational
FQXSPPP4005I The ower ca value changed from [arg1] watts to [arg2] watts by
user [arg3].
Informational
FQXSPPP4006I The minimum ower ca value changed from [arg1] watts to [arg2]
watts.
Informational
FQXSPPP4007I The maximum ower ca value changed from [arg1] watts to [arg2]
watts.
Informational
FQXSPPP4008I The soft minimum ower ca value changed from [arg1] watts to
[arg2] watts.
Informational
FQXSPPP4011I Power ca ing was activated by user [arg1]. Informational
FQXSPPP4012I Power ca ing was deactivated by user [arg1]. Informational
FQXSPPP4013I Static Power Savings mode has been turned on by user [arg1]. Informational
FQXSPPP4014I Static Power Savings mode has been turned off by user [arg1]. Informational
FQXSPPP4015I Dynamic Power Savings mode has been turned on by user [arg1]. Informational
Cha ter 2.XClarity Controller events 15

Table 2. E ents organized by se erity (continued)
Event ID Messa e Strin Severity
FQXSPPP4016I Dynamic Power Savings mode has been turned off by user [arg1]. Informational
FQXSPPP4017I Power ca and external throttling occurred. Informational
FQXSPPP4019I Power ca throttling occurred. Informational
FQXSPPP4020I The measured ower value has returned below the ower ca value. Informational
FQXSPPP4022I The server was restarted for an unknown reason. Informational
FQXSPPP4023I The server is restarted by chassis control command. Informational
FQXSPPP4024I The server was reset via ush button. Informational
FQXSPPP4025I The server was owered-u via ower ush button. Informational
FQXSPPP4026I The server was restarted when the watchdog ex ired.. Informational
FQXSPPP4027I The server was restarted for OEM reason. Informational
FQXSPPP4028I The server was automatically owered on because the ower restore
olicy is set to always on.
Informational
FQXSPPP4029I The server was automatically owered on because the ower restore
olicy is set to restore revious ower state..
Informational
FQXSPPP4030I The server was reset via Platform Event Filter. Informational
FQXSPPP4031I The server was ower-cycled via Platform Event Filter. Informational
FQXSPPP4032I The server was soft reset. Informational
FQXSPPP4033I The server was owered u via Real Time Clock (scheduled ower
on).
Informational
FQXSPPP4034I The server was owered off for an unknown reason. Informational
FQXSPPP4035I The server was owered off by chassis control command. Informational
FQXSPPP4036I The server was owered off via ush button. Informational
FQXSPPP4037I The server was owered off when the watchdog ex ired. Informational
FQXSPPP4038I The server stayed owered off because the ower restore olicy is set
to always off.
Informational
FQXSPPP4039I The server stayed owered off because the ower restore olicy is set
to restore revious ower state..
Informational
FQXSPPP4040I The server was owered off via Platform Event Filter. Informational
FQXSPPP4041I The server was owered off via Real Time Clock (scheduled ower
off).
Informational
FQXSPPP4042I Management Controller [arg1] reset was initiated due to Power-On-
Reset.
Informational
FQXSPPP4043I Management Controller [arg1] reset was initiated by PRESET. Informational
FQXSPPP4044I Management Controller [arg1] reset was initiated by CMM. Informational
FQXSPPP4045I Management Controller [arg1] reset was initiated by XCC firmware. Informational
FQXSPPP4046I Remote ower ermission is [arg1]. Informational
FQXSPPP4047I Management Controller [arg1] reset was initiated by user [arg2]. Informational
16 ThinkSystem ST250 Messages and Codes Reference