X hits on this document

PDF document

February 10, 2006 - page 99 / 238

622 views

0 shares

0 downloads

0 comments

99 / 238

C7h

C8h

C9h

CAh

CBh

CCh

CDh

CEh

CFh

D0h

D1h

D2h

D3h

Command Length Invalid Command Field Too Long Parameter Out of Range

Too Many Re- quested Bytes

Invalid Object

Invalid Data Field Command In- valid for Object No Response

Duplicate Re- quest

SDR

Respos-

itory

Being

Updated Firmware Being Updated

BMC ing

Initializ-

Destination Un- available

The received command was the wrong length for the command.

A field in a command was too long for the given command.

One or more fields in a command were outside the range of allowed values. According to the spec, “This is different from the ’Invalid data field’ (CCh) code in that it indicates that the erroneous field(s) has a contiguous range of possible values.” The meaning of that enigmatic statement is unknown. A request was made for some data, but the requested number of bytes was either beyond the end of the data or too long to fit into the return response. The requested sensor, record, or data was not present. The com- mand is supported, but the specific object asked for does not exist. An invalid data field was in the request. See error C9h for more details. The specific sensor, record, or data does not support the given command. The command response could not be provided. The meaning of this is unknown. A duplicate request was received and ignored. The spec says “This completion code is for devices which cannot return the re- sponse that was returned for the original instance of the request. Such devices should provide separate commands that allow the completion status of the original request to be determined. An Event Reciever does not use this completion code, but returns the 00h completion code in response to (valid) duplicate requests.” The meaning of this statement is unknown. However, in general IPMI should be stateless because reponses can be lost and com- mands retransmitted. Commands that have intermediate state need to be handled very carefully (and there are none in the main spec). The SDR repository is currently in update mode so the given command could not be executed.

The given command could not be executed because firmware on the system is being updated. The given command could not be executed because the BMC (or probably any MC) is currently initializing. An MC could not deliver the command to the given destination. For instance, if you send a “Send Message” command to a channel that is not active, it may return this.

87

Document info
Document views622
Page views622
Page last viewedWed Dec 07 21:09:20 UTC 2016
Pages238
Paragraphs8090
Words85809

Comments