Skip to main content

Platform Event Filters

Platform Event Filter (PEF) provides a mechanism for configuring the BMC to take selected actions on event messages that it receives or has internally generated. These actions include operations such as system power-off, system reset, as well as triggering the generation of an alert.

Event Filters

This page shows all configured Event filters and available slots. You can modify or add new event filter entries on this page. By default, 15 event filter entries are configured out of a maximum of 40 slots.

  • Click the Event Filters section to configure the event filters in the available slots

    • All: Display all the event filters.

    • Configured: Display the configured event filters.

    • Unconfigured: Display the unconfigured event filters.

  • Click the Delete icon (x) on the top right corner to directly delete an item from the list.

  • To add an event filter entry, select a free section to open the event filter entry page.

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

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

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

    • Event Filter Action Alert: Check the box 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.

    • Channel Number: Set the channel 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.

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

    • Sensor type: Select the sensor types that will trigger the event filter action.

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

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

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

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

    • Event Data 1 Compare 1: This field is used to indicate whether each bit position’s comparison is an exact comparison or not. Values range from 0 to 255.

    • Event Data 1 Compare 2: This field is used to indicate whether each bit position’s comparison is an exact comparison or not. Values range from 0 to 255.

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

    • Event Data 2 Compare 1: This field is used to indicate whether each bit position’s comparison is an exact comparison or not. Values range from 0 to 255.

    • Event Data 2 Compare 2: This field is used to indicate whether each bit position’s comparison is an exact comparison or not. Values range from 0 to 255.

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

    • Event Data 3 Compare 1: This field is used to indicate whether each bit position’s comparison is an exact comparison or not. Values range from 0 to 255.

    • Event Data 3 Compare 2: This field is used to indicate whether each bit position’s comparison is an exact comparison or not. Values range from 0 to 255.

Alert Policies

This page shows all configured Alert policies and available slots. You can modify or add new alert policy entries on this page. A maximum of 60 slots are available. Click the Alert Policies section to configure the alert policies in the available slots.

  • Policy Group Number: Displays the Policy number of the configuration.

  • Enable this alert: Check the box to enable the policy settings.

  • Policy Action: Choose any one of the Policy set values from the list.

  • LAN Channel: Choose a particular channel from the available channel list.

  • Destination Selector: Choose a particular destination from the configured destination list.

  • Event Specific Alert String: Check the box to specify event-specific Alert String.

  • Alert String Key: Specify which string is to be sent for this Alert Policy entry.

LAN Destinations

This page is used to configure the LAN destination of PEF configuration. Select any empty slot to configure LAN Destinations.

  • LAN Channel: Displays LAN Channel Number for the selected slot (read only).

  • LAN Destination: Displays ID for setting Destination Selector of Alert Policy (read only).

  • SNMP Destination Address: Destination type can be either an SNMP Trap or an E-mail alert. For E-mail alerts, the four fields - SNMP Destination Address, BMC User Name, Email subject and Email message needs to be filled. For SNMP Trap, only the SNMP Destination Address has to be filled.

  • Destination Type: Destination type can be either an SNMP Trap or an E-mail alert.
    • For E-mail alerts, SNMP Destination Address, BMC Username, Email subject, and Email message needs to be filled. The SMTP server information also must be added under Settings > Monitoring > SMTP Settings.

    • For SNMP Trap, only the SNMP Destination Address must be filled.

  • SNMP Destination Address: If Destination type is SNMP Trap, then enter the IP address of the system that will receive the alert. Destination address will support the IPv4 address format and IPv6 address format. If Destination Type is E-mail Alert, then provide the e-mail address that will receive the e-mail.

  • BMC User Name: If Destination Type is Email Alert, then choose the user to whom the email alert has to be sent. E-mail address can be configured under Settings > User Management.

  • Email Subject & Email Message: These fields must be configured if email alert is chosen as destination type. An email will be sent to the configured email address of the user in case of any severity events with a subject specified in subject field and will contain the message field’s content as the email body. These fields are not applicable for ‘AMI-Format’ email users.