System Management: SIPL Protocol
ATCA-9305 User’s Manual 10009109-01
7-6
• The seventh byte and beyond contain parameters for specific commands (if required).
• The final byte is the two’s-complement checksum of all of the message data after the
first checksum.
An IPMI response message (see Table 7- 4) is similar to an IPMI request message. The main
difference is that the seventh byte contains the Completion Code, and the eighth byte and
beyond hold data received from the controller (rather than data to send to the controller).
Also, the Slave Address and Logical Unit Number for the requester and responder are
swapped.
Table 7-4: Format for IPMI Response Message
SIPL PROTOCOL
The IPMC supports the Serial Interface Protocol Lite (SIPL) protocol. It supports raw IPMI
messages in SIPL and handles these messages the same way as it ha ndles IPMI messa ges
from the IPMB-0 bus, except that the replies route to either the payload or serial debug
interface. Messages are entered as case-insensitive hex-ASCII pairs, separated optionally by
a space, as shown in the following examples:
[18 00 22]<newline>
[180022]<newline>
The IPMC does not, however, support SIPL ASCII text commands, as defined by the IPMI
specification.
The IPMC does support Pigeon Point Systems extension commands, implemented as OEM
IPMI commands. These commands use Network Function Codes 2E/2F (hex), and the mes-
sage body is transferred similarly to raw IPMI messages, as described previously.
The following figures show an example of an extension command request and response,
respectively.
Byte: Bits:
76543210
1rqSA
2 Network Function (netFn) rqLUN
3Checksum
4rsSA
5rsSeqrsLUN
6Command
7Completion Code
8:N Data
N+1 Checksum