ITM Situations and SNMP traps
John Alvord, IBM Corporation
It is possible to have an ITM situation running [Enterprise via TEMS or Private] and send SNMP traps to event receivers for awareness and management control. There are two limitations compared to Enterprise situations.
Limitations - Logic that SNMP logic does NOT have,
1) Persist=N in Enterprise situations means to delay creating a situation event until it has occurred N times in a row. That can be highly useful for cases where a value is sometimes high and sometimes low and you want to alert only when it stays high. The SNMP logic does not have that control. It sends the SNMP trap when the condition is true the first time.
2) DisplayItem in Enterprise situations means that a Situation Formula evaluation can return multiple results - for example when multiple processes are using more than 10% CPU. The SNMP logic does not have that control. It sends a SNMP trap for the first one in the result set.
Setting up SNMP
The documentation to set up SNMP is in the ITM Administrators Guide .
In quick summary you create a file pc_trapcnfg.xml which defines the targets, the situations and other factors. ["pc" is the product code like ux for Unix OS Agent.] When the agent starts up that file controls the production of SNMP traps.
These are fairly easy to setup. The situation tag includes a mode HY which means send SNMP traps when true and later when not true. The mode RC means to just send true on each evaluation.
At one site where this was used, the work needed at the receiver was that the MIB supplied was insufficient to fully decode the SNMP data. Some logic was needed at the SNMP receiver to recover the data.
This post presents basic information and documentation pointers concerning generating SNMP traps for ITM Situations.
Subscribe and follow us for all the latest information directly on your social feeds: