Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 33 of 94
Message
Status
Code
Description
43h 44h C1h C2h
10h-
FFh
Reserved for future definition by this specification
3.2.4 RMCP “ASF” Message Types
This section defines message data formats for the standard RMCP “ASF” class (i.e. the IANA
Enterprise Number in the RMCP Data section is 4542). This specification defines the Data
portion of each message; OEMs and ISVs can provide extensions using the general RMCP “ASF”
class, but cannot extend the standard messages’ packet size.
3.2.4.1 Reset (10h), Power-up (11h), and Power Cycle Reset (13h)
A management console can send these RMCP messages to cause a managed client to perform
a hard-reset, power up, or power cycle reset. See section 6.3.3 for detailed descriptions and
definitions of these remote control functions.
Each of these message types can optionally include Boot Options in its variable data; the options
define operations a managed client performs with the boot initiated by the RMCP message. The
RMCP message’s Data Length value indicates the presence (0Bh or greater) or absence (00h) of
the options. The Boot Options contain a bit-mask of standard options and a Special Command
with an optional parameter.
If a managed client doesn’t support the message (as indicated on the presumed, previous
response to the console’s Capabilities Request message), the alert-sending device issues an
RMCP Acknowledge and otherwise disregards the message. Any message disregarded in this
fashion has no effect on the alert-sending device’s response to a subsequently issued SMBus
Get Boot Options message (see 5.2 for these messages’ definitions). Otherwise, the alert-
sending device records the Boot Options and Special Command values and reports those values
in response to subsequently issued SMBus Get Boot Options messages until either
1. The alert-sending device receives another RMCP message, supported by the system. This
message’s Boot Options and Special Command values replace the previously recorded
values.
2. The alert-sending device receives an SMBus Boot Options Clear message (see 5.2.2 for
details). Until the alert-sending device receives another RMCP message with Boot Options
values, the device responds with the No Boot Options response to any SMBus Get Boot
Options messages.
When the Boot Options are present, the message’s Data field is organized as follows:
Boot
Options
Data Byte
Field Description
1-4
IANA Enterprise
Number
IANA-assigned Enterprise Number — ASF (4542) or OEM specific
— that defines the interpretation of the OEM Special Command
values and their associated Special Command Parameters, and
the OEM Parameters fields.
Note: This specification defines the interpretation of the Boot
Options Bit Mask field, regardless of the Enterprise Number value.
5 Special Command
Defines commands to be processed by the managed client on the
boot initiated by the ASF-RMCP message. See Special Command
Definitions below for more detail.