Suspend/Resume Payload Encryption
更新时间： 2026/08/06
在Gitcode上查看源码Suspend/Resume Payload Encryption
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Suspends or resumes payload encryption.
Privilege
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | App 06h |
| CMD | 55h |
| 1 | [7:6]-reserved [5:0]-payload type (See Table 1. Payload Type Numbers) |
| 2 | Payload Instance [7:4]-reserved [3:0]-payload instance 1-based 0h=reserved |
| 3 | [7:2]-reserved [4:0]-Operation 2h=Regenerate initialization vector For xRC4 encryption, this causes the BMC to reinitialize the xRC4 state machine, reset the data offset, and deliver a new Initialization Vector value in the next encrypted packet it sends to the remote console. Because of processing delays and potential tasks in progress, the remote console may receive additional packets from the BMC that are encrypted using the prior Initialization Vector before getting packets that use the new IV 1h=Resume/Start encryption on all transfers of specified payload data from the BMC 0h=Suspend encryption on all transfers of specified payload messages from the BMC |
Table 1 Payload Type Numbers
| number | type | major format version | minor format version |
|---|---|---|---|
| Standard Payload Types | |||
| 0h | IPMI Message | 1h | 0h |
| 1h | SOL (serial over LAN) | 1h | 0h |
| 2h | OEM Explicit(When this payload type appears in the network header, it indicates that the packet includes explicit OEM IANA and OEM Payload ID fields that identify the payload type, instead of using an OEM Payload Type Handle to identify the type of payload contained in the packet. When used, this option adds 6 bytes to the overhead of the packet.) | OEM specified according to OEM IANA and OEM Payload ID. | OEM specified according to OEM IANA and OEM Payload ID. |
| Session Setup Payload Types | |||
| 10h | RMCP+ Open Session Request | 1h | 0h |
| 11h | RMCP+ Open Session Response | 1h | 0h |
| 12h | RAKP Message 1 | 1h | 0h |
| 13h | RAKP Message 2 | 1h | 0h |
| 14h | RAKP Message 3 | 1h | 0h |
| 15h | RAKP Message 4 | 1h | 0h |
| OEM Payload Type Handles | |||
| 20h-27h | Handle values for OEM payloads OEM0 through OEM7, respectively. | OEM specified according to OEM IANA and OEM Payload ID. | OEM specified according to OEM IANA and OEM Payload ID. |
| all other | reserved | - | - |
The payload type number is a 6-bits (00h-3Fh).
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code Generic plus the following command-specific completion codes: 80h: Operation not supported for given payload type 81h: Operation not allowed under present configuration for given payload type 82h: Encryption is not available for session that payload type is active under 83h: The payload instance is not presently active |
Command Example
Suspend or resume payload encryption.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN