Get Event Record
更新时间： 2026/08/06
在Gitcode上查看源码Get Event Record
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Query alarm information.
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, subcommand = 40h |
| 5 | Lower four bits: request type, 0- current alarm; higher four bits: format, returned information type. 0: simplified information. Currently, only 0 is supported. 1- queries historical events. The four most significant bits indicate the type of returned information. 0: simplified information. Currently, only 0 is supported. |
| 6:7 | Indicates the event index. When multiple events are filtered based on certain conditions, the start number of the events to be queried starts from 0. If the queried event information cannot be contained in a single message, you need to obtain the event information for multiple times. The offset sequence number obtained for the Nth time is the total number of events queried for 0 to N-1 times. |
| 8 | severity: severity level, in the bitmap format. The value is a parameter, and the value is bit3-critical. If the corresponding bit is 0, events of this severity level are not included. If the corresponding bit is 1, events of this severity level are included. 0xFF indicates that no level is specified. |
| 9 | Subject type. The value 0xFF indicates that the subject type is not specified. |
| (10) | This parameter is valid when request type is set to 1. direction: event direction. 1: event generation; 0: event recovery; 0xFF: no direction specified |
| (11:14) | This parameter is valid when request type is set to 1. start time: start timestamp (unit: second). 0xFFFFFFFF indicates that the event starts from the earliest event. |
| (15:18) | This parameter is valid when request type is set to 1. end time: end timestamp (unit: second). 0xFFFFFFFF indicates the current time. |
Response Information
| Response code. | Meaning | Suggestions |
|---|---|---|
| COMP_CODE_SUCCESS 0x00 | Success. No data is to be returned. | Wait for the next round of request initiation. |
| COMP_CODE_BUSY 0xC0 | Failed, but there may be data to be returned. | Re-initiate the request immediately. |
| COMP_CODE_DATA_TRUNCATED 0xC6 | Succeeded, and data is to be returned. | Continue to initiate a request and wait for data to be returned. |
| COMP_CODE_OUTOF_RANGE (0xC9) | Failed. No data is to be returned. | Check the request parameters. |
| Others | Failed | Check the request parameters. |
Command Example
If the request type is 0, query the current alarm information.
Request:
bash
ipmitool raw 0X30 0X94 0XDB 0X07 0X00 0X40 0X00 0x00 0x00 0x04 0xFFResponse:
text
db 07 00 01 00 01 00 01 00 00 28 ff ff ff ff 02
28 01 00 00 00 00