List of alerts generated by AMT

[valantinaa]

Everyone,

Ihope that the events which are listed under "Intel AMT features ->EventManager -> AMT Generated Events " in AMT SDk (6.0 hotfix ) ONLY EVENTSwhich AMT can intimate to remote consolevia snmp alerts. Please correct me if i am wrong.

'BIOS Hang Event' is one among those events & hv the below value :

Event Sensor Type 0Fh (System Firmware Error or Progress)
Event Type 01h (Generic)
Event Offset 01h (System Firmware Hang (uses same Event Data 2 definition as following System Firmware Progress offset)

Specific trap value : 983297

• Am receiving events which has sensor type & event type same as above ( ie 0Fh & 01h) but with different Event offset value of 02h& which indicates "System firmware progress event" in IPMI spec.

2011-03-02 17:33:44 0.0.0.0(via UDP: [10.0.0.205]:36522->[10.0.6.177]) TRAP, SNMP v1, community public
SNMPv2-SMI::enterprises.3183.1.1 Enterprise Specific Trap (1011458) Uptime: 2:22:20.92
SNMPv2-SMI::enterprises.3183.1.1.1 = Hex-STRING: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
00 1E 18 C3 C5 F0 FF FF 50 68 08 FF FF 03 00 40
19 00 00 00 00 00 00 FF 00 00 04 1A 00 01 C1

so, is it a mistake in SDK?

• Also receiving events like 'No bootable media' etc ....

2011-03-02 17:49:53 0.0.0.0(via UDP: [10.0.0.205]:36522->[10.0.6.177]) TRAP, SNMP v1, community public
SNMPv2-SMI::enterprises.3183.1.1 Enterprise Specific Trap (1994496) Uptime: 2:38:28.96
SNMPv2-SMI::enterprises.3183.1.1.1 = Hex-STRING: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
00 61 18 C3 C9 B9 FF FF 50 68 20 FF FF 04 00 40
00 00 00 00 00 00 00 FF 00 00 04 1A 00 01 C1

Regards
Valantina

[Paul_C_Intel1]

Valantina,

We are researching this and should have an answer soon.

Thanks, Paul

[valantinaa]

Thanks Paul. Awaiting for ur reply.

Steps for generating these alerts:

1. Configure AMT to send all the alerts.
2. Restart the managed system

Thanks & Regards,
Valantina

[blakeyang]

Hi Pual,

Since BIOS Hang Event(AMT generated) shares same event sensor type(0x0F) with "System Firmware Errors Events/System Firmware Progress Events"Could thisbe the reason whyAMT will send out SNMP traps?

There is a remark in BIOS Hang Event:

This Event is sent to all Event subscribers regardless of any Event Filter state.
This Event is logged regardless of any Event Filter state.

Another question is will AMTsends alert on those event which can be received if event filter(AMT_PEFFilter) and event subscriber(AMT_SNMPSubscriber) has properly be set.
From my understanding, event filter is used to filter out the events and do the specify actions(log/send alert); event subscriber is used to set the correspond ip as an event filter needs to sent alert out.
If there is an event comes , AMT checks if any event filter matches, and it does, checking event filter setting see if this event needs to be logged or sent alert which means thoseevents that AMT can received should be able to send alert.

"Intel AMT Features > Event Manager > Detailed Description > Event Types Summary"
The following table describes the types of events that are received by the Intel AMT.

For example, AMT system has an event filter with
Policy ID: 0x3
Event Sensor Type: 0x4
Event Type: 0xFF
Event Offset: 0xF (match all)
....rest is set to match all

an event subscriber:
Policy ID:0x3
AccessInfo: 172.16.99.99

Now, there is an event comes (Event Sensor Type:0x4, Event Offset:0x1), AMT should send alert toassigned IP. Is that correct behavior, or I misinterpret the meaning?

BTW, in the SDK document "Event Types Summary", case intrusion shows event sensor type as0x4, but in Manageability Commander Suite source code shows evnet sensor type as 0x5, could you tell me which is correct value? Thanks for your help.

Best,
Blake

[Paul_C_Intel1]

Valantina,

We also support the firmware progress events and the event data is the same as the firmware hang event. I was able to find all of these events listed in theWSEventAndPetTableReplacement.xls spreadsheet which can be found at (Intel AMT Features > WS-Eventing > Detailed Description) in the SDK.Please look at eventsPLAT186 and PLAT188 for System Firmware Hang, and System Firmware Progress Event respectively.Column M provides the offset, and column V provides the Event Data 2.

Always refer to the translation table in the SDK for a master list of the supported events.

Thanks, Paul

[Paul_C_Intel1]

Valantina,

No Boot Media is also a supported event, and is described in the spreadsheet as event PLAT286.

Thanks, Paul

[valantinaa]

Thanks Paul !!!

But..... oops!!! I was expectingit as 'Missed Eventin SDK documentation!!!'

Referring back to 'WSEventAndPetTableReplacement.xls' makes me to again look into thebelow thread
http://software.intel.com/en-us/forums/showthread.php?t=78604.

It was concluded in the discussion that alerts like

1. PLAT004 - Chassis Open
2. PLAT0128 - Memory added etc....

will not be sent as alert from AMT. (I couldn'treceive these events even after triggering this event !!!)

But these 2 alerts are there in 'WSEventAndPetTableReplacement.xls'. Please clarify !!!

Thanks,
Valantina

[valantinaa]

Please share your ideas , if anyone knows about thelist of alerts generated fromAMT !!!!

Thanks
Valantina

[Richard_B_Intel1]

Valantina-

Let me look into this. Itmay take a few days, but your question is being worked.

-RB

[Richard_B_Intel1 · Accepted solution]

Hi Valantina-

Thank you for your patience with this matter.

Intel AMT supports two eventingformatsPET (Platform Event Trap) and WS-MAN Eventing.Events can come from Intel AMT itself or from platform sensors. A platform's sensors are OEM specific, limited to 8and must be enabled (via the BIOS) before Intel AMT can monitor the platform sensor.

The file WSEventAndPetTableReplacement.xls describes all possible supported events; those having a MessagId starting with "iAMT"originate from Intel AMT itselfand those starting with "PLAT"originate from a platform sensor. The "greenish title/header" section of the spreadsheet details all the PET related event information. Again, keep in mind not every platform sensor event listed in this spreadsheet is available on every platform; this is OEM specific.

You should be able to enumerate the AMT_PETCapabilites instances to determine what platform sensors are available for Intel AMT to monitor. You would then create a filter specifing the correct sensor in order to have Intel AMT monitor that sensor. Finally, you would set up subscribers to be notified of the events.

Let us know if you have further questions.

-RB