
Using SNMP Traps
Setting Up SNMP Traps
The Simple Network Management Protocol (SNMP) is an internet standard that allows a management station to
monitor the status of a device over the network. SNMP organizes information about Equalizer and provides a
standard way to help gather that information. Using SNMP requires:
l An SNMP agent running on the system to be monitored.
l A Management Information Base (MIB) database on the system to be monitored.
l An SNMP management station running on the same or another system.
An SNMP agent and MIB databases are provided on Equalizer Models E370LX, and E250GX and above,
implemented for SNMPv1 and SNMPv2c.
A management station is not provided with Equalizer and must be obtained from a third party supplier. The
management station is often used primarily to browse through the MIB tree, and so is sometimes called a MIB
browser. One such management station that is available in a free personal edition is the
iReasoning MIB Browser
,
available from www.ireasoning.com.
A MIB database is a hierarchical tree of variables whose values describe the state of the monitored device. A
management station that wants to browse the MIB database on a device sends a request to the SNMP agent
running on the device. The agent queries the MIB database for the variables requested by the management station,
and then sends a reply to the management station.
SNMP traps are alerts that are tied into the Equalizer Alerts system. They enable an agent to notify a management
station of significant events by way of unsolicited SNMP messages. First, they must be enabled using the CLI
context and then created for each desired alerts. Presently, Equalizer supports the following SNMP traps:
l Server up/down events - Equalizer will triggers these traps when it detects either a server failure or a
response from a failed server.
l Peer state change events - Equalizer will trigger these traps whenever a state change occurs to a peer or
peer interface..
l Failover Group state change events - Equalizer triggers these traps whenever a state change occurs to a
failover group.
Different OIDs (Object Identifier) are used for each item in the above list. The OID identifies a variable that can be
read via SNMP. So, for example, server up and server down events are sent using different OIDs. The text
message sent with the trap tells you exactly what the event was (server up or server down).
The SNMP Trap configuration process includes 4 steps:
I. Set up an SNMP Management Station
II. Enable SNMP
III. Enable SNMP Traps
IV. Creating alerts for the desired traps
494
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentarios a estos manuales