IPMI OEM Command Format
wiki summary
http://3ms.huawei.com/hi/group/2030499/wiki_7451055.html
Basic info
The IPMI specification classifies OEM commands into three types: 1. Group Extension. 2. Organization-level OEM (OEM/Group) 3. Vendor-level OEM(Controller-specific OEM/Group)
Class 1: Netfn is 2Ch and 2Dh.
The organization is distinguished by the first byte of the request. The first byte of both the request and response must contain this byte. The vendor ID does not need to be entered in the request and response data.
The following is a typical OEM command definition extended by the PICMG organization. The first byte of the request and response contains the PICMG identifier.
Category 2: Netfn is 2Eh and 2Fh.
The first three bytes of the request and response of these commands must be the IANA number. The IANA number can be different from the vendor ID of the device. This is because that Because the meanings of these commands are defined by the organization, not by a certain vendor. If a vendor wants to implement these commands, the vendor must comply with the definition of the organization. This command is implemented by multiple vendors and has the same meaning. The functions of this command must be compatible.
Category 3: Netfn is 30h to 3Fh.
These commands are OEM commands defined by vendors. Therefore, the vendor ID does not need to be entered in the command request and response. What can I do if the commands of different vendors are defined repeatedly but have different meanings? The upper-layer software needs to be distinguished by vendor ID, but the vendor ID is not entered in the OEM command. What should I do? Obtain the vendor ID from the Get Device ID command.
That is, the upper-layer software needs to obtain the vendor ID before parsing the OEM command. Therefore, you do not need to enter the vendor ID again in such OEM commands.
Vendor ID
Query website: https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers
Application address: http://pen.iana.org/pen/PenApplication.page
2011 =0x7db HUAWEI Technology Co.,Ltd
19621=0x4ca5 alibabaPermission Description
Take iBMCBMC V3 as an example. The mds ipmi.json syntax supports nine permissions, which are defined as follows:
1) User role: role, which complies with the IPMI specifications. The options are Unspecified, Callback, User, Operator, Administrator and OEM.
2) Nine permissions: privilege. The definitions of the nine permissions are as follows (pay attention to the abbreviation of Mgmt): "UserMgmt" "BasicSetting" "KVMMgmt" "VMMMgmt" "SecurityMgmt" "PowerMgmt" "DiagnoseMgmt" "ReadOnly" "ConfigureSelf"
| Permission | Explanation in English. | ZH | Corresponding V2 Configuration | V3 Adaptation Guide |
|---|---|---|---|---|
| Callback | This may be considered the lowest privilege level. Only commands necessary to support initiating a Callback are allowed. | Indicates the lowest permission level. Only the commands required to start the callback are allowed. | ||
| User | Only 'benign' commands are allowed. These are primarily commands that read data structures and retrieve status. Commands that can be used to alter BMC configuration, write data to the BMC or other management controllers, or perform system actions such as resets, power on/off, and watchdog activation are disallowed. | Only "benign" orders are allowed. These are mainly commands for reading data structures and retrieving status. Commands that can be used to change BMC configurations, write data to the BMC or other management controllers, or perform system operations (such as reset, power on/off, and watchdog activation) are not allowed. | RMCP_USER | Query Commands |
| Operator | All BMC commands are allowed, except for configuration commands that can change the behavior of the out-of-band interfaces. For example, Operator privilege does not allow the capability to disable individual channels, or change user access privileges. | All BMC commands are allowed, except for configuration commands that can change the behavior of the out-of-band interface. For example, operator rights do not allow disabling a single channel or changing user access rights. | RMCP_OPERATOR | Setting Commands |
| Administrator | All BMC commands are allowed, including configuration commands. An Adminstrator can even execute configuration commands that would disable the channel that the Administrator is communicating over. | Allows all BMC commands, including configuration commands. Administrators can even execute configuration commands to disable the channel through which administrators are communicating. | RMCP_ADMIN | Commands for Modifying Hardware GUIDs |