Get Event Entry
更新时间： 2026/08/06
在Gitcode上查看源码Get Event Entry
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
This command is used to query events.
Privilege
ReadOnly
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 94h |
| 1:3 | Manufacturer ID, LS Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h. |
| 4 | Sub command, sub command = 37h |
| 5 | Event type 0 indicates the abnormal events that are not cleared, excluding the equipment/maintenance events. In this case, data5 is displayed as 1 when data5 is 0. 1: abnormal event that is not recovered. It is mainly used for equipment. In this case, data5 is 0 and data5 is 1. 2: all events recorded locally. |
| 6 | Serverity: indicates the severity level, 1: minor or above 2: major or above 3: critical |
| 7 | Format 0- English event format 1- multi-language ID format, which is converted by the invoker (not implemented currently) |
| 8:09 | Event Record ID, LS Byte first 0000h=Get first event FFFFh=Get last event |
| 10:11 | Read offset, starting from 0. |
| 12 | Read Length: indicates the length of the data to be read. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code |
| 2:4 | Manufacturer ID, LS Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h. |
| 5:6 | Next Record ID, LS Byte first If FFFFh is returned, the record is the last one. |
| 7 | End of List, indicating whether the current data is complete. Long data may need to be read multiple times. This field is used to check whether data is completely read. [7:1]: reserved [0]: End of list 0=last data 1=middle data |
| 8 | Reserved. The value is 0. |
| 9:N | #Event information data1:4-NewEventId, in little endian format. The new event code is unique and can be used for event control. data5:4-OldEventId, little endian. This field is provided if an old event code exists. Otherwise, this field is set to 0. However, the old event code is not unique and is provided only for compatibility. data9:1: severity level 0-Normal 1-Minor 2-Majo 3-Critical data10:1: event triggering mode 1- normal monitoring 2- analog 3- Manually trigger a recovery event. 16- The re-report command is received. 18- simulation + re-reporting. The meaning is the same as the value of the Mode attribute of the event monitoring object. data11:20: time and date, in the format of YYYY-MM-DD HH:MM:SS data31:N - Event content When the format type is 0, this parameter indicates the event description in English. When the format type is 1: Format 1: lang_xxx_str=[Event description] [0xba] Dynamic data 1[0xba] Dynamic data 2[0xba] Dynamic data 3[0xba] Dynamic data 4 Format 2: lang_xxx_str[0xba] dynamic data 1[0xba] dynamic data 2[0xba] dynamic data 3[0xba] dynamic data 4 Each piece of dynamic data has three formats: lang_xxx_str, lang_xxx_str=xxxxx, or xxxxx. NOTE: The number of dynamic data N is optional. The N values are separated by invisible characters 0xba. A maximum of 10 dynamic data records can be reserved. The returned data may be less than or equal to the read length. |
Command Example
Query events.
Request:
bash
ipmicmd -k "0f 00 30 94 db 07 00 37 00 02 00 00 00 00 00 40" smi 0Response:
text
0f db 07 00 02 00 00 00 0d 00 00 03 ff ff 03 08 02 20 31 39 37 30 2d 30 31 2d 30 31 20 30 30 3a 30 31 3a 32 30 00 54 68 65 20 41 43 2f 44 43 20 69 6e 70 75 74 20 6f 66 20 50 53 55 20 33 20 69 73 20 6c 6f 73 74 20 6f