Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide, Release 1.4
Configuring Platform Event Filters
Downloads: This chapterpdf (PDF - 462.0KB) The complete bookPDF (PDF - 2.98MB) | The complete bookePub (ePub - 520.0KB) | Feedback

Configuring Platform Event Filters

Configuring Platform Event Filters

This chapter includes the following sections:

Platform Event Filters

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 Alerts area, check the Enable Platform Event Alerts 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 Alerts area, uncheck the Enable Platform Event Alerts 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 tasks:

        Configuring SNMP Trap Settings

        Before You Begin

        You must log in as a user with admin privileges to perform this task.

        Procedure
          Step 1   In the Navigation pane, click the Admin tab.
          Step 2   On the Admin tab, click Communications Services.
          Step 3   In the Communications Services pane, click the SNMP tab.
          Step 4   In the Common Trap Destination Settings area, complete the following fields:
          Name Description

          Trap Community String field

          The name of the SNMP community group to which trap information should be sent.

          SNMP Version drop-down list

          The SNMP version and model used for the trap. This can be one of the following:

          Type field

          If you select V2 for the version, this is the type of trap to send. This can be one of the following:

          • Trap
          • Inform
          Step 5   In the Trap Destinations area, complete the following fields:
          Name Description

          ID column

          The trap destination ID. This value cannot be modified.

          Enabled column

          For each SNMP trap destination that you want to use, check the associated check box in this column.

          Trap Destination IP Address column

          The IP address to which SNMP trap information is sent.

          Tip   

          To change the settings for a trap or to send a test trap message, administrators can click the trap row in the table.

          Step 6   Click Save Changes.

          Sending a Test SNMP Trap Message

          Before You Begin

          You must log in as a user with admin privileges to perform this task.

          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 Trap Settings tab.
            Step 4   In the Trap Destinations area, click the row of the desired SNMP trap destination.

            The Traps Details dialog box opens.

            Step 5   Click Send SNMP trap.

            An SNMPv1 test trap message is sent to the trap destination.

            Note   

            The trap must be configured and enabled in order to send a test message.


            Interpreting Platform Event Traps

            A CIMC platform event alert sent as an SNMP trap 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]
            854016 0D0800h HDD Absent, Generic Sensor [Note 2]
            854017 0D0801h HDD Present, Generic Sensor [Note 2]
            880384 0D6F00h HDD Present, no fault indicated
            880385 0D6F01h HDD Fault
            880512 0D6F80h HDD Not Present
            880513 0D6F81h HDD is deasserted but not in a fault state
            884480 0D7F00h Drive Slot LED Off
            884481 0D7F01h Drive Slot LED On
            884482 0D7F02h Drive Slot LED fast blink
            884483 0D7F03h Drive Slot LED slow blink
            884484 0D7F04h Drive Slot LED green
            884485 0D7F05h Drive Slot LED amber
            884486 0D7F01h Drive Slot LED blue
            884487 0D7F01h Drive Slot LED read
            884488 0D7F08h Drive Slot Online
            884489 0D7F09h Drive Slot Degraded

            Note 1: Basic information about the event number format can be found in the IPMI Platform Event Trap Format Specification v1.0 at this URL: ftp://download.intel.com/design/servers/ipmi/pet100.pdf.

            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).