Owners Manual
SNMP and email alerts
Event lters
To set the platform event lters, use the raw command format. To congure an entry in the lter table:
# ipmitool raw 0x04 0x12 0x6 0x2 0xc0 0x1 0x2 0x2 0x 0x 0x 0x 0x 0x01 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Byte 3 (0x60) – event filter table cmd
Byte 4(0x2) – filter number
Byte 5(0xc0) – filter config(enable)
Byte 6(0x1) – action(alert)
Byte 7(0x2) – policy number
Byte 8(0x2) - event severity(information)
Byte 9(0xff) – slave address
Byte 10 (0xff) – channel number(any)
Byte 11(0xff) - sensor number(any)
Byte 12(0x01) – event trigger(threshold)
The entry 2 is changed after the command, as shown:
# ipmitool pef lter list
1 | enabled, configurable | Any | Any | None | OEM | Any | Alert,OEM-defined | 1
2 | enabled, pre-congured | Any | Any | Information | OEM | Any | Alert | 2
For more information, see the IPMI Specication v2.0 chapter 17.7 Event Filter Table and chapter 30.3 Set PEF Conguration Parameters
Command.
Alert policies and destinations
For more information, see the IPMI Specication v2.0 chapter 17.11 Alert Policy Table and chapter 30.3 Set PEF Conguration Parameters
Command (parameter 9).
LAN destinations
BMC supports SNMP alert destinations. These are SNMP traps. When you set a LAN destination for alerts, the BMC sends an SNMP trap
to the set a destination whenever BMC detects alert conditions. You can setup the SNMP management application on the destination to
receive these SNMP traps; however, setting up the SNMP management station is beyond the scope of this document.
To view alert destinations, use the ipmitool lan alert print command.
# ipmitool lan alert print
Alert Destination : 0
Alert Acknowledge : Unacknowledged
Destination Type : PET Trap
Retry Interval : 0
Number of Retries : 0
Alert Gateway : Default
Alert IP Address : 0.0.0.0
Alert MAC Address : 00:00:00:00:00:00
Alert Destination : 1
Alert Acknowledge : Unacknowledged
Destination Type : PET Trap
Retry Interval : 0
Number of Retries : 0
10
Conguration methods