Event Name Information

---

Event name is used in resolving the %u variable. The trap name is used in resolving the %(trapname) variable. The name of the trap is exactly the same string that appears between the parentheses in a WhatsUp Gold log line referring to a trap. This can be an OID, a name (translated from mib.txt/traps.txt) or a trap major/minor number, or some combination of them.

For example:

coldstart specialmib-6.27
anotherspecialmib.1.2.3.5-6.2031
org.9.83.121.115.109.111.110.76.111.103-6.2031

Exactly what appears here will depend on what was in your mib.txt and traps.txt at the moment the trap was generated. WhatsUp Gold does its best to present the most "translated" name it can. A particular piece of equipment might generate 6 different traps, with the following names that can be seen in the log file when the appropriate MIB has NOT been compiled:

enterprises.3332.30.100.6-6.2
enterprises.3332.30.100.4-6.2
enterprises.3332.30.100.5-6.2
enterprises.3332.30.100.3-6.2
enterprises.3332.30.100.2-6.2
enterprises.3332.30.100.1-6.2

However, after compiling the MIB, the names might be logged like this:

ipswitch-prd-bot-amp1-high-trap
ipswitch-prd-bot-audio-high-trap
ipswitch-prd-bot-door-trap-tripped
ipswitch-prd-bot-airflow-traps-6.2
ipswitch-prd-bot-humidity-high-trap
ipswitch-prd-bot-temperature-high-trap

Knowledge of how names are derived helps with understanding how to use On Event when configuring alerts.

More details for On Event (regarding SNMP Trap events)

The alert will be generated based on what is currently being logged in the SNMP log. Thus, using "enterprises.3332.30.100.6-6.2" will work when the MIB is not compiled. And if the MIB is compiled later, this string will result in NO alerts. Based on the above example, it must be changed to "ipswitch-prd-bot-amp1-high-trap" in order to give the desired single alert again.

Ipswitch, Inc. http://www.ipswitch.com

©Ipswitch 2003