Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 36 of 94
3.2.4.3 Presence Pong (40h)
A managed client sends this RMCP message — in response to a management console’s
Presence Ping (80h) RMCP message — to identify the presence of an ASF-RMCP-aware
managed client on the network. The Message Tag value of the Presence Ping’s RMCP Header
is copied to this message’s Message Tag field. The format of this message’s Data section is as
follows:
Data
Byte(s)
Field Description
1-4
IANA
Enterprise
Number
3
If no OEM-specific capabilities exist, this field contains the ASF IANA (4542)
and the OEM-defined field is set to all zeroes (00000000h). Otherwise, this
field contains the OEM’s IANA Enterprise Number and the OEM-defined
field contains the OEM-specific capabilities.
Note: Regardless of the value in the IANA Enterprise Number, this
specification defines the interpretation of data bytes 9 and higher.
5-8 OEM-defined
3
OEM defined fields.
9
Supported
entities
Bit(s)
Value/Meaning
7 Set to 1b if IPMI is supported.
6:4 Reserved for future definition by this specification, set to 000b.
3:0 0000b Reserved
0001b ASF, Version 1.0
Others Reserved for future definition by this specification.
10
Supported
interactions
Bit(s)
Value/Meaning
7 Set to 1b if RMCP security extensions are supported
6:0 Reserved for future definition by this specification, set to 0000000b
11-16 Reserved Reserved for future definition by this specification, set to all zeros.
3.2.4.4 Capabilities Response (41h)
A managed client sends this RMCP message — in response to a management console’s
Capabilities Request (81h) RMCP message — to describe the client system's ASF capabilities.
The Message Tag value of the Capability Request’s RMCP Header is copied to this message’s
Message Tag field. The capabilities described are the least common denominator of the
capabilities of the alert-sending device, the motherboard, the firmware, and the supporting
software. This message’s Data section is formatted as follows:
Data
Byte(s)
Field Description
1-4
IANA Enterprise
Number
3
If no OEM-specific capabilities exist, this field contains the ASF IANA
(4542) and the OEM-defined field is set to all zeroes (00000000h).
Otherwise, this field contains the OEM’s IANA Enterprise Number and the
OEM-defined field contains the OEM-specific capabilities.
Note: Regardless of the value in the IANA Enterprise Number, this
specification defines the interpretation of data bytes 9 and higher.
5-8 OEM defined
3
OEM defined fields.
9-10
Special
Commands
Supported
Defines the standard set of ASF-RMCP Special Commands supported by
the managed client. See Special Commands Bit Mask
for detailed
information.
11
System
Capabilities
Supported
Defines the standard set of system capabilities supported by the
managed client system. See System Capabilities Bit Mask
for detailed
information.
3
This field can contain OEM-defined values; the method through which these values are
communicated to an alert-sending device is left to the device manufacturer.