Contents
Configuring Platform Event Filters
This chapter includes the following sections:
- Platform Event Filters
- Enabling Platform Event Alerts
- Disabling Platform Event Alerts
- Configuring Platform Event Filters
- Configuring SNMP Trap Settings
- Sending a Test SNMP Trap Message
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
Procedure
Command or Action Purpose Step 1 Server# scope fault Enters the fault command mode.
Step 2 Server /fault # set platform-event-enabled yes Enables platform event alerts.
Step 3 Server /fault # commit Commits the transaction to the system configuration.
Step 4 Server /fault # show [detail] (Optional) Displays the platform event alert configuration.
Disabling Platform Event Alerts
Procedure
Command or Action Purpose Step 1 Server# scope fault Enters the fault command mode.
Step 2 Server /fault # set platform-event-enabled no Disables platform event alerts.
Step 3 Server /fault # commit Commits the transaction to the system configuration.
Step 4 Server /fault # show [detail] (Optional) Displays the platform event alert configuration.
Configuring Platform Event Filters
ProcedureYou can configure actions and alerts for the following platform event filters:
ID Platform Event Filter 1
Temperature Critical Assert Filter
2
Temperature Warning Assert Filter
3
Voltage Critical Assert Filter
5
Current Assert Filter
6
Fan Critical Assert Filter
8
Processor Assert Filter
9
Power Supply Critical Assert Filter
10
Power Supply Warning Assert Filter
11
Power Supply Redundancy Lost Filter
12
Discrete Power Supply Assert Filter
13
Memory Assert Filter
14
Drive Slot Assert Filter
What to Do NextThis example configures the platform event alert for an event:
Server# scope fault Server /fault # scope pef 13 Server /fault/pef # set action reboot Server /fault/pef *# set send-alert yes Server /fault/pef *# commit Server /fault/pef # show Platform Event Filter Event Action Send Alert --------------------- --------------------------- ----------- ------------------ 13 Memory Assert Filter reboot yes Server /fault/pef #
If you configure any PEFs to send an alert, complete the following tasks:
Configuring SNMP Trap Settings
Procedure
Command or Action Purpose Step 1 Server# scope fault Enters the fault command mode.
Step 2 Server /fault # set community-str string Enter the name of the SNMP community to which trap information should be sent.
Step 3 Server /fault # scope trap-destination number Enters the SNMP trap destination command mode for the specified destination. Four SNMP trap destinations are available. The destination number is an integer between 1 and 4.
Step 4 Server /fault/trap-destination # set enabled {yes | no} Enables or disables the SNMP trap destination.
Step 5 Server /fault/trap-destination # set addr ip-address Specifies the destination IP address to which SNMP trap information is sent.
Step 6 Server /fault/trap-destination # commit Commits the transaction to the system configuration.
This example configures the SNMP trap destination:
Server# scope fault Server /fault # set community-str public Server /fault *# scope trap-destination 1 Server /fault/trap-destination # set enabled yes Server /fault/trap-destination *# set addr 10.20.30.41 Server /fault/trap-destination *# commit Server /fault/trap-destination # show Trap Destination IP Address Enabled ---------------- ---------------- -------- 1 10.20.30.41 yes Server /fault/trap-destination #Sending a Test SNMP Trap Message
Procedure
Command or Action Purpose Step 1 Server# scope fault Enters the fault command mode.
Step 2 Server /fault # scope trap-destination number Enters the SNMP trap destination command mode for the specified destination. Four SNMP trap destinations are available. The destination number is an integer between 1 and 4.
Step 3 Server /fault/trap-destination # sendSNMPtrap Sends a test message to the SNMP trap destination.
Note The trap must be configured and enabled in order to send a test message.