Fortinet FortiGate-5060 Chassis Manual page 61

Using the shelf manager CLI
FortiGate-5060 Chassis Guide
01-400-129494-20110912
http://docs.fortinet.com/ • Feedback
<sensor_type> is the type of sensor. FF means any sensor, F0 means hot swap.
See "Sensor types" on page
<sensor_number> is the number of the sensor. FF means any sensor.
<event_type> is the event or reading type. FF means any event type.
<event_offset> is the event offset mask. FF FF means any event offset mask.
0 0 0 0 0 0 0 0 0 are additional settings to add granularity and boolean logic for
selecting particluar events. In this example they are all set to 0 which means they have
no effect.
Example filter entries for a FortiGate-5000-series chassis with a FortiSwitch-5003A
board in logical slot 1 and a FortiGate-5005FA2 board in logical slot 5. The example
also includes an event filter for FRUs at IPMB address 20 (PEMs, Fans, etc). For
clarity the filter entry numbers match the IPMB numbers, but this is not a requirement.
These filter entries set the alert level to 02 which means SNMP traps are generated for
all events. You could raise the alert levels to 10 to only receive traps for critical events.
Add filter entry 1 for the FortiSwitch-5003A board in logical slot 1. The filter entry uses
filter configuration 80, sets the action to alert (1), references alert policy 5, sets the
severity level to 02, is for IPMB address 82 (the first hub slot), any channel (FF), is for
the hot swap sensor (F0), is for any sensor number (FF), any sensor offset (FF), any
event type (FF), and any event offset (FF).
clia setpefconfig event_filter 1 80 1 5 02 82 FF F0 FF FF FF FF
0 0 0 0 0 0 0 0 0
Add filter entry 20 for the FRUs at IPMB address 20 (PEMs, Fans, etc)
clia setpefconfig event_filter 20 80 1 5 02 20 FF FF FF FF FF
FF 0 0 0 0 0 0 0 0 0
To configure the alert policy and string tables
1 Set alert policy table entry 8 with alert policy number 5, policy enabled, alert always
sent, destination channel 1, destination address 2 and alert string selector 7
clia setpefconfig alert_policy 8 5 8 1 2 7
2 Set the alert string selector 7 equal to test alert message.
clia setpefconfig alert_string 7 "test alert message"
Testing the configuration
A simple test of the configuration to make sure the SNMP manager can receive traps.
Since in most cases in this example the event filter is set for any channel and any sensor
any simple state change should trigger a trap. The following steps show to enter a
command to deactivate selected FRUs which will result in a trap being sent.
Note: The format of SNMP traps produced by the shelf manager is specified in the IPMI
Platform Event Trap Format Specification v1.0 document
(http://download.intel.com/design/servers/ipmi/PET100.pdf).
1 Enter the following command to view the state of PEM 1 in a FortiGate-5000 series
chassis.
# clia fru 20 7
20: FRU # 7
Entity: (0xa, 0x61)
Hot Swap State: M4 (Active), Previous: M3 (Activation In
Process), Last State Change
Cause: Normal State Change (0x0)
Generating SNMP traps for system events
33.
61