
Using SNMP Traps
Setting an SNMP Trap alert enables the sending of snmp trap messages to the snmp management station
whenever a peer state changes to Primary, Backup, or Standalone modes. Primary and Backup modes apply to
Equalizer in a failover configuration. Standalone mode is the normal operational state for a single Equalizer not
deployed in a failover pair when it is first booted.
For example, the following sequence of commands creates an snmp trap alert for the touch user that enables trap
messages whenever the local Equalizer (peer Eq_AD1122CC99, which is not in failover) reboots and changes to
Standalone mode:
eqcli > user touch
eqcli user-tou*> alert standalonemode
eqcli user-tou*-alert-tes*> alert_type state_change
eqcli user-tou*-alert-tes*> notify_type snmp
eqcli user-tou*-alert-tes*> object Eq_AD1122CC99
eqcli user-tou*-alert-tes*> object_type peer
eqcli user-tou*-alert-tes*> commit
Creating SNMP Trap Failover Group Alerts
Setting an SNMP Trap alert enables the sending of snmp trap messages to the snmp management station
whenever a Failover Group changes to Primary, Backup, or Standalone modes.
For example, the following sequence of commands creates an snmp trap alert for the touch user that enables a trap
message whenever a failover group (fo_group1 ) changes state. Note that the failover group object name must
be entered as <peername>:<fogroupname>:
eqcli > user touch
eqcli user-tou*> alert fogroupstatechange
eqcli user-tou*-alert-tes*> alert_type state_change
eqcli user-tou*-alert-tes*> notify_type snmp
eqcli user-tou*-alert-tes*> object Eq_AD1122CC99:fo_group1
eqcli user-tou*-alert-tes*> object_type fogrp
eqcli user-tou*-alert-tes*> commit
498
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Kommentare zu diesen Handbüchern