Report Component Faults
更新时间： 2026/08/06
在Gitcode上查看源码Report Component Faults
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Receives iME fault error reports.
Privilege
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 98h |
| 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 =05h |
| 5 | Component Status 0: FRU_STATUS_ASSERT 1: FRU_STATUS_DEASSERT |
| 6 | Component type: For details about the value, see the component type definition. |
| 7 | Number of the faulty frame (bit 7 and bit8 are reserved). The value starts from 0. |
| 8:9 | Number of the faulty component (starting from 0) |
| 10 | Indicates the number of faulty master status registers. bit0: Indicates whether the last frame is received. This parameter is used to determine whether the message is received completely. Bits 1-7: number of errors in the main status register |
| 11:M | Fault register information: The information is reported based on the number of 10 fault registers. |
| M+1:N | Module dump register information: All register information except the faulty register information is reported in sequence. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code d6- indicates that the command is not registered with the BMC and is not supported. |
| 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. |
Command Example
Receive an iME fault error report.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN