What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

SNMP trap reciever bind variables

Votes:

0

I'm just a beginner with PRTG. I configured SNMP Trap Receiver and it works (test SNMP trap notifications passed). But I have problem with my real SNMP trap. It is snmp version 1 and contains bind variables in its body. I catch snmp packet by Wireshark, here it is:

3704	623148.637157	192.168.0.1	192.168.0.2	SNMP	162	trap iso.3.6.1.4.1.232 1.3.6.1.4.1.232.1 1.3.6.1.4.1.232.2 1.3.6.1.4.1.232.3 1.3.6.1.4.1.232.4

You see, it has the main root iso.3.6.1.4.1.232 and some multiple variables, for example:
1.3.6.1.4.1.232.1 - server name (for example: "MyServer")
1.3.6.1.4.1.232.2 - server sensor name ("file share")
1.3.6.1.4.1.232.3 - server senasor status ("Error")
1.3.6.1.4.1.232.4 - status description ("file was modified")

For me it is important to get and work with all this messages _together_. Is it possible to do this, using PRTG? What is yhe OID value syntax in this way? The only one, I've get is _separated_ messages with different OID values listening.

prtg8 snmp-trap snmptraps

Created on Jun 15, 2011 12:57:57 PM

Last change on Jun 15, 2011 3:26:14 PM by Torsten Lindner [Paessler Support]



2 Replies

Votes:

0

Hello,

I'm afraid as PRTG needs the exact OIDs of a variable binding you would have to use multiple Trap Sensors.

best regards.

Created on Jun 15, 2011 3:26:53 PM by Torsten Lindner [Paessler Support]



Votes:

0

It's a pity, separated OID value without other variables is pointless for me in this case (due to my previous example, for 1.3.6.1.4.1.232.3 I'll get trap "Error", which really means nothing without understating on what system it happened). OK, I'll try to find smth to resolve this problem.

Created on Jun 17, 2011 10:53:51 AM




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.