Sending Out SNMP Traps

From ServersCheck Wiki

Overview

ServersCheck can query SNMP enabled devices such as routers and servers by using a poll-driven approach: they consist of ServersCheck making a specific request that results in action being taken and a response being generated by an SNMP agent.

If you want to integrate ServersCheck with your Network Management System, then another SNMP approach will allow you to do so: SNMP Trap-PDU messages.

In computer science, a trap is simply a set of conditions that a device monitors continuously. If the appropriate conditions occur, the trap is triggered and causes some sort of action to occur. In SNMP, traps are programmed into ServersCheck, and when they are triggered, an SNMP Trap-PDU message is sent to an SNMP Manager to inform it of the occurrence.

ServersCheck SNMP Traps

This feature is only available to Enterprise edition users of the ServersCheck Monitoring Software.

The ServersCheck SNMP traps are built upon the ServersCheck Enterprise OID; which is 1.3.6.1.4.1.25432.

The first digit after ServersCheck's Enterprise OID is the unique identifier of the rule. The last digit is the type of message sent along:

.0 is the last known value (INTEGER)

.1 is the current status of the rule (OCTET STRING); value can be DOWN, OK or WARNING

.2 is the last known error message

.3 is the label of the rule

Configuring ServersCheck SNMP Traps

Go the Configuration, General Settings, and select the SNMP Trap Sending Settings option:

You need then to add three values:

• The IP address of the Network Management System receiving the traps

• The UDP port of to send the traps to (default value is 162)

• The community string used by the Network Management System (default value is public).