Shelf Manager CLI
Fortinet Technologies Inc.
action> <alert_policy_number> <severity> <IPMB_address> <channel> <sensor_type>
<sensor_number> <event_type> <event_offset> 0 0 0 0 0 0 0 0 0
Each event filter command adds or edits and event filter table entry. Each entry consists of a <entry_number> and a
<filter_action> followed by 19 numeric values, in hexadecimal, encoded according to the definition in table 15-2 of
the IPMI specification version 1.5 (
http://download.intel.com/design/servers/ipmi/IPMIv1_5rev1_1.pdf
).
l
<entry_number>
is the filter entry number. Each entry must have a different number. Adding a second entry
with the same number overwrites the first entry with that number.
l
<filter_configuration>
In this example the filter configuration is ways set to 80 to enable the filter.
l
<filter_action>
In this example the filter action is ways set to 1 to set the action to alert.
l
<alert_policy_number>
In this example the alert policy number is 5.
l
<severity>
In this example the severity is 02 which means information level messages and higher can trigger
traps. Normally you would set severity to 08 for non-critical conditions, 10 for critical conditions, or 20 for non-
recoverable conditions to limit the number of traps sent.
l
<IPMB_address>
is the IPMB address of the FRU for which the alert is generated. See
logical and physical slot numbers, and FRU ids on page 39
l
<channel>
is the channel to match. FF means any channel.
l
<sensor_type>
is the type of sensor. FF means any sensor, F0 means hot swap. See
.
l
<sensor_number>
is the number of the sensor. FF means any sensor.
l
<event_type>
is the event or reading type. FF means any event type.
l
<event_offset>
is the event offset mask. FF FF means any event offset mask.
l
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.
Add filter entry 1 for the FortiSwitch 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 6 for the FortiGate-5005FA2 board in logical slot 6. 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 8C (physical slot 10 in a
5144C chassis), any channel (FF), is for any sensor (FF), is for any sensor number (FF), any sensor offset (FF), any
event type (FF), and any event offset (FF).
clia setpefconfig event_filter 6 80 1 5 02 8C FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 8 for the FortiGate board in logical slot 8. 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 90 (physical slot 10 in a FortiGate-
5144C chassis), 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 6 80 1 5 02 8C FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 10 for the FortiGate board in logical slot 10 (IPMB address 94).
clia setpefconfig event_filter 10 80 1 5 02 94 FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 11 for the FortiGate board in logical slot 11 (IPMB address 96).
clia setpefconfig event_filter 11 80 1 5 02 96 FF FF 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
FortiGate-5144C 6.2.3 Chassis Guide
67
