Add SEL Entry
更新时间： 2026/08/06
在Gitcode上查看源码Add SEL Entry
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Adds SEL logs to the BMC.
Privilege
BasicSetting
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | Storage 0Ah |
| CMD | 44h |
| 1:16 | Record Data, 16 bytes. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code. Generic, plus following command specific: 80h=operation not supported for this Record Type 81h=cannot execute command, SEL erase in progress |
| 2:3 | Record ID for added record, LS Byte first. |
Reference
Table 1 SEL Record Formats
| Byte | Field | Description | Fields to be filled in the BIOS |
|---|---|---|---|
| 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. | NO |
| 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 | YES |
| 4:7 | Timestamp | Time when event was logged. LS byte first. | NO |
| 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. | YES |
| 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. | YES |
| 11 | Sensor Type | Sensor Type Code for sensor that generated the event | YES |
| 12 | Sensor # | Number of sensor that generated the event | NO |
| 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 section 42.1, Event/Reading Type Codes. [6:0]-Event Type Code | YES |
| 14 | Event Data 1 | Per Table 29-6, Event Request Message Event Data Field Contents | YES |
| 15 | Event Data 2 | Per Table 29-6, Event Request Message Event Data Field Contents | YES |
| 16 | Event Data 3 | Per Table 29-6, Event Request Message Event Data Field Contents | YES |
NOTE: For the BIOS, set this parameter to NO. For the BIOS, set this parameter to 0.
Command Example
Add SEL logs to the BMC.
Request:
bash
Request:
ipmicmd -k "0f 00 0a 44 0 2 2 16 23 10 01 0 0 3 2 1 0 0 0 0" smi 0
Response:
0f 02 00
Note:
The number of returned logs is related to the number of SEL logs recorded in the environment.