Set Rack Info
更新时间： 2026/08/06
在Gitcode上查看源码Set Rack Info
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Setting Cabinet Configuration Parameters
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 = 0x6Bh |
| 5:6 | Parameter Selector, LS Byte first. For details, see Table 1. |
| 7 | [7:1]: reserved [0]: cascading flag 0: last data 1: middle data |
| 8:9 | Write Offset Offset of the data to be written. The value starts from 0. If the data is long and needs to be written for multiple times, the data must be written from the beginning to the end in sequence. |
| 10 | Length Length of the written data |
| 11:N | Parameter data. For details, see Table 1. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code 80h= parameter not supported. 81h= attempt to set the 'set in progress' value (in parameter #0) when not in the 'set complete' state. 82h=attempt to write read-only parameter |
| 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. |
Reference
Table 1 Configuration parameters of the cabinet
| Overview | parameter selector | parameter data-get | parameter data-set |
|---|---|---|---|
| Template: function description and application scenario | 0xMMNN | Request: Read Offset: 0x0000 Length: 1 Response: End of List: 0 Data: 0: function 0 1: function 1 | Request: Write Offset: 0x0000 Length: 1 Data: 0: function 0 1: function 1 |
| Whether to enable multiple external network port groups | 0x0100 | Request: Read Offset: 0x0000 Length: 1 Response: Data: 0: disabled 1: yes | Request: Write Offset: 0x0000 Length: 1 Data: 0: disabled 1: yes |
| Customize the old and new leakage detection solutions. | 0x0200 | Request: Read Offset: 0x0000 Length: 1 Data: 0: old leakage detection: photoelectric and float leakage detection 1. New liquid leakage detection: water leakage detection | Request: Write Offset: 0x0000 Length: 1 Data: 0: Customized old liquid leakage detection solution - liquid detection 1. Customized new leakage detection solution - rope leakage detection solution |
| Is the customized liquid cooling door/manifold supported? | 0x0300 | Read Offset: 0x01: liquid cooling door 0x02 : manifold Length : 1 Data: 0x00: no 0x01: supported | Write Offset: 0x0000 Length: 2 Data: Byte0: 0x01: liquid cooling door 0x02 Manifold Byte1: 0x00: not supported 0x01: supported |
| Customizing the SuperPodLabel Attribute | 0x0004 | Read Offset: 0x0000 Length : 8 Data: Byte1:4 SuperPodId Byte5:6 ServerIndex Byte7:8 SuperPodSize | Write Offset: 0x0000 Data: Byte0: 0x00: All attributes are customized. length: 9 0x01 SuperPodId length: 5 0x02 ServerIndex length: 3 0x03 SuperPodSize length: 3 |
| Supernode mode | 0x0005 | Request: Read Offset: 0x0000 Length: 1 Response: End Of List: 0 Data: supernode mode value 0: false, non-supernode mode1: true (supernode mode) | Request: End Of List: 0, 1 byte Write Offset: 0x0000, 2 bytes Length: length of the data to be written, 1 byte Data: written data, which is set in supernode mode. 0: false, non-supernode mode1: true (supernode mode) Response: |
| Customized Liquid-Cooled Door Temperature Sensor | 0x0006 | Request: Read Offset:0x0000 Length : 1 Response: data: installation status of the liquid-cooled door temperature sensor 0x01: supported 0x00: not supported | Request: Write Offset: 0x0000 Length: 1 Data: written data, indicating the presence status of the liquid-cooled door temperature sensor 0x01: supported 0x00: not supported |
| Power supply mode of the customized cabinet | 0x0007 | Request: Read Offset: 0x0000 Length: 1 Response: Data: Byte[1]: 0: The main circuit supplies power (all power supplies are powered by the main circuit). 1: standby power supply (All power supplies are powered by standby power supplies.) 2: half-cross redundant power supply (power supplies 1 to 6 use the active power supply, and power supplies 7 to 12 use the standby power supply) 3: quarter-cross redundant power supply (Power supplies 1 to 3 use the active power supply, power supplies 4 to 6 use the standby power supply, power supplies 7 to 9 use the active power supply, and power supplies 10 to 12 use the standby power supply.) 4: Redundant power supply for odd and even cross-connect boards (The power supply in an odd-numbered slot uses the active power supply, and the power supply in an even-numbered slot uses the standby power supply.) | Request: Write Offset: 0x0000 Length: 1 Data: Byte[1]: 0: The main circuit supplies power (all power supplies are powered by the main circuit). 1: standby power supply (All power supplies are powered by standby power supplies.) 2: half-cross redundant power supply (power supplies 1 to 6 use the active power supply, and power supplies 7 to 12 use the standby power supply) 3: quarter-cross redundant power supply (Power supplies 1 to 3 use the active power supply, power supplies 4 to 6 use the standby power supply, power supplies 7 to 9 use the active power supply, and power supplies 10 to 12 use the standby power supply.) 4: Redundant power supply for odd and even cross-connect boards (The power supply in an odd-numbered slot uses the active power supply, and the power supply in an even-numbered slot uses the standby power supply.) Note: 1. The cross-connect redundancy mode and N+R mode are mutually exclusive. Before switching the cross-connect redundancy mode, disable the N+R mode. |
| Customizing the SuperPodLabelExpansion Attribute | 0x0008 | Request: Read Offset: 0x0000 Length - total length of the obtained supernode information Response: Data0: number of queried supernode attributes Data1: type of supernode attribute 1. For details, see Table 2 Supernode configuration attributes. Data2: length (N) of supernode attribute 1. For details, see Table 2 Supernode information configuration attributes. Data3:3+N - value of supernode attribute 1 When multiple supernode attributes are queried, the Type Length Value structure is used. The format is the same as that of Data3:3+N. | Request: Write Offset:0x0000 Length - Set the total length of the supernode information. Parameter Data0: indicates the number of supernode attributes. Parameter Data1 - Length of supernode attribute 1. For details, see Table 2 List of supernode attributes. For example, to set TopologyType, set Parameter Data1 to 0x01. Parameter Data2: type number of supernode attribute 1. For details, see Table 2 List of supernode attributes. For example, to set TopologyType, set Parameter Data2 to 0x00. Parameter Data3:3+N - Value of supernode attribute 1. For example, to set TopologyType, Parameter Data3 can be 0x01. When setting multiple supernode attributes, use the Type Length Value structure. The format is the same as that of Parameter Data3:3+N. |
Table 2 List of supernode configuration attributes.
| Attribute Name | Type | Length |
|---|---|---|
| TopologyType | 0x00 | 1 |
| UBMDeployMode | 0x04 | 1 |
| ChassisId | 0x05 | 2 |
| IsUBFabricMode | 0x06 | 1 |
| IsUBControlNode | 0x07 | 1 |
| LogicalSlotNumber | 0x08 | 1 |
Command Example
xxx.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN