ASF Specification v2.0 DSP0136 - DMTF

Alert Standard Format (ASF) Specification v2.0
DMTF Document DSP0136
PET Variable
Binding Field
Trap Source
Type
Event Source
Type
Event Severity
Sensor Device
Sensor Number
Entity
Entity Instance
Event Data
Language Code
Manufacturer
ID
System ID
Description
The Trap Source Type is the device or software that originated the trap on the network.
Normally it will be the NIC (50h), the System Management Card (58h), or the Modem
(60h).
The Event Source Type describes the originator of the event. The Event Source Type
is ASF 1.0 (68h) for all PET frames defined by this specification.
Event Source Type values in the range 68h to 6Fh are reserved by [PET] for ASF use:
68h
ASF 1.0 Implementation
69h-6Fh Reserved for future assignment by this (ASF) specification.
The Event Severity setting is met to give a management station an indication of the
severity of the event in the PET Frame. Typical values are Monitor (0x01), Non Critical
(0x08), or Critical Condition (0x10).
The Sensor Device is the SMBus address of the sensor that caused the event for the
PET Frame. In the case of a poll, the address of the polled sensor is used. In the case
of a push, the address of the pushing sensor is used. If there is no SMBus address
associated to the event (e.g. a firmware error or firmware progress message), then the
value is 0xFF (unspecified).
If an SMBus address is represented in this field, bits 7 through 1 contain the address,
and bit 0 is set to 0b.
The Sensor Number is used to identify a given instance of a sensor relative to the
Sensor Device. Values of 00h and FFh identify that the Sensor Number is not
specified.
The Entity indicates the platform device or subsystem associated with the event,
usually identifying a Field Replaceable Unit (FRU). For example, an over-temperature
event with this field set to “Processor” indicates a processor over-temperature event.
When a system includes multiple device instances, e.g. a multi-processor system,
Entity Instance identifies which unique device is associated with the event. For
example, if a system has two processors, this field distinguishes between events
associated with Processor #1 and Processor #2. A value of 00h in this field indicates
that Entity Instance is unspecified.
The Event Type determines the Event Data. Some of the PET messages defined in
this specification allow the inclusion of a variable number of event data bytes, to further
describe the event. When event data is included, the first byte of event data (Event
Data 1) defines the format of Event Data bytes 2 through 5 that follow, using the
following enumerations:
00b Data not specified
01b Data conforms to standard definitions
10b Data conforms to OEM definitions
11b Reserved for future assignment
ED1 Bit Range Description
7:6 Defines the format of Event Data 2
5:4 Defines the format of Event Data 3
3:2 Defines the format of Event Data 4
1:0 Defines the format of Event Data 5
Note: Values in Event Data bytes 6 through 8 are OEM-specific and outside the range
of this specification.
The Language Code is used with the OEM Custom Fields. For PET frames that do not
have any OEM specific data, the language code should be set to FFh (unspecified).
The IANA Manufacturer ID associated with the alerting system. The value is specified
by the system’s ACPI implementation, see 4.1.2.1 ASF_INFO on page 50 for details.
The manufacturer associated with the alerting system assigns the system identifier.
The value is specified by the system’s ACPI implementation, see 4.1.2.1 ASF_INFO on
page 50 for details.
DSP0136 23 April 2003 Page 9 of 94