Platform Event Message
更新时间： 2026/08/06
在Gitcode上查看源码Platform Event Message
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2026/08/06 | Initial draft: add command details |
Basic Information
Function Description
Platform event message (system interface).
Privilege
BasicSetting
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | S/E 04h |
| CMD | 02h |
| 1 | Generator ID.7-bit System Software ID. This field identifies the device that has generated the Event Message. |
| 2 | 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. |
| 3 | Sensor Type. Indicates the event class or type of sensor that generated the Event Message. |
| 4 | Sensor #.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. |
| 5 | Event Dir | Event Type [7]:Event Dir Indicates the event transition direction. (0=Assertion Event, 1=Deassertion Event) [6:0]:Event Type 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. |
| For Sensor Class=threshold | |
| 6:8 | 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. |
| For Sensor Class=discrete | |
| 6:8 | 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 [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. |
| For Sensor Class=OEM | |
| 6:8 | Event Data 1 [7:6]-00b=unspecified in 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 [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 or unspecified. |
Response Information
Command Example
Platform event message (system interface).
Request:
bash
ipmicmd -k "0f 00 04 02 28 03 01 01 00 00 00 00" smi 0Response:
text
0f