This section contains information on administering the Operations Sentinel Trap Service. It includes the following topics:
Setting up the Operations Sentinel Trap Service (see 15.1)
Understanding the database (see 15.2)
Starting the Operations Sentinel Trap Service (see 15.3)
Stopping the Operations Sentinel Trap Service (see 15.4)
Opening the database (see 15.5)
Configuring Operations Sentinel Servers (see 15.6)
Configuring Operations Sentinel Trap Service (see 15.7)
Configuring Trap Destinations on [UNIX]/Linux (see 15.8)
Using the Windows Application Event Log (see 15.9)
Migrating the database (see 15.10)
The Operations Sentinel Trap Service can receive the SNMP traps from any source and translate the traps into Operations Sentinel event reports, using a flexible, user controlled conversion scheme. No third-party SNMP trap handler is required.
The Operations Sentinel Trap Service conversion scheme lets you specify the event text and other boxes, including the event severity. It allows any kind of event report to be sent, and not just alerts. The Operations Sentinel Trap Service includes a predefined database of traps and corresponding Operations Sentinel events, allowing your site to immediately start using the SNMP trap reporting.
With the event reports created from an SNMP trap by the Operations Sentinel Trap Service, you can attach automated actions to alert events and use the multilevel notification facilities of Operations Sentinel. These automated alert actions can include sending commands to the node that raised the SNMP trap and to resolve the condition that caused the trap. If you prefer to automate the response without raising an alert, you can have commands sent directly to the node that raises the SNMP trap.