X hits on this document

PDF document

February 10, 2006 - page 54 / 238

657 views

0 shares

0 downloads

0 comments

54 / 238

42

CHAPTER 3. IPMI INTERFACES

4

5 6 7

b8

34 00 f4

Responder LUN in bits 0-1 (0 in this case), Sequence number in bits 2-7 (2eh in this case). The command, a Send Message response in this case. Completion code Checksum for the whole message.

5

01

Command, a Get Device ID response

6

00

message data

7

00

message data

8

00

message data

9

01

message data

10

05

message data

11

51

message data

12

29

message data

13

57

message data

14

01

message data

15

00

message data

16

00

message data

17

09

message data

18

01

message data

19

01

message data

20

00

message data

21

00

message data

22

a0

Checksum for the whole message

Notice that in this second response, the destination address, LUNs, sequence numbers, etc. are from the IPMB message, not from the original LAN message.

Separate Send Message and Translated responses

In this possibility, a Send Message response comes back with no data, then a separate message comes back with the data, but the data in the second message has the same header information as the first, with a different command. This could be inferred from the errata, but it makes things more difficult to track. For instance, if you encapsulated a Send Message command inside a Send Message, the second response would

The following is the second message, the IPMB response:

Byte Value Description

IPMB Destination address (the BMC’s IPMB address) IPMB Requester LUN in bits 0-1 (2 in this case), Send Message response NetFN in bits 2-7 (7 in this case) Checksum for the previous two bytes Responder IPMB address Requester LUN in bits 0-1 (0 in this case), Sequence number in bits 2-7 (2fh in this case).

2

C2

3

C0

4

BC

0

20

1

1E

Document info
Document views657
Page views657
Page last viewedFri Dec 09 08:36:01 UTC 2016
Pages238
Paragraphs8090
Words85809

Comments