Manageability engine (me) events, 1 me firmware health event, 1 me firmware health event – next steps – Kontron S4600 SEL Troubleshooting User Manual
Page 125: Me firmware health event, Next steps

System Event Log Troubleshooting Guide for EPSD
Platforms Based on Intel
®
Xeon
®
Processor E5 4600/2600/2400/1600/1400 Product Families
Manageability Engine (ME) Events
Revision 1.1
Intel order number G90620-002
115
13. Manageability Engine (ME) Events
The Manageability Engine controls the PECI interface and also contains the Node Manager functionality.
13.1 ME Firmware Health Event
This sensor is used in Platform Event messages to the BMC containing health information including but not limited to firmware
upgrade and application errors.
Table 92: ME Firmware Health Event Sensor Typical Characteristics
Byte
Field
Description
8
9
Generator ID
002Ch or 602Ch
– ME Firmware
11
Sensor Type
DCh = OEM
12
Sensor Number
17h
13
Event Direction and
Event Type
[7] Event direction
0b = Assertion Event
1b = Deassertion Event
[6:0] Event Type = 75h (OEM)
14
Event Data 1
[7:6]
– 10b = OEM code in Event Data 2
[5:4]
– 10b = OEM code in Event Data 3
[3:0]
– Health event type – 0h (Firmware Status)
15
Event Data 2
16
Event Data 3
13.1.1
ME Firmware Health Event – Next Steps
In the following table Event Data 3 is only noted for specific errors.
If the issue continues to be persistent, provide the content of Event Data 3 to Intel support team for interpretation. Event Data 3
codes are in general not documented, because their meaning only provides some clues, varies, and usually needs to be individually
interpreted.