Hex-Ascii Command Format - Intel SR870BN4 - Server Platform - 0 MB RAM Product Manual

sequence, the BMC responds by outputting an output newline sequence. Otherwise, the BMC goes
back to looking for the start character.
Special Character Handling - <DEL> or <BKSP> character
The <BKSP> or <DEL> key can be used to delete the last character entered if the message has not
been submitted to the BMC yet.
Special Character Handling - Line Continuation character
Long IPMI messages can be split across multiple lines by using the line continuation
<BACKSLASH> character followed immediately by an input newline sequence. Line continuation
character usage is supported for both text and hex-ASCII commands.
Special Character Handling - Illegal characters
Any illegal characters received by the BMC clears the message in progress and forces the BMC
back to looking for the start character.

Hex-ASCII Command Format

Binary IPMI commands are sent and received as a series of case insensitive hex-ASCII pairs, where
each is optionally separated from the preceding pair by a single <space> character. The following
is an example of a binary IPMI request message:
[18 00 22]<newline sequence>
The software ID and LUN for the remote console are fixed and implied by the command. The
SWID for messages to the remote console is always 47h, and the Logical Unit Number
(LUN) is 00b.
Instead, there is a 'bridge' field that is used to identify whether the message should be routed to the
BMC's bridged message tracking or not. See the Terminal Mode IPMI Message Bridging section
for more information.
Table 26. Terminal Mode Request to BMC
Byte
1
2
3
4:N
Table 27. Terminal Mode Request from BMC
Byte
1
2
3
4
5:N
Intel® SR870BN4 Server System Product Guide
Explanation
[7:2] – Net Function (even)
[1:0] – Responder's LUN
[7:2] – Requester's Sequence Number
[1:0] – Bridge field
Command Number
Data
Explanation
[7:2] – Net Function (odd)
[1:0] – Responder's LUN
[7:2] – Requester's Sequence Number
[1:0] – Bridge field
Command Number
Completion Code
Data
151