Use the following checklist if you have problems with Operations Sentinel Trap Service recognizing new or changed trap settings:
Ensure that the values for Agent OID and Trap number in each SNMP trap entry within the Operations Sentinel Trap Service database (SpoTrapService.mdb) match those of the SNMP trap you are trying to handle. If they do not match, the default entry is used instead.
Ensure the Text box is not blank within each alert or log event, unless you do not want an event report generated.
Ensure the correct syntax is specified within the SPO Event Report box.
Ensure the updated database is copied to the Windows system running the Operations Sentinel Trap Service. It is recommended that you stop the Operations Sentinel Trap Service prior to this copy, and restart the service after the copy is complete. See “Starting Trap Service” and “Stopping the Trap Service.”
Sometimes it can be difficult to determine what Agent OID and what Trap number to use. The detailed information displayed for the undefined SNMP trap alert in the Operations Sentinel Console Alerts window should indicate what the Agent OID and trap numbers are. Specify those values in a new entry in the Operations Sentinel Trap Service database.
If the undefined SNMP trap that you are trying to handle contains any of the following trap types, the SNMP is a GENERIC trap, which works differently.
The GENERIC trap types are as follows:
COLD START
WARM START
LINK DOWN
LINK UP
AUTHENTICATION FAILURE
EGP NEIGHBOR LOSS
For the GENERIC traps, you must specify GENERIC in the Agent OID box.