Emerson ATCA-9305 Manuale Utente
System Management:
IPMI Messaging
7-3
Table 7-1:
Network Function Codes
Hex Code
Value(s):
Value(s):
Name:
Type:
Name:
00, 01
Chassis
chassis device
requests/responses
requests/responses
00 = command/request, 01 = response:
common chassis control and status functions
common chassis control and status functions
02, 03
Bridge
bridge
requests/responses
requests/responses
02 = request, 03 = response:
message contains data for bridging to the next
bus. Typically, the data is another message,
which also may be a bridging message. This
function is only present on bridge nodes.
message contains data for bridging to the next
bus. Typically, the data is another message,
which also may be a bridging message. This
function is only present on bridge nodes.
04, 05
Sensor/
Event
Event
sensor and event
requests/responses
requests/responses
04 = command/request, 05 = response:
for configuration and transmission of Event
Messages and system Sensors. This function
may be present on any node.
for configuration and transmission of Event
Messages and system Sensors. This function
may be present on any node.
06, 07
App
application
requests/responses
requests/responses
06 = command/request, 07 = response:
message is implementation-specific for a
particular device, as defined by the IPMI
specification
message is implementation-specific for a
particular device, as defined by the IPMI
specification
08, 09
Firmware
firmware transfer
requests/responses
requests/responses
08 = command/request, 09 = response:
firmware transfer messages match the format
of application messages, as determined by the
particular device
firmware transfer messages match the format
of application messages, as determined by the
particular device
0A, 0B
Storage
non-volatile
storage
requests/responses
storage
requests/responses
0A = command/request, 0B = response:
may be present on any node that provides
nonvolatile storage and retrieval services
may be present on any node that provides
nonvolatile storage and retrieval services
0C-2F
reserved
–
reserved: 30 network functions (15 pairs)
30-3F
OEM
–
30 = command/request, 3F = response:
vendor specific: 16 network functions (8 pairs).
The vendor defines functional semantics for
cmd and data fields. The cmd field must hold the
same value in requests and responses for a
given operation to support IPMI message
handling and transport mechanisms. The
controller’s Manufacturer ID value identifies the
vendor or group.
vendor specific: 16 network functions (8 pairs).
The vendor defines functional semantics for
cmd and data fields. The cmd field must hold the
same value in requests and responses for a
given operation to support IPMI message
handling and transport mechanisms. The
controller’s Manufacturer ID value identifies the
vendor or group.