Skip to main content

Event Filters

A PEF implementation is recommended to provide at least 40 entries in the event filter table. A subset of these entries should be pre-configured for common system failure events, such as over-temperature, power system failure, and fan failure events. Remaining entries can be made available for events configured through OEM or system management software. Note that individual entries can be tagged as being reserved for system use, so this ratio of pre-configured entries to runtime configurable entries can be reallocated if necessary.

To open the Event Filters page, click Settings > Platform Event Filters > Event Filters.

By default, 15 event filter entries are configured among the 40 available slots.

  • Select All to view available configured and unconfigured slots.

  • Select Configured or Unconfigured to view available configured or unconfigured slots.

Supported operations on event filters​

Event Filters allows you to delete, modify, or add event filter entries.

  • To delete an event filter entry from the list, click Icon for deleting an event filter in the upper right corner.

  • To modify a configured event filter entry, click the entry to enter the Event Filter Configuration page and then modify its configurations.

  • To add an event filter entry, select a free slot to open the Event Filter Configuration page and then set its configurations.

Event Filter Configuration​

The Event Filter Configuration page includes the following configurations.

  • Enable this filter: Select this check box to enable the PEF settings.

  • Event Severity to trigger: Select any one of the event severities from the list.

  • Event Filter Action Alert: This option is enabled by default, which means to enable the PEF alert action.

  • Power Action: Select a desired power action.

  • Alert Policy Group Number: Configure the number of alert policies.
    Note
    Alert policies can be configured under Settings > Platform Event Filters > Alert Policies.

  • Raw Data: Select this check box to fill the Generator ID with raw data.

  • The Generator ID 1 field is used to give raw generator ID1 data value.

  • The Generator ID 2 field is used to give raw generator ID2 data value.

    Note
    In the raw data fields, prefix the value with '0x' to specify a hexadecimal value.
  • Generator Type:

    • Select Slave if events were generated from IPMB.

    • Select Software if events were generated from system software.

  • Slave Address/Software ID: Specify the corresponding I2C slave address or system software ID.

  • Select the particular Channel Number that event messages were received over. Alternatively, select 0 if the event messages were received via the system interface, primary IPMB, or internally generated by the BMC.

  • Choose the corresponding IPMB Device LUN if events were generated by IPMB.

  • Select the Sensor type of sensors that will trigger the event filter action.

  • Sensor name: Select the particular sensor from the sensor list.

  • Choose Event Options to be either all events or sensor-specific events.

  • The Event trigger field is used to give Event/Reading type value, ranging from 0 to 255.

  • The Event Data 1 AND Mask field is used to indicate wildcarded or compared bits, ranging from 0 to 255.

  • The Event Data 1 Compare 1 and Event Data 1 Compare 2 fields are used to indicate whether each bit position’s comparison is an exact comparison or not. Both values range from 0 to 255.

  • Event Data 2 AND Mask: similar to Event Data 1 AND Mask

  • Event Data 2 Compare 1 and Event Data 2 Compare 2: similar to Event Data 1 Compare 1 and Event Data 1 Compare 2 respectively

  • Event Data 3 AND Mask: similar to Event Data 1 AND Mask

  • Event Data 3 Compare 1 and Event Data 3 Compare 2: similar to Event Data 1 Compare 1 and Event Data 1 Compare 2 respectively

Click Save to save the changes and return to the event filter list.

Click Delete to delete the existing filter.