Is it possible to send SNMP traps using PRTG?

Up

0

Down

I would like to send SNMP traps as notifications, so that my trap receiver can process them. Is this possible?

notifications receiver sensor snmp traps

Created on Feb 23, 2010 1:40:15 PM by  Patrick Hutter [Paessler Support] (4,804) 3 2

Last change on Feb 26, 2010 9:01:46 AM by  Daniel Zobel [Paessler Support] (9,594) 3 3


1 Reply

Accepted Answer

Up

0

Down

Documentation of SNMP Traps Sent by PRTG

Beyond including a SNMP trap receiver sensor, PRTG Network Monitor 7 (as of V7.1) includes the option to trigger notifications used to send SNMP traps to a computer where a trap receiver is listening. Trap receivers store these messages for later analysis and/or forward traps to the administrators using other means of alerting.

Setup of SNMP Trap Notifications

To activate a SNMP Trap notification in PRTG you must navigate to the settings of a notification, enable "Send SNMP Trap" and then supply the following fields:

  • "Host/IP-address" and "Port" (usually port 162) of your trap receiver.
  • "Community string" (usually "public").
  • A value of your choice for the field "Message ID". On the trap receiver this value will enable you to filter messages from PRTG.
  • A string of your choice for the field "Message". You can use PRTG's standard placeholders, they will be substituted during runtime, just the same as in other notifications.
  • In the field "Agent IP" you can supply an IP address to be used for sending the trap (or leave this field blank to automatically use the IP address of the computer running PRTG).

Contents of SNMP Traps Sent by PRTG

SNMP traps sent by PRTG allways use SNMP V1 format. The following OIDs will be included in the trap:

  • 1.3.6.1.4.1.32446.1.1.1: MessageID (as defined by the user in the Field "Message ID")
  • 1.3.6.1.4.1.32446.1.1.2: An integer representing the event that triggered the notification:
    • 0 = State ended
    • 1 = State started
    • 2 = Volume reached
    • 3 = Speed not reached
    • 4 = Speed reached
    • 5 = Threshold not reached
    • 6 = Threshold reached
    • 7 = Value changed
  • 1.3.6.1.4.1.32446.1.1.3: The state of the object:
    • 0 = None
    • 1 = Unknown
    • 2 = Collecting Data
    • 3 = Up
    • 4 = Warning
    • 5 = Down
    • 6 = No Probe
    • 7 = Paused by User
    • 8 = Paused by Dependency
    • 9 = Paused by Schedule
    • 11 = Paused by License
    • 12 = Paused until
  • 1.3.6.1.4.1.32446.1.1.4: The message text of the notification as defined by the user.

Created on Feb 23, 2010 1:55:05 PM by  Patrick Hutter [Paessler Support] (4,804) 3 2

Last change on Feb 23, 2010 5:15:37 PM by  Daniel Zobel [Paessler Support] (9,594) 3 3


Please log in or register to enter your reply.

Disclaimer:The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

Top Tags


View all Tags

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions! Learn more