Get VRD Parameter
更新时间： 2026/08/06
在Gitcode上查看源码Get VRD Parameter
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
This interface is used to obtain VRD configuration parameters.
Privilege
ReadOnly
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 92h |
| 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 = 2Dh |
| 5 | VRD parameter domain Table 1 |
| 6:N | Table 1 sub-parameter of the obtained information |
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:N | Table 1 |
Reference
Table 1 VRD parameters
| Overview | parameter selector | parameter data-get | parameter data-set |
|---|---|---|---|
| CPU Core | 0x01 | Request: [6:21]: obtained component mask, expressed by bit, 1: yes 0: no Little-endian byte order. For example, to set the CPU1 parameter (the CPU ID starts from 1), set bit0 of byte6 to 1. To set the CPU2 parameter, set bit1 of byte6 to 1. The rest can be deduced by analogy. [22] Parameter Type: parameter type 1: negative offset of the report scale Response: [5:20] indicates the obtained component mask, expressed by bit, 1: obtained successfully 0: Failed to obtain the information. Little-endian byte order. For example, to set the CPU1 parameter (the CPU ID starts from 1), set bit0 of byte6 to 1. To set the CPU2 parameter, set bit1 of byte6 to 1. The rest can be deduced by analogy. Value of [21:N] 1) Request data whose byte 5 is 1: a. If the value of Byte22 in the request is 1, the parameter length is 1 x Total number of components that are successfully queried. | Request: Bit[6:21]: component mask, expressed by bit. 1: configures a specified domain as the forwarding domain. 0: not specified Little-endian byte order. For example, to set the CPU1 parameter (the CPU ID starts from 1), set bit0 of byte6 to 1. To set the CPU2 parameter, set bit1 of byte6 to 1. The rest can be deduced by analogy. [22] Parameter Type: parameter type 1: negative offset of the report scale 2-3: unavailable 4: gears [23:N] parameter value (1) Byte5 is 1: a. If Byte22 is set to 1, the parameter length is calculated as follows: Parameter length = 1 x Total number of components to be set. NOTE: The parameter value of each component contains one byte, and the value ranges from 0 to 15. b. Byte22=4: The parameter length is 1 byte. NOTE: Different levels correspond to multiple parameter combinations. The specific mapping needs to be confirmed with the BIOS and hardware. For CCPod products, the combination is Iout and IccMax. |
| VRD service life | 0x02 | Request: [6] FRU device ID, which is used to obtain the Fru_id of the VRD service life. [7] Component Type: type of the component whose VRD service life is obtained. 0: mainboard VRD service life 1: VRD service life of the interface card Response: [5:N] Data, actual returned service life, expressed in ASCII format of a character string | Read-only |
| VRD overtemperature protection and alarm switch NOTE: This function is supported only by TS200-2480/2480 Pro. | 0x03 | Request: Command length: 0 Response: Data1: value of the current switch. The options are as follows: 0: disabled 1: enabled | Request: Command length: 1 Data1: indicates the switch value to be set. The options are as follows: 0: disabled 1: enabled |
Command Example
Obtain the VRD service life of the mainboard.
Request:
bash
ipmicmd -k "0f 00 30 92 db 07 00 2d 02 00 00" smi 0Response:
text
0f 31 00 92 00 db 07 00 32 31 2e 32 31 2e 32 32 2e 32 31