|
|
The EELS daemon can be configured to generate SNMP traps when particular events occur. It is the EELS daemon that generates the SNMP traps.
Configuration information for alarm generation is contained in the send-trap configuration block. The count tag specifies how many traps must be sent each time a specified event occurs. By sending multiple traps, you can be more confident that a trap will arrive at the SNMP management station. This is necessary because SNMP traps are sent using UDP which is an unreliable transport medium.
The interval tag specifies the number of seconds to wait between sending each trap. For example, if count is equal to 10, and interval is equal to 20, then ten traps will be sent twenty seconds apart whenever the specified trap event occurred.
If events occur back to back that cause traps to be sent corresponding to the same send-trap configuration block, then traps will only be sent for the first event. No traps will be sent for the second event. This prevents the network from being flooded with redundant trap information.
The filter tag in the configuration block corresponds to a filter parameter block used to detect events. This filter specification is used in the same way that it is used for the execute-script parameter block.
The type of trap that is sent is configured via the trap-type tag and the SNMP community name via the community tag.
The name of the host to which traps are sent is configured using the hostname parameter.
For more information on alarm generation, see ``Sending SNMP traps using filters''.