HP Moonshot 1500 Chassis User Manual Page 75

  • Download
  • Add to my manuals
  • Print
  • Page
    / 189
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 74
Table 46 Payload-specific encryption behavior (continued)
Payload Type = SOL
The SOL configuration parameters allow configuring the system to require that SOL data be encrypted.
The MC will transmit SOL payload data according to encryption settings that were selected when the payload was
activated unless over-ridden by SOL configuration parameters.
The Suspend/Resume Payload Encryption command controls whether SOL Payload data is encrypted or not.
Table 47 Suspend/resume payload command request and response data
Data fieldIPMI
request
data byte
number
[7:6] - reserved1
[5:0] - payload type (See Table 13-16, Payload Type Numbers)
Payload Instance2
[7:4] - reserved
[3:0] - payload instance. 1-based. 0h = reserved.
[7:2] - reserved3
[4:0] - Operation
2h = Regenerate initialization vector. For xRC4 encryption, this causes the MC 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 MC 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 MC.
0h = Suspend encryption on all transfers of specified payload messages from the MC.
Data fieldIPMI
response
data byte
number
Completion Code1
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.
Set channel security keys command
The Set Channel Security Keys command provides a standardized interface for initializing system
unique keys that are used for the pseudo-random number generator key (KR) and the key-generation
key (KG) used for RMCP+. Implementing the ability to set Kr is optional. The command is provided
mainly to offer a common interface for BMCs that are not pre-configured with a KR values, or which
may need their KR values to be restored if they are lost due to a data corruption or firmware update.
The command includes a mechanism that allows specified keys to be “locked”. Once locked, the
key value cannot be read back or rewritten via standard IPMI commands. It is possible, however,
that a firmware update or re- installation procedure may cause the keys to be cleared or unlocked.
Software utilities responsible for MC initial installation and setup should check to see whether keys
have been locked and if not, should initialize them appropriately and lock them.
Standard command specification 75
Page view 74
1 2 ... 70 71 72 73 74 75 76 77 78 79 80 ... 188 189

Comments to this Manuals

No comments