Event Filters
An event filter determines which alerts to catch and what to do with them. The event filter can make the alert information available in the following ways:
• Event Log: Events can be logged into the Event Log of the Web-UI, and also by the following WS-Man command: AMT_MessageLog.GetRecord.
• PETs: Events can also be sent to subscribers through Platform Event Trap (PETs). These events can be seen using a sniffer (such as Ethereal or Wireshark).
|
|
|
The Intel AMT Event Manager SNMP PET Alerts feature is being deprecated. Starting from Intel ME 18.0 firmware, the feature will no longer be available. The WS-Events feature remains, and will be used instead of SNMP PET alerts. |
|
|
|
Events conform to the Alert Standard Format (ASF) Specification DSP0136. |
A preconfigured filter exists (“AMT Diagnostic”), created by Intel AMT on initialization, which cannot be removed or updated. This filter, recognized by its PolicyID of 134, was created for the use of the User Notification local interface. It is configured to catch User Notification events in the local interface. From Intel AMT Release 6, this filter still exists but is no longer relevant since the User Notification local interface is not supported.
The maximum number of event filters you can create depends on the Intel AMT Release:
• Intel AMT Release 2.5 and earlier: 16
• Intel AMT Release 2.6 and later: 17 (increased by one to include the default preconfigured filter)
|
|
|
When the maximum number of event filters is reached, you must delete at least one of the filters before you add a filter. |
Intel AMT Default Event Filters
| Filter |
AlertSubscription PolicyID |
Device Address |
EventSensor Type |
Event Type |
Event Offset |
EventSource Type |
Event Severity |
Sensor Number |
Entity |
Entity Instance |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 0x01 | ANY | 0x01(Temperature) | ANY | 0x0F | ANY | ANY | ANY | ANY | ANY |
| 2 | 0x02 | ANY | 0x02(Voltage) | ANY | 0x0F | ANY | ANY | ANY | ANY | ANY |
| 3 | 0x03 | ANY | 0x04(Fan) | ANY | 0x0F | ANY | ANY | ANY | ANY | ANY |
| 4 | 0x04 | ANY | 0x05(Chassis Intrusion) | ANY | 0x0F | ANY | ANY | ANY | ANY | ANY |
| 5 | 0x05 | ANY | 0x20 | ANY | 0x01 | ANY | ANY | ANY | ANY | ANY |
| 6 | 0x06 | ANY | 0x0F | ANY | 0x00 Std BIOS Error | ANY | ANY | ANY | ANY | ANY |
| 7 | 0x07 | ANY | 0x0F | ANY | 0x01 Std BIOS Hang | ANY | ANY | ANY | ANY | ANY |
| 8 | 0x08 | ANY | 0x1E | ANY | 0x00 (No boot media) | ANY | ANY | ANY | ANY | ANY |
| 9 | 0x09 | ANY | 0x0F | ANY | 0x02 (Std BIOS Progress) | ANY | ANY | ANY | ANY | ANY |
| 10 | 0x0A | ANY | 0x0F | ANY | 0x82 (Std BIOS End Progress) | ANY | ANY | ANY | ANY | ANY |
| 11 | 0x0B | ANY | 0x25 (Entity presence heartbeat) | ANY | 0x00 | ANY | ANY | ANY | ANY | ANY |
| 11 | 0x0B | ANY | 0x25 (Entity presence heartbeat) | ANY | 0x00 | ANY | ANY | ANY | ANY | ANY |
| 12 | 0x0C | ANY | 0x23 (OS Boot Failure – WD Expired) | ANY | 0x0F | ANY | ANY | ANY | ANY | ANY |
| 13 | 0x0D | ANY | 0x06 (Password violation) | ANY | 0x05 | ANY | ANY | ANY | ANY | ANY |
| 14 | 0x0E | ANY | 0x24 (platform LAN alert – circuit breaker) | ANY | 0x01 | ANY | ANY | ANY | ANY | ANY |
| 15 | 0x0F | ANY | 0x12 (platform LAN alert – circuit breaker) | ANY | 0x00 | ANY | ANY | ANY | ANY | ANY |
| 16 | 0x86 | ANY | 0xC0 (Critical AMT User Notification) | ANY | 0x00 | ANY | ANY | ANY | ANY | ANY |
| 17 | 0x00 | ANY | 0xC1 (Critical AMT Notifications) | ANY | 0x00 | ANY | ANY | ANY | ANY | ANY |
|
|
|
The Intel AMT event log can contain a maximum of 390 events. |
|
See Also: |
|
Copyright © 2006-2022, Intel Corporation. All rights reserved. |