Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 85 of 94
Table , Entity Instance Number
Bit Description
7 0 = physical entity, 1 = logical entity
6:0 Entity Instance number
00h-5Fh = system relative
60h-7Fh = sensor device relative
00h-5Fh = System Relative. Instance number must be unique for each different entity of type
Entity ID in the system. This range is used for devices that have a fixed enumeration (i.e. Not
add in cards)
60h-7Fh = Sensor Device Relative. Instance number is unique for each different entity of type
Entity ID for the sensor device that provides access to the sensors for the entity. The entity is
uniquely identified by the combination of the Sensor Device number and the Entity Instance
number.
Note that when using a Sensor Device Relative instance number, all sensors for the entity must
be provided by one sensor device. Otherwise, it may appear that there are more instances of the
entity than are actually present. For example, suppose an add-in card has monitoring for both fan
current and fan speed for a single fan. If the fan current was monitored via sensor device 2 and
the fan speed monitored via sensor device 1, then the trap for fan current would return sensor
device number 1 and a trap for fan speed would return sensor device number 2. Because the
sensor device number is now part of what identifies a unique entity, software would view these
traps as being from different fans, even if the Sensor Device Relative instance number were the
same.
A.5 Event Source Type
A range for an ASF Event Source Type must be added to the PET specification to support the
proper PET frame from an ASF entity. This text below is the proposed addition to the Event
Source Type definition of the PET specification:
ASF 68h – 6Fh
A.6 Sensor Type = 23h (Watchdog 2) Updates
This sensor type defines Event Data 2 values that further describe the system state at the time of
the watchdog event. The possible values for the “timer use at expiration”, present in bits 3:0 of
this field must be extended to provide a discrete code to describe a system boot failure:
6h = System boot failure.
A.7 IPMI 1.0 Entity IDs
A mismatch between [PET_1.0] and [IPMI_1.0] was found in the Entity IDs table. The following
changes are required to make [PET] match [IPMI_1.0]:
Code Entity
19d
power unit / power domain (typically used as a pre-defined logical entity for grouping
power
20d power module / converter
21d power management / power distribution board
22d chassis back panel board
23d system chassis
24d sub-chassis
25d Other chassis board