IPMI SEL 相关表项详情

更新时间：2025/06/26

在Gitcode上查看源码

修订记录

openUBMC版本号	修订日期	修订人	修订内容
25.06	2025/06/26	pengqiang-gs	初稿，新增

SEL Event Records

Byte	Field	Description
1:2	Record ID	ID used for SEL Record access. The Record ID values 0000h and FFFFh have special meaning in the Event Access commands and must not be used as Record ID values for stored SEL Event Records.
3	Record Type	[7:0] - Record Type 02h = system event record C0h-DFh = OEM timestamped, bytes 8-16 OEM defined E0h-FFh = OEM non-timestamped, bytes 4-16 OEM defined
4:7	Timestamp	Time when event was logged. LS byte first.
8:9	Generator ID	RqSA & LUN if event was generated from IPMB. Software ID if event was generated from system software. Byte 1 [7:1] - 7-bit I2C . Slave Address, or 7-bit system software ID [0] 0b = ID is IPMB Slave Address 1b = system software ID Byte 2 [7:4] - Channel number. Channel that event message was received over. 0h if the event message was received via the system interface, primary IPMB, or internally generated by the BMC. (New for IPMI v1.5. These bits were reserved in IPMI v1.0) [3:2] - reserved. Write as 00b. [1:0] - IPMB device LUN if byte 1 holds Slave Address. 00b otherwise.
10	EvM Rev	Event Message format version (=04h for events in this specification, 03h for IPMI v1.0 Event Messages.) Note: the BMC must accept Platform Event request messages that are in IPMI v1.0 format (EvMRev=03h) and log them as IPMI v1.5 / v2.0 Records by setting the EvMRev field to 04h and setting the Channel Number in the Generator ID field appropriately for the channel that the event was received from.
11	Sensor Type	Sensor Type Code for sensor that generated the event
12	Sensor #	Number of sensor that generated the event
13	Event Dir \| Event Type	Event Dir [7] 0b = Assertion event. 1b = Deassertion event. Event Type Type of trigger for the event, e.g. critical threshold going high, state asserted, etc. Also indicates class of the event. E.g. discrete, threshold, or OEM. The Event Type field is encoded using the Event/Reading Type Code. See Event/Reading Type Codes. [6:0] -Event Type Code
14	Event Data 1	Per Event Request Message Event Data Field Contents
15	Event Data 2	Per Event Request Message Event Data Field Contents
16	Event Data 3	Per Event Request Message Event Data Field Contents

Event Request Message Fields

Field	Description
Generator ID	This field identifies the device that has generated the Event Message. This is the 7-bit Requester’s Slave Address (RqSA) and 2-bit Requester’s LUN (RqLUN) if the message was received from the IPMB, or the 7-bit System Software ID if the message was received from system software.
EvMRev	One byte. Event Message Revision. This field is used to identify different revisions of the Event Message format. The revision number shall be 04h for Event Messages that comply with the format given in this specification. IPMI v1.0 messages use 03h. It is recommended that software be able to interpret both versions.
Sensor Type	One byte. Indicates the event class or type of sensor that generated the Event Message. The Sensor Type Codes are specified in Sensor Type Codes.
Sensor #	One byte. A unique number (within a given sensor device) representing the ‘sensor’ within the management controller that generated the Event Message. Sensor numbers are used for both identification and access of sensor information, such as getting and setting sensor thresholds.
Event Dir	1-bit. Indicates the event transition direction. (0 = Assertion Event, 1 = Deassertion Event)
Event Type	7-bits. This field indicates the type of threshold crossing or state transition (trigger) that produced the event. This is encoded using the Event/Reading Type Code.
Event Data	One to three Bytes. The remainder of the Event Message data according to the class of the Event Type for the sensor (threshold, discrete, or OEM). The contents and format of this field is specified in Event Request Message Event Data Field Contents, below.

Event Request Message Event Data Field Content

Sensor class	Event Data
threshold	Event Data 1 [7:6] 00b = unspecified byte 2 01b = trigger reading in byte 2 10b = OEM code in byte 2 11b = sensor-specific event extension code in byte 2 [5:4] 00b = unspecified byte 3 01b = trigger threshold value in byte 3 10b = OEM code in byte 3 11b = sensor-specific event extension code in byte 3 [3:0] - Offset from Event/Reading Code for threshold event. Event Data 2 reading that triggered event, FFh or not present if unspecified. Event Data 3 threshold value that triggered event, FFh or not present if unspecified. If present, byte 2 must be present.
discrete	Event Data 1 [7:6] 00b = unspecified byte 2 01b = previous state and/or severity in byte 2 10b = OEM code in byte 2 11b = sensor-specific event extension code in byte 2 [5:4] 00b = unspecified byte 3 01b = reserved 10b = OEM code in byte 3 11b = sensor-specific event extension code in byte 3 [3:0] - Offset from Event/Reading Code for discrete event state Event Data 2 Optional OEM code or severity / previous state fields. May be not present if byte is unspecified AND Event Data 3 is also not present. [7:4] - Optional offset from ‘Severity’ Event/Reading Code. (0Fh if unspecified). [3:0] - Optional offset from Event/Reading Type Code for previous discrete event state. (0Fh if unspecified.) Event Data 3 Optional OEM code. FFh or not present if unspecified.
OEM	Event Data 1 [7:6] 00b = unspecified byte 2 01b = previous state and/or severity in byte 2 10b = OEM code in byte 2 11b = reserved [5:4] - 00b = unspecified byte 3 01b = reserved 10b = OEM code in byte 3 11b = reserved [3:0] - Offset from Event/Reading Type Code Event Data 2 Optional OEM code or severity / previous state fields. May be not present if byte is unspecified AND Event Data 3 is also not present. [7:4] - Optional OEM code bits or offset from ‘Severity’ Event/Reading Type Code. (0Fh if unspecified). [3:0] - Optional OEM code or offset from Event/Reading Type Code for previous event state. (0Fh if unspecified). Event Data 3 Optional OEM code. FFh or not present if unspecified.