Get Blade Configuration
更新时间： 2026/08/06
在Gitcode上查看源码Get Blade Configuration
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 node configurations (for OSCA servers only).
Privilege
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 = 01h |
| 5 | bladeid, 1 based |
| 6 | Blade Configuration Parameter See Table 1. |
| 7 | Read offset, starting from 0. |
| 8 | Length: read length. |
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 | End of list, indicating whether the data reading 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 |
| 6:N | Data. The actually returned data may be less than or equal to the value of Read length. |
Reference
Table 1 Blade Configuration Parameter
| Parameter | Parameter Data | No. (Decimal) | |
|---|---|---|---|
| Presence | read-only | data1:1-Get blade presence status | 1 |
| Spaned Slot | read-only | data1:1 Get Spaned Slot | 2 |
| Health state | read-only | data1:3 Get blade health state 1: minor events count of the blade 2: major events count of the blade 3: critical events count of the blade | 3 |
| Power | read-only | data1:2- Get Power value LS-byte first | 4 |
| CPU Temp | read-only | data1:1-Get Max temperature Value from range [CPU1, CPU2, ... , CPUn] of the blade | 5 |
| Power State | read-only | data1:1 Get blade power state | 6 |
| Chassis Type | read-only | data1:1 Chassis Type of the blade | 7 |
| System Serial Number | read-only | data1:N Blade system serial number | 8 |
| Asset Tag | read-only | data1:N Blade asset tag | 9 |
| Owner Chassis ID | read-write | data2: N Owner Chassis ID (home chassis/cabinet ID) Max 64 Bytes. End by null if less than 64 Bytes | 10 |
| Location ID | read-write | data2:N Location ID (location information), string. Max 64 Bytes. End by null if less than 64 Bytes. | 11 |
| Remote Manage ID | read-write | data2:N Remote Manage ID Used for stateless computing of eSight. Max 64 Bytes. End by null if less than 64 Bytes | 12 |
| Poweron Control String | read-write | data1:N Power On Control String (controlled power-on) Used to power on the BMC in the stateless computing solution of network management software such as eSight. The server is powered on only after the profile is delivered to the BMC. Format: IP address of the control board to be powered on,Port number of the control board to be powered on,List of boards to be powered on under control The power-on board list is a string of a maximum of 64 characters. Each character indicates a board and can only be 0 or 1. 0 indicates that the power-on is not controlled, and 1 indicates that the power-on is controlled. For a single BMC, there is only one character. For example: 192.168.0.2, 1025, 1 Max 255 Bytes. End by null if less than 64 Bytes | 14 |
| System Boot Control | write-only | Controlling the BIOS Startup Phase Used for 9032 power-on configuration. data1:1 indicates the BIOS synchronization startup phase (1 base). | 15 |
| Input Vlotage | read-write | The OSCA rear board needs to monitor the voltage difference before and after the MOSFET. However, the BMC cannot detect the voltage before the MOSFET. Therefore, the SMM needs to deliver the voltage difference. LS-byte first | 16 |
| Fixed Key | write-only | data1:1: Passwords and community names are encrypted using fixed keys. To ensure compatibility, you need to run this command to forcibly encrypt passwords and community names using fixed keys before setting the restoration point. After the BMC is delivered, dynamic keys are used for encryption after startup. 0- fixed working key 1-Dynamically generate the working key. | 17 |
| NetCardChipInfo | read | data1: 1, number of chips (1 currently) data2: 1 indicates the information amount of the first chip (2 at present). data3: 1, length (L) of the port quantity information of the first chip data4: 1, number of ports on the first chip (V) data5: 1, length (L) of the chip model information of the first chip data6: N, model of chip 1 (V) If there are other information, add the corresponding L and V. If there are multiple chips, repeat the data format of the first chip. | 18 |
Command Example
Query the cabinet ID of a node.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN