IBM System x iDataPlex dx360 M4 7912, Руководство по обслуживанию

Страница: 121 / 400

5. (Trained technician only) Remove the affected
microprocessor and check the microprocessor
socket pins for any damaged pins. If a damage is
found, replace the system board.
6. (Trained technician only) Replace the affected
microprocessor.
7. Manually re-enable all affected DIMMs if the server
firmware version is older than UEFI v1.10. If the
server firmware version is UEFI v1.10 or newer,
disconnect and reconnect the server to the power
source and restart the server.
8. (Trained Service technician only) Replace the
affected microprocessor.
806f050c-2004ffff Memory Logging Limit Reached
for [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
(DIMM 4)
Explanation: This message is for the use case when
an implementation has detected that the Memory
Logging Limit has been Reached.
Internal Event: No
Severity: Warning
Alert Category: Warning - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0144
SNMP Trap ID: 43
Automatically notify Support: Yes
User response:
1. Check the IBM support website for an applicable
retain tip or firmware update that applies to this
memory error.
2. Swap the affected DIMMs (as indicated by the error
LEDs on the system board or the event logs) to a
different memory channel or microprocessor.
3. If the problem follows the DIMM, replace the failing
DIMM.
4. (Trained technician only) If the problem occurs on
the same DIMM connector, check the DIMM
connector. If the connector contains any foreign
material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected
microprocessor and check the microprocessor
socket pins for any damaged pins. If a damage is
found, replace the system board.
6. (Trained technician only) Replace the affected
microprocessor.
7. Manually re-enable all affected DIMMs if the server
firmware version is older than UEFI v1.10. If the
server firmware version is UEFI v1.10 or newer,
disconnect and reconnect the server to the power
source and restart the server.
8. (Trained Service technician only) Replace the
affected microprocessor.
806f050c-2005ffff Memory Logging Limit Reached
for [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
(DIMM 5)
Explanation: This message is for the use case when
an implementation has detected that the Memory
Logging Limit has been Reached.
Internal Event: No
Severity: Warning
Alert Category: Warning - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0144
SNMP Trap ID: 43
Automatically notify Support: Yes
User response:
1. Check the IBM support website for an applicable
retain tip or firmware update that applies to this
memory error.
2. Swap the affected DIMMs (as indicated by the error
LEDs on the system board or the event logs) to a
different memory channel or microprocessor.
3. If the problem follows the DIMM, replace the failing
DIMM.
4. (Trained technician only) If the problem occurs on
the same DIMM connector, check the DIMM
connector. If the connector contains any foreign
material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected
microprocessor and check the microprocessor
socket pins for any damaged pins. If a damage is
found, replace the system board.
6. (Trained technician only) Replace the affected
microprocessor.
7. Manually re-enable all affected DIMMs if the server
firmware version is older than UEFI v1.10. If the
server firmware version is UEFI v1.10 or newer,
disconnect and reconnect the server to the power
source and restart the server.
8. (Trained Service technician only) Replace the
affected microprocessor.
806f050c-2006ffff Memory Logging Limit Reached
for [PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
(DIMM 6)
Explanation: This message is for the use case when
an implementation has detected that the Memory
Logging Limit has been Reached.
Internal Event: No
806f050c-2004ffff • 806f050c-2006ffff
Chapter 3. Diagnostics
103