HP Moonshot 1500 Chassis User Manual Page 43

  • Download
  • Add to my manuals
  • Print
  • Page
    / 189
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 42
Table 20 Send message command request and response data (continued)
Channel number where to send the message[3:0]
Message data. Format dependent on target channel type.2:N
Data fieldRequest data
byte number
Completion code1
Generic, plus additional command-specific completion codes: 80h = Invalid session handle. The
session handle does not match up with any currently active sessions for this channel.
If channel medium = IPMB, SMBus, or PCI management bus (This status is recommended for applications
that need to access low-level I
2
C or SMBus devices).
81h = Lost arbitration
82h = Bus error
83h = NAK on write
Response data(2:N)
This data will only be present when using the send message command to originate requests from
IPMB or PCI management bus to other channels such as LAN or serial/modem. It is not present in the
response to a send message command delivered via the system interface.
NOTE: The MC does not parse messages that are encapsulated in a send message command
and does not know what privilege level should be associated with an encapsulated message. Thus,
messages that are sent to a session using the send message command are always output using
the authentication type that was negotiated when the session was activated.
The following table summarizes the contents of the message data field when the send message
command is used to deliver an IPMI message to different channel types. In most cases, the format
of message information the message data field follows are the same used for the IPMB, with two
typical exceptions:
When the message is delivered to channels without physical slave devices, a SWID field takes
the place of the slave address field.
When the message is delivered to a channel that supports sessions, the first byte of the message
data holds a session handle.
Table 21 Send message data fields
Message data for sending requests (RQ) and
responses (RS)
Target channel protocolTarget channel type
RQ: rsSA, netFn/rsLUN, chk1, rqSA,
rqSeq/rqLUN, cmd, <data>, chk2
IPMBIPMB (I
2
C)1
RS: rqSA, netFn/rqLUN, chk1, rsSA, rqSeq/rsLUN,
cmd, completion code, <data>, chk2
RQ: Session handle
1
, rsSWID, netFn/rsLUN, chk1,
rqSWID or rqSA, rqSeq/rqLUN, cmd, <data>,
chk2
IPMB+session header802.3 LAN4
RS: Session handle
1
, rqSWID, netFn/rsLUN, chk1,
rsSWID or rsSA, rqSeq/rsLUN, cmd, completion
code, <data>, chk2
RQ: Session handle
1
, rsSWID, netFn/rsLUN, chk1,
rqSWID or rqSA, rqSeq/rqLUN, cmd, <data>,
chk2
IPMB (basic mode, terminal
mode, and PPP mode)
Asynch. serial/modem
(RS-232)
5
RS: Session handle
1
, rqSWID, netFn/rsLUN, chk1,
rsSWID or rsSA, rqSeq/rsLUN, cmd, completion
code, <data>, chk2
Standard command specification 43
Page view 42
1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 188 189

Comments to this Manuals

No comments