Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 10 of 94
PET Variable
Binding Field
Description
OEM Custom
Fields
Whenever possible PET frames should use the error codes and values contained in the
PET specification to describe events. The OEM Custom fields should only be used if
the event cannot be expressed in a standard way. If there are no OEM Custom Fields,
then the type field is set to C1h.
3.1.4.1 PET Frame Content Sources
The following sections use this legend to provide a map to the information source for the various
elements of a Platform Event Trap:
Hard-coded by Alert-
Sending Device
SMBIOS Data SEEPROM Data Sensor Data
SMBus “Push Alert”
Message Data
Determined by Alert-
Sending Device (non-
constant)
ACPI Data
These abbreviations are used for PET fields within the following sections:
TST Trap Source Type
EST Event Source Type
SEV Severity
SD Sensor Device
S# Sensor Number
E Entity
EI Entity Instance
LC Language Code
Initial Firmware Timeout
This information map applies to the initial timeout failure that an alert-sending device transmits if
the reset-activated watchdog timer is not stopped by the managed client’s firmware.
Specific Trap Field
Reserved Event Sensor Type Event Type Event Offset
Variable Bindings Fields
GUID Seq# Local
Timestamp
UTC
Offset
T
S
T
E
S
T
S
E
V
S
D
S
#
E
E
I
Event Data
L
C
Manufacturer ID
System
ID
OEM
C. F.