A platform event filter (PEF) can trigger an action and generate an alert when a critical hardware-related event occurs. For each PEF, you can choose the action to be taken (or take no action) when a platform event occurs. You can also choose to generate and send an alert when a platform event occurs. Alerts are sent as an SNMP trap, so you must configure an SNMP trap destination before the alerts can be sent.
You can globally enable or disable the generation of platform event alerts. When disabled, alerts are not sent even if PEFs are configured to send them.
Enabling Platform Event Alerts
Before You Begin
You must log in as a user with admin privileges to enable platform event alerts.
Procedure
Step 1
In the
Navigation pane, click the
Admin tab.
Step 2
On the Admin tab, click Event Management.
Step 3
In the Event Management pane, click the Platform Event Filters tab.
Step 4
In the Platform Event Properties area, check the Enable Platform Event Filters check box.
Step 5
Click Save Changes.
Disabling Platform Event Alerts
Before You Begin
You must log in as a user with admin privileges to disable platform event alerts.
Procedure
Step 1
In the
Navigation pane, click the
Admin tab.
Step 2
On the Admin tab, click Event Management.
Step 3
In the Event Management pane, click the Platform Event Filters tab.
Step 4
In the Platform Event Properties area, uncheck the Enable Platform Event Filters check box.
Step 5
Click Save Changes.
Configuring Platform Event Filters
Before You Begin
You must log in as a user with admin privileges to configure platform event filters.
Procedure
Step 1
In the
Navigation pane, click the
Admin tab.
Step 2
On the Admin tab, click Event Management.
Step 3
In the Event Management pane, click the Platform Event Filters tab.
Step 4
In the Platform Event Filters area, complete the following fields for each event:
Name
Description
ID column
The unique filter ID.
Event column
The name of the event filter.
Action column
For each filter, select the desired action from the scrolling list box. This can be one of the following:
None—No action is taken.
Reboot—The server is rebooted.
Power Cycle—The server is power cycled.
Power Off—The server is powered off.
Send Alert column
For each filter that you want to send an alert, check the associated check box in this column.
Note
In order to send an alert, the filter trap settings must be configured properly and the Enable Platform Event Filters check box must also be checked.
Step 5
Click Save Changes.
What to Do Next
If you configure any PEFs to send an alert, complete the following task:
You must log in as a user with admin privileges to configure platform event filters.
Procedure
Command or Action
Purpose
Step 1
In the
Navigation pane, click the
Admin tab.
Step 2
On the Admin tab, click Event Management.
Step 3
In the Event Management pane, click the Event Trap Destination Settings tab.
Step 4
In the Event Trap Destination area, select a row and complete the following in the Destination Settings dialog box:
Name
Description
ID
column
The unique filter ID.
Enabled
check box
If this field is checked, alerts will be sent for the specified filter ID.
Destination IP Address
column
The IP address to which platform event information is sent.
Step 5
Click Save Changes.
Step 6
Click Send Event to send the platform event to the set destination.
Interpreting Platform Event Traps
A CIMC platform event alert contains an enterprise object identifier (OID) in the form 1.3.6.1.4.1.3183.1.1.0.event. The first ten fields of the OID represent the following information: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).wired_for_management(3183).PET(1).version(1).version(0), indicating an IPMI platform event trap (PET) version 1.0 message. The last field is an event number, indicating the specific condition or alert being notified.
Platform Event Trap Descriptions
The following table provides a description of the event being notified in a platform event trap message, based on the event number in the trap OID.
Event Number [Note 1]
Platform Event Description
0
0h
Test Trap
65799
010107h
Temperature Warning
65801
010109h
Temperature Critical
131330
020102h
Under Voltage, Critical
131337
020109h
Voltage Critical
196871
030107h
Current Warning
262402
040102h
Fan Critical
459776
070400h
Processor related (IOH-Thermalert/Caterr sensor) – predictive failure deasserted
459777
070401h
Processor related (IOH-Thermalert/Caterr sensor) – predictive failure asserted
460032
070500h
Processor Power Warning – limit not exceeded
460033
070501h
Processor Power Warning – limit exceeded
524533
0800F5h
Power Supply Critical
524551
080107h
Power Supply Warning
525313
080401h
Discrete Power Supply Warning
527105
080B01h
Power Supply Redundancy Lost
527106
080B02h
Power Supply Redundancy Restored
552704
086F00h
Power Supply Inserted
552705
086F01h
Power Supply Failure
552707
086F03h
Power Supply AC Lost
786433
0C0001h
Correctable ECC Memory Errors, Release 1.3(1) and later releases, filter set to accept all reading types [Note 4]
786439
0C0007h
DDR3_INFO sensor LED - RED bit asserted (Probable ECC error on a DIMM), Generic Sensor [Notes 2,3]
786689
0C0101h
Correctable ECC Memory Errors, Release 1.3(1) and later releases
818945
0C7F01h
Correctable ECC Memory Errors, Release 1.2(x) and earlier releases
818951
0C7F07h
DDR3_INFO sensor LED - RED bit asserted (Probable ECC error on a DIMM), 1.2(x) and earlier releases [Note 3]
851968
0D0000h
HDD sensor indicates no fault, Generic Sensor [Note 2]
851972
0D0004h
HDD sensor indicates a fault, Generic Sensor [Note 2]
Note 2: Some platforms and releases use generic sensor implementations, while some use Cisco proprietary sensor implementations.
Note 3: In Release 1.3(1) and later releases, the ECC sensor no longer activates the LED.
Note 4: When the event filter is set to accept all reading types, bits 15:8 of the hex event number are masked to 0. For example, event number 786689 (0C0101h) becomes 786433 (0C0001h).