Alerts when traps are received from your SNMP devices.
Most SNMP monitoring operations use polling to retrieve data. In this model, the event monitor connects to the device to retrieve the data it requires. The SNMP protocol also supports "traps". Traps work in the opposite direction. With traps, your SNMP gear is configured to detect critical events like hard and soft resets. When one of these events is detected the unit sends a "trap" to one or more systems that it has been configured to notify.
Use the SNMP Trap event monitor to catch incoming traps, filter them based on content and send alerts as appropriate.
This event monitor provides the following options:
Select this option to show a list of all new traps that have been received since the last run. Use the "Limit" option to specify the maximum number that will be included. It's a good idea to set a reasonable limit because traps can often be generated in large numbers when there are significant network issues. Select the format for displaying trap data. The default format strikes a balance between size and legibility, but you can select one of the other available formats if you choose.
With this option selected, the event monitor will take the trap sender's address and perform reverse DNS on it in an attempt to get a host name. This operation can be resource-intensive and we recommend that you leave it off unless host names are required to interpret trap data.
With this option selected, the event monitor will search the available MIBs and attempt to include a description of each trap that is received.
Traps can optionally include variables. With this option selected the event monitor will search the available MIBs and attempt to include a description of the variable and its meaning.
Some traps and variables have very long descriptions spanning multiple lines. Use this option to include only the first line of each description.
Use this option to define the alert level that will be used by default when new traps arrive.
Use this option to define how other traps will be handled by the event monitor. For each exception, specify the Enterprise value, generic trap ID, and specific trap ID.
Use this option to tell the event monitor to discard traps that specified values in the enterprise values. To specify multiple filters, separate them with commas.
Use this option to filter out traps based on the IP address of the agent that sent the trap.
Use this option to filter out traps based on the IP address of the source of the trap.
Each trap includes a generic trap value and a specific trap value. The two of them together can often be used to uniquely identify a trap type. Use this option to filter based on the generic trap value. To specify multiple generic trap values, separate them with commas.
Use this option to filter based on the specific trap value. To specify multiple specific trap values, separate them with commas.
With this option enabled, the event monitor will look at each of the trap variables and skip any traps that do not have one or more of the text strings you specify. To specify multiple text strings, separate them with commas.
This option is the opposite of the previous one. Use it to tell the event monitor to ignore traps that have certain text strings in their extra variables.
With this option selected, each trap record will be searched using the supplied regular expression and traps which do not match will be discarded.
With this option selected, each trap record will be searched using the supplied regular expression and any traps that match will be discarded.
SNMP item names can be obscure and confusing. Use this option to automatically map values to more friendly names. For example, you could map "SNMPv2-MIB::sysDescr.0" to the more friendly "System Description". Click on the checkbox to enable friendly names and specify the substitutions you want FrameFlow to make.
This event monitor does not require authentication.
This event monitor does not generate any data points.
To view the tutorial for this event monitor, click here.
Add a comment