Set Access Rule Configuration
更新时间： 2026/08/06
在AtomGit上查看源码Set Access Rule Configuration
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Configure login rules.
Privilege
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 = 2Eh |
| 5 | Access rule parameter. For details, see Table 1. |
| 6 | Block Selector (00h if parameter does not require a block number) |
| 7 | [7:1]: reserved [0]: cascading flag 0: last data 1: middle data |
| 8 | 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. |
| 9 | Length: length of the data to be written. |
| 10:N | Written data |
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. |
Command Example
Configure a login rule.
Request:
bash
ipmicmd -k "0f 00 30 93 db 07 00 2e 01 01 00 00 01 01" smi 0Response:
text
0f 31 00 93 00 db 07 00The example response assumes successful command execution (completion code 00). Enables login rule 1: parameter 01h, offset 0, length 1, value 01h. The parameter is defined by query command 2Fh.