Get User Access
更新时间： 2026/08/06
在Gitcode上查看源码Get User Access
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Obtain the access permission of the BMC user.
Privilege
UserMgnt
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | App 06h |
| CMD | 44h |
| 1 | [7:4]-reserved [3:0]-Channel Number |
| 2 | [7:6]-reserved [5:0]-User ID 000000b=reserved. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code Note: an implementation will not return an error completion code if the user access level is set higher than the privilege limit for a given channel. If it is desired to bring attention to this condition, it is up to software to check the channel privilege limits and provide notification of the mis-match |
| 2 | Maximum number of User IDs. 1-based. Count includes User 1. A value of 1 indicates only User 1 is supported [7:6]-reserved [5:0]-maximum number of user IDs on this channel |
| 3 | Count of currently enabled User IDs (1-based). A value of 0 indicates that all users, including User 1, are disabled. This is equivalent to disabling access to the channel [7:6]-User ID Enable status (for IPMI v2.0 errata 3 and later implementations) 00b=User ID enable status unspecified. (For backward compatibility with pre-errata 3 implementations. IPMI errata 3 and later implementations should return the 01b and 10b responses) 01b=User ID enabled via Set User Password command 10b=User ID disabled via Set User Password command 11b=reserved [5:0]-count of currently enabled user IDs on this channel (Indicates how many User ID slots are presently in use) |
| 4 | Count of User IDs with fixed names, including User 1 (1-based). Fixed names in addition to User 1 are required to be associated with sequential user IDs starting from User ID 2 [7:6]-reserved [5:0]-count of user IDs with fixed names on this channel |
| 5 | Channel Access [7]-reserved [6]-0b=user access available during call-in or callback direct connection 1b=user access available only during callback connection For pre- IPMI v2.0 errata 3 implementations: bits 5:4, following, are used for determining the 'count of currently enabled user IDs' in byte 3. Either bit being set to 1b represents an 'enabled user ID' For IPMI v2.0 errata 3 and later implementations: The 'count of enabled User IDs' is based on the User IDs that are presently enabled as reflected in byte 3, bits [7:6], User ID Enable status Note: Some pre- IPMI v2.0 errata 3 implementations may automatically clear bits [5:4], and may also prevent them from being set, while the User ID is disabled. IPMI v2.0 errata 3 and later implementations should not alter bits [5:4] based on whether a User ID is enabled or not [5]-0b=user disabled for link authentication 1b=user enabled for link authentication [4]-0b=user disabled for IPMI Messaging 1b=user enabled for IPMI Messaging [3:0]-User Privilege Limit for given Channel 0h=reserved 1h=Callback 2h=User 3h=Operator 4h=Administrator 5h=OEM Proprietary Fh=NO ACCESS (Note: this value does not add to, or subtract from, the number of enabled user IDs) |
Command Example
Obtain the BMC user access permission.
Request:
bash
ipmitool raw 0x06 0x44 0x01 0x03Response:
text
11 42 01 74