Set BMC Configuration
更新时间： 2026/08/06
在Gitcode上查看源码Set BMC Configuration
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
| 26.06 | 2026/05/09 | Added parameter: BMC boot status (0x4F) |
Basic Information
Function Description
Setting BMC Parameters
Privilege
ReadOnly
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 93h |
| 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=5ah |
| 5:6 | Parameter selector. For details, see Table 1. Low-order bytes are placed before low-order bytes. |
| 7:8 | Data length. The least significant byte is placed before the least significant byte. |
| 9:N | Parameter data. For details, see Table 1. |
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 | Data. For details, see Table 1. |
Reference
Table 1 BMC configuration parameters
| Overview | parameter selector | parameter data-get | parameter data-set |
|---|---|---|---|
| Power-off policy for a liquid-cooled server with electrolyte leakage | 0x1 | Request: command length:1 data1:0 Response: data1: 0-manual power off after leakage 1-auto power off after leakage | Request: command length:1 data1: 0 : manual power off after leakage 1 : auto power off after leakage |
| Local O&M IPv4 address of the dedicated network port | 0x2 | Request: command length:1 data1:0 Response: Data1-n: hexadecimal representation of the IPv4 address string | Request: command length:n Data1-n: hexadecimal representation of the IPv4 address string |
| Local O&M subnet mask of the dedicated network port | 0x3 | Request: command length:1 data1:0 Response: data1 to n: hexadecimal subnet mask character string | Request: command length:n data1 to n: hexadecimal subnet mask character string |
| The PSU works in n+r mode. | 0x4 | Request: command length:1 data1:0 Response: data1: 0-normal and redundancy is disabled 1-normal and redundancy is enabled | Request: command length:1 data1: 0 : normal and redundancy is disabled 1 : normal and redundancy is enabled |
| Number of NTP servers supported by the BMC | 0x5 | Request: command length:1 data1:0 Response: data1: 3-The BMC supports three NTP servers. 6-The BMC supports six NTP servers. | Request: command length:1 data1: 3: The BMC supports three NTP servers. 6: indicates that the BMC supports six NTP servers. Other values: invalid |
| NTP server IP address of the BMC | 0x6 | Request: command length:1 data1: 0=ntp preferred server 1=ntp alternative server 2=First NTP extra server 3=Second NTP extra server 4=Third NTP extra server 5=Fourth NTP extra server Response: command length:n Data1-n: ipv4, ipv6, domain name address string | Request: command length:n data1: 0: updates the preferred NTP server. 1: Update the NTP alternative server. 2: Update the first NTP extra server. 3: Update the second NTP extra server. 4: Update the third NTP extra server. 5: Update the fourth NTP extra server. data2 (currently not used, reserved) [7:1]: reserved [0]: cascading flag 0: last frame of data 1: There is data following. data3 (currently not used, reserved) offset: offset length data4~n: IPv4 or IPv6 domain name address character string. The value 0.0.0.0 indicates that the extended NTP service address is deleted. |
| Hotplug surprise state | 0x7 | Request: command length:0 Response: data1: 0-hotplug surprise is disabled 1-hotplug surprise is enabled | Request: command length:1 data1: 0 : hotplug surprise is disabled 1 : hotplug surprise is enabled |
| Power supply status control | 0x8 | Not supported | Request: command length:1 data1-2: The low-order byte is placed before the low-order byte. For details, see "Component Type Definition." data3: reserved. The default value is 0. data4: slot ID data5: power supply ID 1: main power supply Other values: reserved data6: power supply status 0 : power off 1 : power on Other values: reserved |
| Indicator status control | 0x9 | Not supported | Request: command length:1 data1-2: The low byte is placed before the high byte. For details, see the component type definition. data3: reserved. The default value is 0. data4: slot ID data5: indicator ID 2: health indicator 4: UID indicator Others: reserved for extension data6: control status 0: steady off 1: steady on Others: reserved for extension |
| Shield the power button control. | 0xa | Request: command length:2 data1:fruid data2: 0: short press function 1: All functions of the button, including short press and long press (unshielded by default). The IPMI interface is not delivered. Response: data1: 0: not masked 1: masked | Request: command length:3 data1:fruid data2: 0: short press function 1: All functions of the button, including pressing and holding down the button (configuration reset is lost) - The IPMI interface is not delivered. data3: 0: unmasked 1: masked |
| [Configuration description] There are two types of for the shielding function, and the corresponding CPLD has two interfaces. Method 1: Shield the power button on the panel, including pressing and holding the button. After the alarm is masked, pressing and holding the button on the panel becomes invalid. The power-on and power-off commands delivered by the software are not affected. Method 2: Only the power button on the panel is shielded. After the shielding, the short press on the panel becomes invalid, but the long press function on the panel is not affected. The power-on and power-off commands delivered by the software are not affected. Background: 202009228576 1. If you accidentally touch the power button of the server, the server will be shut down and services will be interrupted. However, if you enable the function of shielding the power button on the panel, the server cannot be shut down by pressing and holding the power button. You have to remove the power cable to shut down the server. However, there are too many servers, and incorrect cables may be removed, this brings great inconvenience to users. 2. After the power anti-touch function is enabled for servers of other brands, touching the power button does not shut down the server. However, pressing and holding the power button can shut down the server. | |||
| Specifies whether the IRM heartbeat function is supported. | 0x0b | Request: command length:0 Response: data1: 0-irm heartbeat feature is not supported 1-irm heartbeat feature is supported | Not supported |
| Slot number of the PCIe NIC connected to the PCIe ncsi cable | 0x0c | Request: command length:0 Response: data1: 0xff: unknown 0 to 254: slot number of the PCIe NIC connected to the PCIe ncsi cable | Not supported |
| Expected number of components to be configured | 0x0d | Request: command length:1 data1: device type, which is the same as the type ID in the Component Type Customization sheet. Response: data1: Expected number of components to be configured | Request: command length:2 data1: device type, which is the same as that in the Component Type Customization sheet. data2: Expected number of components to be configured |
| Web page javakvm support status | 0x0e | Request: command length:1 data1:0 Response: data1: 0-java kvm is invisible 1-java kvm is visible | Request: command length:1 data1: 0-java kvm is invisible 1-java kvm is visible |
| BMC reset reason | 0x0f | Request: command length:0 Response: data1: BMC reset reason code: 0=powerup reset 1=outer watchdog or button reset 2=inner watchdog reset | Not supported |
| snmp sysname | 0x10 | Request: command length:0 Response: data1~n: indicates the ASCII representation of the SNMP sysname character string. | Request: command length:n Data1-n: indicates the character string of the SNMP sysname to be set in ASCII format. |
| USB management enable status | 0x11 | Request: command length:0 Response: data1: 0-usb management service is disabled 1-usb management service is enabled | Request: command length:1 data1: 0-usb management service is disabled 1-usb management service is enabled |
| Wireless management status | 0x12 | Request: command length:0 Response: data1: 0-wireless service is disabled 1-wireless service is enabled | Request: command length:1 data1: 0-wireless service is disabled 1-wireless service is enabled |
| Wireless management timeout | 0x13 | Request: command length:0 Response: data1: 00h-never timeout 01h~3ch-inactivity timeout (minutes) | Request: command length:1 data1: 00h-never timeout 01h~3ch-inactivity timeout (minutes) |
| Wi-Fi power-on status | 0x14 | Request: command length:0 Response: data1: 0-wifi is power off 1-wifi is power on | na |
| Number of currently connected Wi-Fi users | 0x15 | Request: command length:0 Response: data1: wifi connection num | na |
| Wi-Fi authentication type | 0x16 | Request: command length:0 Response: data1: 0-no auth 1-wpa-psk 2-wpa2-psk 3-wpa-psk/wpa2-psk | Request: command length:1 data1: 0-no auth 1-wpa-psk 2-wpa2-psk 3-wpa-psk/wpa2-psk |
| Wi-Fi authentication encryption algorithm | 0x17 | Request: command length:0 Response: data1: 0-aes 1-tkip | Request: command length:1 data1: 0-aes 1-tkip |
| Wi-Fi authentication password setting | 0x18 | na | Request: command length:8~63 data1-n(8<=n<=63): wifi password |
| Wi-Fi authentication password verification | 0x19 | na | Request: command length:8~63 data1-n(8<=n<=63): wifi password |
| vlan config | 0x1a | Request: command length:0 Response: data1: config count data2~5: config 1 data2: port type 0-ncsi 1-dedicated data3: vlan id enable. 0-disabled 1-enabled data4: msb vlan id. 00h if vlan is disabled [7:4]-reserved [3:0]-most significant four bits of the vlan id. data5: lsb vlan id. 00h if vlan is disabled [7:0]-least significant 8-bits of the vlan id. data6~9: config 2 ...... | Request: command length:4 data1~4: config 1 data1: port type 0-ncsi 1-dedicated data2: vlan id enable. 0-disabled 1-enabled data3: msb vlan id. 00h if vlan is disabled. [7:4]-reserved [3:0]-most significant four bits of the vlan id. data4: lsb vlan id. 00h if vlan is disabled. [7:0]-least significant 8-bits of the vlan id. |
| Power supply configuration of the USB port | 0x1b | Request: command length:0 Response: data1:usb ports num data2-n(2<=n<=255): usb power status 0-power off 1-power on | Request: command length:n data1:usb ports num data2-n(n=data1+1):usb power status 0-power off 1-power on |
| BIOS PXE startup timeout interval | 0x1c | na | Request: command length:3 data1: configuration item 0-pxetimeoutretrycontrol data2:3:(lsb) When data1 is 0: 0: disabled 1: timeoutretrycount1 (4s) 2: timeoutretrycount2 (12s) 3: timeoutretrycount3 (28s) 4: timeoutretrycount4 (60s) |
| PSU FRU Information Customization | 0x1d | Request: command length:1 data1: configuration item 0-product version Response: data1: configuration value Request data1=0 0: hardware version 1: software version (firmware version) indicates the PSU software version (firmware version). | Request: command length:2 data1: configuration item 0-product version data2: configuration value When data1 is 0: 0: hardware version 1: software version (firmware version), power supply software version (firmware version) |
| System Management Software Name (ibma) | 0x1e | Request: command length:0 Response: command length:n data1: length of smsname Data2–n: ASCII representation of the smsname character string | Request: command length:n data1: length of smsname data2~n: ASCII representation of the smsname name string |
| Default fan speed ratio in the AC power-on scenario | 0x1f | Request: command length:0 Response: data1: fan level 50-100: corresponding rate ratio | Request: command length:1 data1: fan level 50-100: corresponding rate ratio |
| Minimum number of power supplies required for the device to work properly | 0x20 | Request: command length:0 Response: command length:1 data1: minimum number of power supplies required for the entire system to work properly | Request: command length:1 data1: minimum number of power supplies required for the entire system to work properly |
| Customization of customer configuration models | 0x21 | Request: command length:0 Response: command length:n data1: configuration value length Configure the length of the model value. data2~n: configuration value Customized configuration model value | Request: command length:n data1~n: configuration value Customized configuration model value |
| Customization of customer version information | 0x22 | Request: command length:0 Response: command length:n data1: configuration value length Length of the customized version information. data2~n: configuration value Customized version information. | Request: command length:n data1~n: configuration value Customized version information. |
| Customizing the Redfish OEM Vendor Name | 0x23 | Request: command length:0 Response: Data1–n: ASCII representation of the customized vendor character string | Request: command length:n Data1–n: ASCII representation of the customized vendor character string to be set |
| Control the switch for collecting device information from SPs. | 0x24 | Request: command length:0 Response: data1: 0- The function is disabled. 1- The function is enabled. | Request: command length:1 data1: 0- The function is disabled. 1- The function is enabled. |
| Service life of the electronic insurance policy | 0x25 | Request: command length:0 Response: data1: Service life of the electronic insurance policy (unit: month) | Request: command length:1 data1: service life of the electronic insurance policy to be set (unit: month) |
| Enabling status of a dedicated alarm item. | 0x26 | Request: command length:1 data1: customalarm type, which indicates the serial number of the alarm type to be customized. NOTE: Alarms related to cabinet management can be customized. A maximum of 32 types of alarms are supported. Currently, the following types of alarms are supported: 1: The link of the 10GE network port on the RM210 management module is down. 2: rm210 management board sensor cable offline alarm 3: The leakage detection card of the fusionpod node is not in position. 4: A linkdown alarm is generated on the GE port of port 2. Response: command length:1 data1: customalarm status, indicating whether to enable or disable the customized alarm function. | Request: command length:2 data1: customalarm type, which indicates the serial number of the alarm type to be customized. For details, see the remarks on the right. data2: customalarm status, indicating whether to enable or disable the customized alarm function. |
| UUID Persistence Mode Configuration | 0x27 | Request: command length:1 data1: 0- reset persistency 1- power-off persistence NOTE: Two internal variables are used to store the UUID. One is reset persistence, and the other is power-off persistence. A switchover switch is configured to control which attribute is used as the final UUID. | Request: command length:1 data1: 0- reset persistency 1- power-off persistence |
| Chassis power capping status | 0x28 | Request: command length:0 Response: data[1]: power capping status 0: Inactive 1- activated data2: whether power capping is successful (valid only when data1 is 1) 0: success 1: failure data3: number of nodes (n) Data4-data(4+n-1): indicates whether the cap values of nodes 1 to n have been manually configured. 0- not configured 1- configured | na |
| ID of the node to which the left mounting ear is cut | 0x29 | Request: command length:0 Response: data1: indicates the slot ID of the node where the left mounting ear resides. The value ranges from 1 to 4. | na |
| H2P key verification result | 0x2a | Request: command length:0 Response: command length:1 data1:return value 0: The H2P key is verified successfully. 1- Failed to obtain the H2P key information. 2: The H2P key information fails to be verified. | na |
| efuse type | 0x2b | Request: command length:0 Response: command length:1 data1:return value bit0: indicates whether to support partners. 0: no; 1: yes. bit1: whether the TCM mode eFUSE exists. 0: no; 1: yes. | na |
| Enable status of secure boot | 0x2c | Request: command length:0 Response: command length:1 data1:return value 0- Secure boot is disabled. 1- Enable secure boot. | na |
| Anti-rollback RevisionNumber | 0x2d | Request: command length:1-6 data1: firmware type Scenario 1: 0xfe:bmc 0xfd:bios 0xfc: CPLD of the master board Scenario 2: 0xC0 uses ComponentID and ComponentIDEx to match. data2: ComponentID data3-6: ComponentIDEx (If this parameter is not involved, enter 0xFFFFFFFF.) Response: data1: RevisionNumber Anti-rollback RevisionNumber of the corresponding firmware | Request: command length:2-7 data1: firmware type Scenario 1: 0xfe:bmc 0xfd:bios 0xfc indicates the CPLD of the active board. data2: RevisionNumber Scenario 2: 0xC0 uses ComponentID and ComponentIDEx for matching. data2: ComponentID data3-6: ComponentIDEx (If this parameter is not involved, enter 0xFFFFFFFF.) data7: RevisionNumber |
| Considering the compatibility between the old and new BMC versions, after the BMC is upgraded to a certain version, the BMC cannot be rolled back to a version earlier than a specified revision number. 1. Subcommand for querying or setting BMC configuration parameters (Get/Set BMC Configuration) of RevisionNumber on the BMC side, preventing rollback RevisionNumber 0x2d 2. The following is an example of the Revision field in the update.cfg file: [Basic] Version=1.0 Revision=4 3. Comparison mechanism: If the value of Revision in the update.cfg file in the HPM package is smaller than the value of RevisionNumber on the BMC side, an upgrade failure message is returned. The implementation differences between different versions are as follows: 1. iBMC V2: You need to upgrade the dft.hpm package before modifying the configuration. 2. iBMC V3: The setting action is not coupled with the equipment. The setting action is supported in the official version. | |||
| Enable partner roots | 0x2e | na | Request: command length:0 Response: command length:1 data1:return value 0- The partner root is successfully enabled. ff: Failed to enable the partner root. |
| Customized speed adjustment policy for the rear hard disk backplane rearhbpcustompolicy | 0x2f | Request: command length:0 Response: data1: rear hdd backplane custom policy 0: default speed adjustment policy 1: public cloud speed adjustment policy Other values: reserved for future extension. Currently, the maximum return value is 1. | Request: command length:1 data1: rear hdd backplane custom policy 0: default speed adjustment policy 1: public cloud speed adjustment policy Other values: reserved for future expansion. Currently, the maximum value is 1. |
| Customization of Comparison Information About the First N Bytes of the User Password | 0x30 | Request: command length:0 Response: command length:2 data1:enable_status data2:compare_len data1: 0- The function of comparing the first n bytes of a user password is disabled. 1- The function of comparing the first n bytes of a user password is enabled. data2: value: compares the first $value bytes of the user password. | Request: command length:2 data1: 0- The first n bytes of a user password are not compared. 1- Enable the function of comparing the first n bytes of a user password. For other values, 0xcc is returned and an error is reported. data2: value: 4 to 20 (comparison length to be set) Note: This status is valid only when the password complexity check function is enabled. That is: If the password complexity check function is disabled, the password complexity check function does not take effect even if it is enabled. This function takes effect only after the password complexity check function is enabled. |
| Supported expansion module types supported expansion module types | 0x31 | Request: command length: 0 Response: data1: 0: SAS1.0 expansion module 1: SAS2.0 expansion module | Request: command length:1 data1: 0: SAS1.0 expansion module 1: SAS2.0 expansion module Response: command length:0 |
| System disk fault status system disk fault status | 0x32 | Request: command length: 0 Response: data1: [7:2]: reserved. [1]: ata2 fault status 0: no fault 1: faulty [0]: ata1 Fault status 0: no fault 1: faulty NOTE: After detecting a system disk fault, the product invokes a setting command to configure the fault status to the persistent medium for the BIOS to obtain. | Request: command length:1 data1: [7:2]: reserved. [1]: ata2 fault status 0: no fault 1: faulty [0]: ata1 Fault status 0: no fault 1: faulty Response: command length:0 |
| Indicates whether the first login policy can be modified. account first login policy switch status | 0x33 | Request: command length: 0 Response: data1: account first login policy switch status. Indicates whether the first login policy can be modified. 0: disabled 1: enabled | Request: command length:1 data1: account first login policy switch status. Response: status 0: disabled 1: enabled |
| Customized function configuration guestcustomconfig | 0x34 | Request: command length: 0 Response: data1~data4: customconfigstate [data1:data4] is a 32-bit unsigned number in little-endian mode. Each bit corresponds to a specific customization function. If a bit is set to 1, the corresponding customization function is enabled. If a bit is set to 0, the corresponding customization function is disabled. bit0: information displayed on the RESTful interface Bit 1 to bit 31: reserved for future extension data5: length of the vendor name in the customized URI (a maximum of 32 bytes) data6-(len+n): ASCII code of the vendor name in the URI | Request: command length: n data1~data4: redfish custom configuration [data1:data4] is a 32-bit unsigned number in little-endian mode. Each bit corresponds to a specific customization function. If a bit is set to 1, the corresponding customization function is enabled. If a bit is set to 0, the corresponding customization function is disabled. bit0: information displayed on the RESTful interface Bit 1 to bit 31: reserved for future extension data5: length of the vendor name in the customized URI. The value is a string of a maximum of 32 bytes. data6-(len+n): ASCII code of the vendor name in the URI |
| White-box customization item configuration | 0x35 | Request: Command Length: 1 data1: Obtain the option. Response: data1 to N: ASCII code of the customized vendor character string option: 0x07: indicates whether to display device information (including the manufacturer, manufacturer ID, model, device ID, and board name) on the WebUI. The options are as follows: ASCII code of 0 or 1. 0x08: indicates whether to display the one-click collection button on the WebUI. The options are as follows: ASCII code of 0 or 1. 0x09: specifies whether to display the virtual console on the home page, video screenshots on the maintenance and diagnosis page, virtual media and virtual console on the service management page, and KVM, VMM, and video port information on the service management page. The options are as follows: ASCII code of 0 or 1. CAUTION: The options 0x07, 0x08, and 0x09 apply only to the CM221, CM221S, CM221V2, CM421V2, CN221, CN221SV2, CN221V2 and SMM models. | Request: Command Length: N data1: setting option data2 to N: configured data option: 0x00: software name 0x01: alarm and event description 0x02: operation run log and security log (iBMA) 0x03: operation run log and security log (iBMCBMC) 0x04: command prompt 0x05: whether to display the QR code 0x06: KVM download link 0x07: indicates whether to display device information (including the manufacturer, manufacturer ID, model, device ID, and board name) on the WebUI. The options are as follows: ASCII code of 0 or 1. 0x08: indicates whether to display the one-click collection button on the WebUI. The options are as follows: ASCII code of 0 or 1. 0x09: specifies whether to display the virtual console on the home page, video screenshots on the maintenance and diagnosis page, virtual media and virtual console on the service management page, and KVM, VMM, and video port information on the service management page. The options are as follows: ASCII code of 0 or 1. |
| Set the product delivery place (in China or outside China). | 0x35 | - | - |
| FirstPowerOnTime | 0x36 | Request: Command Length: 0 Response: data1 to data2: year of the first power-on time data3: month of the first power-on time data4: number of days for the first power-on | Request: Command Length: 4 data1 to data2: year of the first power-on time data3: month of the first power-on time data4: number of days when the device is powered on for the first time NOTE: This parameter takes effect only in equipment mode. |
| Product delivery destination | 0x37 | Request: Command Length: 0 Response: data1: 0: delivery in China 1: delivery outside China | Request: Command Length:1 data1: 0: delivery in China 1: delivery outside China 0xff: The delivery destination is not restricted. Response: Command Length:0 |
| Node type, backup power type, and node software type | 0x38 | Request: Command Length: 0 Response: data1: 0: spare parts 1: storage node 2: compute node 0xff: compute node by default data2: [5:0]: node software type. This parameter is valid only for storage nodes. 0: spare parts 1–UVP 2–Euler 3–Vmware 0xff: unknown [7:6]: backup power type of the node 0: spare parts 1: transparent power backup 2-OS backup power 3: no backup power, not written into the EEPROM | Request: Command Length:2 data1: 0: spare parts 1: storage node 2: compute node 0xff: compute node by default data2: [5:0]: node software type. This parameter is valid only for storage nodes. 0: spare parts 1–UVP 2–Euler 3–Vmware 0xff: unknown [7:6]: backup power type of the node 0: spare parts 1: transparent power backup 2-OS backup power 3: no backup power, not written into the EEPROM Response: Command Length:0 |
| IP address of the DPU card | 0x39 | Request: command Length: 2 data1: DPU slot n data2: 0-IPv4 address 1-IPv6 address Response: data1: DPU slot n data2~n: hexadecimal representation of the IP address character string | Not supported. |
| BMC NAND flash information | 0x3A | Request: Command Length: 0 Response: data1: vendor ID 0x11: Toshiba 0x15: Samsung 0x45: SanDisk 0x90: Hynix 0xC2: Macronix data2: indicates the chip ID. This parameter is reserved. The default value is 0xff. data3: remaining service life percentage data4: percentage of available reserved blocks (supported only by Hynix and filled with 0xff if not supported) Data5–8: number of available reserved blocks (supported only by Hynix and filled with 0xff if not supported) | Not supported. |
| DPU network port link status | 0x3B | Request: command Length: 1 data1: DPU slot n Response: data1: DPU slot n data2: 0–linkup 1–linkdown | Not supported. |
| In-position information of internal and external devices in the cabinet | 0x3C Note: This parameter cannot be adjusted in cabinet scenarios. | Request: command Length: 2 data1: device type 1 – ECU (embedded liquid cooling unit) 2 – Temperature and Humidity Transmitter data2: slave component ID ff: indicates that all in-position information is returned. 0-7: return the in-position information of the slave component Response: data1: presence information of the slave component All in-position information 0xff: 8 in-position Indicates the in-position information of the component with a specified number. 0: Not detected 1: Detected | Request: command length:2 data1: device type 1-ECU (embedded liquid cooling unit) 2. Temperature and humidity transducer data2: presence information about a maximum of eight slave components Indicates the in-position information by bit. Ff-8 present 1: first in-position Response: command length:0 |
| Carrier Version Customization | 0x3C Remarks: This parameter will be migrated to 0x41. | - | - |
| Number of connected USB flash drives | 0x3D | Request: Command Length: 0 Response: data1: number of connected USB flash drives | Not supported |
| Enabling or Disabling the DST Function | 0x3E | Request: command length:0 Response: data1: DST switch status: 0: The DST is disabled. 1: The DST is enabled. | Request: command length:1 data1: 0: Disable the DST function. 1: The DST function is enabled. |
| MPC switch MpcEnable | 0x3F | Request: command length: 0 Response: data1: MPC switch status. MPC switch status 0: disabled 1: enabled | Request: command length:1 data1: MPC switch status. Response: status 0: disabled 1: enabled |
| Cabinet Bus Type | 0x40 | Request: Command Length: 2 Data1–data2: read length, which is fixed at: 0x01 0x00 Response: data1: cabinet bus type 0: three-bus cabinet 1: two-bus cabinet | Request: Command Length: 4 Data1–data2: length of the written data. The value is fixed at: 0x02 0x00 Data3–data4: cabinet bus type: 0x00 0x00 Three-bus cabinet 0x01 0x00 Two-bus cabinet Response: Command Length:0 |
| Customized Version Information | 0x41 | Request: command length: 1 data1: user-defined version information 1: version information customized for China Mobile 2: version information customized for China Unicom Response: command length:n data1: configuration value length Length of the customized version information. data2~n: configuration value Customized version information. | Request: command length:n data1: user-defined version information 1: version information customized for China Mobile 2: version information customized for China Unicom data2~n: configuration value Customized version information. |
| High temperature power-off mask enable | 0x42 | Request: command length:0 data1:0 Response: data1: 0 – disable high temp power off shield 1-enable high temp power off shield 255- not supported | Request: command length:1 data1: 0-disable high temp power off shield 1-enable high temp power off shield |
| Enter the minimum system. | 0x43 | Not supported | Request: command length:0 data: 0- Gracefully enter the minimum system. 1- forcibly entering the minimum system NOTE: To access the minimum system interface, you must have the BasicSetting and SecurityMgmt permissions. |
| Enabling NTP | 0x44 | Request: command length: 0 Response: data1: current enabled status of NTP. Status of the NTP service 0: disabled 1: enabled | Request: command length:1 data1: NTP enabled status will be set Value of enabled status: 0: disabled 1: enabled Response: |
| Enabling the BMC Version Revocation Function | 0x45 | Request: command length:0 Response: data1: 0: The BMC version revocation function is disabled. 1: The BMC version revocation function is enabled. | Request: command length:1 data: 0: The BMC version revocation function is disabled. 1: The BMC version revocation function is enabled. |
| SNMP OID vendor name customization | 0x46 | Request: command length:0 Response: data1 to datan: ASCII representation of the OID vendor character string of the customized SNMP interface | Request: command length:n data1 to datan: ASCII representation of the OID vendor character string of the SNMP interface to be set |
| BMC Version Revocation List | 0x47 | Request: command length:1 data1: sequence number of the revoked version, starting from 1 Response: data1~3: Manufacture ID data4: length of the revoked version. If there is no revoked version number in the corresponding sequence number offset, 0 is returned. Data5-n: BMC revocation version in ACSII code format. If the revocation version number is not included in the corresponding sequence number offset, an empty string is returned. | Request: command length:N data1: [7]: cascading flag 0: last frame 1: Data is available. [6:0]: offset of the file name. The value starts from 0. If the file name is too long and needs to be transferred for multiple times, the file name must be transferred from the beginning to the end in sequence. data2: Operation: operation type. The options are as follows: 0x00: added0x01: delete0x02: clear data3: version number data length data4~n: BMC version revocation list, which is separated by semicolons (😉 in the ACSII format. |
| Setting the BMC customer name | 0x48 | Not supported | Request: command length:n Data1-n: ACSII code of the customer name string to be set Currently, the following customer names are supported: ByteDance Alibaba CMCC Kwai Meituan Tencent CTCC JD CUCC Baidu NOTE: After running the command to set the customer name, you need to manually restart the BMC for the setting to take effect. |
| BMC firmware encryption type | 0x49 | Request: command length:0 Response: command length:1 data1: encryption type of the BMC firmware | Not supported |
| BMC coprocessor enable status | 0x4A | Request: command length:0 Response: command length:1 data1: enabling status of the BMC coprocessor. The options are as follows: 0: disabled 1: enabled | Not supported |
| Sending DNS record packets in polling mode | 0x4C | Request: command length: 0 Response: data length:8 data1: completion code data[2:4]: manufacturer id data5: 0-DNS record update disabled 0x1-DNS record update enabled data[5:8]: DNS record update interval (LSB First) | Request: 1. if data9 is 1 - DNS record update enabled: 1.1. command data length:1 DNS record update interval will be set up to 180 seconds 1.2. command data length:5 data[10:13]: DNS record update interval(LSB First) 2. if data9 is 0 - DNS record update disabled: 2.1. data length:1 DNS record update interval will be set up to 180 seconds Response: data length:4 data1: completion code data[2:4]: manufacturer id |
| Querying the Configuration of the Public Key Fingerprint for Secure Boot | 0x4D | Request: data length:2 data1: type of the public key fingerprint for secure boot 0: queries the public key fingerprint for secure boot of the BMC firmware in PKCS format. 1:Query the public key fingerprint data2 of the BMC firmware secure boot in PSS format. 0: Query the import status of the public key fingerprint for secure boot. 1: Query the hash value of the public key fingerprint for secure boot. Response: Request data2=0 data1: 0: not imported; 1: imported Request data2=1 data1: length n of the public key fingerprint information for secure boot data2~n+1: hash value of the public key fingerprint for secure boot | Not supported |
| CPLD firmware upgrade whitelist | 0x4E | Request: command length:3 Response: data1: CPLD type 0- no whitelist 1-anlu x6 firmware 0xff: initial state data2: Part ID. data3: Extended Component ID | Request: command length:3 data1: CPLD type 0- no whitelist 1-anlu x6 firmware 0xff: restored to the initial state data2: Part ID. data3: Extended Component ID |
| BMC startup status | 0x4F | Request: Data Length: 0 Response: Data Length: 1 data1: BMC startup status 0: The BMC startup is not complete. 1: The BMC startup is complete. | Not supported |
Command Example
Set the BMC DDNS.
Request:
bash
ipmicmd -k "0f 00 30 93 db 07 00 5a 4c 00 01 00 00" smi 0Response:
text
0f 31 00 93 00 db 07 00