Using traps

A trap is an OID that is sent by an SNMP agent when a particular event occurs. Traps are initiated by the SNMP agent and can be detected by SNMP management software, which can then either deal with the event directly or query the SNMP agent for more information.

To receive traps, you must configure the SNMP service. The SNMP service will receive the trap information and then forward it on somewhere; however, by default, this is nowhere, so any trap listeners you have running will not detect anything. The following steps show how to configure your SNMP Service to send traps to your computer.

To configure the SNMP service

Right-click My Computer and choose Manage.
In the left pane, double-click Services And Applications.
In the left pane, double-click Services.
Locate SNMP Service in the list of services in the right pane, right-click it and choose Properties.
Click the Traps tab.
Click Add.
In the SNMP Service Configuration window, type localhost in the text box and then click Add.
Click OK.

SQL Anywhere SNMP Extension Agent traps

The SQL Anywhere SNMP Extension Agent sends a trap whenever a connection is dropped by the database server. The OID of this trap is 1.3.6.1.2.1.39.2.1.

If you are using database mirroring, and the SQL Anywhere SNMP Extension Agent connection to the database server drops, every 30 seconds the SQL Anywhere SNMP Extension Agent attempts to reconnect to the database server. When the agent reconnects, if it finds that it is connected to a different database server (as determined by the ServerName property), then it sends a trap with the OID 1.3.6.1.4.1.897.2.6.3, and the database ID from the sasnmp.ini file. In this case, the SQL Anywhere SNMP Extension Agent was connected to the primary database server, which went down, and now the mirror server is acting as the primary server. See Introduction to database mirroring.

The only other traps sent by the SQL Anywhere SNMP Extension Agent are dynamic traps. See Creating dynamic traps.

Creating dynamic traps

Discuss this page in DocCommentXchange.