Lenovo ThinkSystem SR675 V3 Manual page 60

Hide thumbs Also See for ThinkSystem SR675 V3:
Table of Contents

Advertisement

The event Log might contain a recent FQXSFMA0011I event denoting detected change in DIMM
population that could be related to this problem.)
2. If no problem is observed on the DIMM connectors or the problem persists, replace the DIMM
identified by LightPath and/or event log entry.
3. If problem recurs on the same DIMM connector, replace the other DIMMs on the same memory
channel.
4. Check Lenovo support site for an applicable service bulletin or firmware update that applies to this
memory error.
5. If problem recurs on the same DIMM connector, inspect connector for damage. If damage found or
problem persists, collect Service Data log.
6. Contact Lenovo Support.
• FQXSPMA0009I: Memory sparing initiated for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName].
This message is for the use case when an implementation has detected that Memory double chip sparing
has been initiated.
Severity: Info
Serviceable: No
Automatically notify Support: No
Alert Category: System - Other
SNMP Trap ID:
CIM Prefix: PLAT CIM ID: 0140
User Action:
Information only; no action is required.
• FQXSPMA0010J: [PhysicalMemoryElementName] on Subsystem [MemoryElementName]
Throttled.
This message is for the use case when an implementation has detected Memory has been Throttled.
Severity: Warning
Serviceable: Yes
Automatically notify Support: No
Alert Category: System - Other
SNMP Trap ID: 22
CIM Prefix: PLAT CIM ID: 0142
User Action:
Complete the following steps:
1. Check the event log of system management module and XClarity Controller for any fan or cooling
related issues.
2. Make sure that the airflow at the front and rear of the chassis is not obstructed and that fillers are in
place,clean, and correctly installed.
3. Make sure that the room temperature is within operating specifications.
4. If the problem persists and there are no other DIMMs with the same indication, replace the DIMM.
• FQXSPMA0011G: Memory Logging Limit Reached for [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Reached.
56
ThinkSystem SR675 V3 Messages and Codes Reference

Advertisement

Table of Contents
loading

This manual is also suitable for:

7d9q7d9r

Table of Contents