Users Guide

PMem event reporting
When system detects PMem-related event either during runtime or POST, system will log the events in Server System Event
Log(SEL) and Life-Cycle Log(LCL). If an event is detected during boot time, system halts during the POST and user needs to
press F1 to continue the boot process.
NOTE: NVDIMM is frequently used in these messages. The term NVDIMM is generic to several different families of
persistent memory including PMem and not meant to indicate NVDIMM-N modules.
Topics:
• Event message ID encoding
• Events during boot time
Event message ID encoding
The event message IDs are encoded as MEM XYZZ.
● X - Severity
○ 5 = Informational (LC log only)
○ 6 = Warning (LC log and SEL)
○ 7 = Critical (LC log and SEL)
● Y - Version
○ 1 = Initial messages
● ZZ - Recommended customer action
○ 00 = No action
○ 01 = Check config
○ 02 = Reset DIMM
○ 03 = Perform warm reset
○ 04 = Perform cold reset
○ 05 = Perform AC power cycle
○ 06 = Contact customer support if problem persists
○ 07 = Retry operation
○ 08 = Sanitize or Factory Reset
○ 09 = Secure Erase
○ 10 = Update Firmware
○ 14 = Contact customer support
○ 99 = Generic or Unknown event
The Message ID and event message information is provided in the table.
Table 12. Message ID and Event Message
Message ID Event Message Severity
MEM5100 A diagnostic event occurred in the memory device at <location>. The
server has automatically taken corrective action and the device is operating
normally. (Debug Code: <code>).
Info
MEM5101 A diagnostic event occurred in the memory device at <location>. Check the
device and system configuration. (Debug Code: <code>).
Info
MEM5102 A diagnostic event occurred in the memory device at <location>. Reseat
the device. (Debug Code: <code>).
Info
5
PMem event reporting 21