Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 73 of 94
8 1 8 1 8 1 8 1 1
Data9 A Data10 A Data11 A
• • •
PEC
A P
Sensor
Number
0 Entity 0 Entity
Instance
0 From zero (0) to five (5) bytes of
Event Data
[data
dependent]
0
5.1.5.2 Message without Retransmission
This message causes the alert-sending device to transmit a single, un-retransmitted PET frame.
If the alert-sending device is either temporarily unable to handle the message or unable to send
the requested PET frame because the device’s transport media is down, the device must NACK
the message according to [SMBUS_2.0] definitions; otherwise, the device sends the single-frame
transmission.
1 7 1 1 8 1 8 1
S Slave Address Wr A Command A Byte Count A
• • •
Alert-sending Device Address 0 0 Messaging
0000 0100
0
0000 1011 to 0001 0000
16
0
8 1 8 1 8 1 8 1
Data1 A Data2 A Data3 A Data4 A
• • •
Sub Command No Retransmit
0001 0110
0 Version Number
0001 0000
0 Event Sensor Type 0 Event Type 0
8 1 8 1 8 1 8 1
Data5 A Data6 A Data7 A Data8 A
• • •
Event Offset 0 Event Source Type 0 Event Severity 0 Sensor Device 0
8 1 8 1 8 1 8 1 1
Data9 A Data10 A Data11 A
• • •
PEC
A P
Sensor
Number
0 Entity 0 Entity
Instance
0 From zero (0) to five (5) bytes of
Event Data
[data
dependent]
0
5.2 Boot Option Messages
5.2.1 Get Boot Options
This message, which uses the SMBus Block Read Protocol with PEC, is used by the managed
client’s firmware to retrieve the options sent over the network to the alert-sending device via the
RMCP commands Reset (10h), Power-up (11h), and Power Cycle Reset (13h). A managed
client that supports ASF-RMCP commands includes firmware that reports these results in an
ASF_RMCP ACPI structure.
The alert-sending device responds with one of two sub-commands to the Get Boot Options
message, depending on whether the device has received one of the ASF-RMCP Boot Options
commands (Reset (10h), Power-up (11h), and Power Cycle Reset (13h)) since the device last
received an SMBus Clear Boot Options message. If so, the device returns the Return Boot
Options sub-command along with the boot options values included in the ASF-RMCP command;
otherwise, the device returns the No Boot Options sub-command.
Note: Managed client firmware that supports ASF-RMCP should
1. Get the boot options as soon as practical during the boot process and subsequently clear the
options. This ensures that the boot options have a single-boot lifetime
.
2. Verify that the system boot was initiated by an ASF-RMCP command prior to taking any
action indicated by the Boot Options returned by this SMBus command.