HP Moonshot 1500 Chassis User Manual download pdf (Page 50)

Table 26 Master write-read command request and response data (continued)

Read count. Number of bytes to read, 1 based. 0 equals not bytes to read. The maximum read count

should be at least 34 bytes. This allows the command to be used for an SMBus Block Read. This is

required if the command provides access to an SMBus or IPMB. Otherwise, if FRU SEEPROM devices

are accessible, at least 31 bytes must be supported. Note than an implementation that supports fewer

bytes can be supported if none of the devices to be accessed can handle the recommended minimum.

Data to write. This command should support at least 35 bytes of write data. This allows the command

to be used for an SMBus Block Write with PEC. Otherwise, if FRU SEEPROM devices are accessible,

4:N

at least 31 bytes must be supported. Note that an implementation is allowed to support fewer bytes

if none of the devices to can handle the recommended minimum.

Data fieldIPMI response

data byte

number

Completion code1

A management controller shall return an error Completion Code if an attempt is made to access an

unsupported bus. This is a generic response but also may include the following command specific

codes:

• 81h—Lost arbitration

• 82h—Bus error

• 83h—NAK on write

• 84h—Truncated read

Bytes read from specified slave address. This field will be absent if the read count is 0. The controller

terminates the I

C transaction with a STOP condition after reading the requested number of bytes.

(2:M)

Get channel authentication capabilities command

This command is available to the MC.

This command is sent in unauthenticated (clear) format. This command is used to retrieve capability

information about the channel from which the message is delivered, or for a particular channel.

The command returns the authentication algorithm support for the given privilege level. When

activating a session, the privilege level passed in this command is normally the same requested

maximum privilege level that is used for a subsequent activate session command.

MC implementations of IP-based channels must support the get channel authentication

capabilities command using the IPMI v1.5 packet format. BMCs that support IPMI v2.0 RMCP+

must also support the command using the IPMI v2.0/RMCP+ format.

The get channel authentication capabilities command can also be used as a no-op

“ping” to keep a session from timing out.

Session header fields request and response data prior when used prior to session activation

authentication type = NONE/payload type = IPMI message

session seq# = null (0’s)

Session ID = null (0’s)

AuthCode = NOT PRESENT

Table 27 Get channel authentication capabilities command request and response data

Data fieldIPMI request

data byte

number

Channel number1

50 Command specification

1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 188 189

Comments to this Manuals

No comments

HP Moonshot 1500 Chassis User Manual Page 50

Comments to this Manuals

Related products and manuals for Chassis components HP Moonshot 1500 Chassis