Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 90 of 94
Appendix C ASF Entity Function Checklists
This section contains the entity-specific checklists that define requirements and recommendations
for an ASF implementation.
C.1 Alert Sending Device
The following table identifies the required and optional features for an ASF alert-sending device.
See also C.2 Local Alert-Sending Device Configuration Software.
Table D-1 Alert-Sending Device Checklist for ASF Implementations
#### Description
AS1
The device includes an SMBus 2.0-compliant master/slave controller, and
external connection to a system’s SMBus.
Required
AS2
The device re-transmits PET frames, and meets the functionality described in
section 3.1.1.
Required
AS3
The device sets the Agent Address field of any transmitted PET’s Protocol Data
Unit per the RFC associated with the transport method, see section 3.1.2.
Required
AS4 The device supports the IPv4 (IP version 4) protocol. Required
AS5
The device statically assigns the Trap Source Type field of issued PETs to identify
the type of the source device, see section 3.1.4.
Required
AS6 The device supports transmission of a system heartbeat message, see 3.1.5.5. Optional
AS7 The device includes a watchdog timer. Required
AS8
The device implements the functionality required to support a system boot-failure
alert; see 3.1.5.6.
Required
AS9
The device provides support for all ASF-RMCP message types and formats
described in section 3.2 that have an IANA Enterprise Number value of 4542
(ASF).
Required
AS10 The device provides support for RMCP Message Class values other than 6 (ASF). Optional
AS11
The device provides support for ASF-RMCP messages that have an IANA
Enterprise Number value other than 4542 (ASF).
Optional
AS12
The device responds to RMCP control messages (see 3.2.4.1 and 3.2.4.2) as
configured by its OS-present configuration software.
Required
AS13
If the device has not been configured, it does not respond to RMCP control
messages (see 3.2.4.1 and 3.2.4.2).
Required
AS14
If there are legacy sensors in the system (as described in the system’s ACPI
implementation, see 4.1.2.2 ASF_ALRT), the alert-sending device periodically
polls the devices to determine the devices’ current status and sends any
associated ASF alerts. Refer to 6.1.2 for additional information.
Required
AS15
If there are legacy sensors in the system, the alert-sending device uses a 4-
second Minimum Legacy Device Poll Time.
Required
AS16
The device polls ASF sensors using the system-specified Inter-poll Wait Time
(see 4.1.2.1), as stored by the device’s configuration software in device-specific
non-volatile memory.
Required
AS17
If there are ASF sensors in the system, the alert-sending device issues periodic
SMBus Get Event Data and/or Get Event Status messages to determine the
devices’ current status and sends any associated ASF alerts.
Required
AS18 The device responds to the SMBus Device Type Poll message, see 5.3.1. Required
AS19
The device maintains its current link status, and reports this status in the Device
Type Poll response.
Required