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

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

SNMP Tester encounters error and stops.

Votes:

0

Your Vote:

Up

Down

I am trying to get a full walk of my device. If I walk 1.3.6 it walks all the way up to a specific OID and fails every time. For some reason it only has an issue with that one OID. I can walk OIDs after that one just fine. How can I get the snmp tester to continue on error?

Here is partial output:

7/23/2020 3:08:05 PM (28453 ms) : 1.3.6.1.2.1.4.31.1.1.29.2 = "0" [ASN_COUNTER]
7/23/2020 3:08:05 PM (28509 ms) : 1.3.6.1.2.1.4.31.1.1.30.1 = "72813233" [ASN_COUNTER]
7/23/2020 3:08:05 PM (28554 ms) : 1.3.6.1.2.1.4.31.1.1.30.2 = "4294967288" [ASN_COUNTER]
7/23/2020 3:08:05 PM (28604 ms) : 1.3.6.1.2.1.4.31.1.1.31.1 = "72813233" [ASN_COUNTER64]
7/23/2020 3:08:05 PM (28739 ms) : Error: -2008

But if I advance the OID, it works.

----------------------- New Test -----------------------
Paessler SNMP Tester - 20.1.58 Computername: *********
7/23/2020 3:11:46 PM (13 ms) : Device: ************
7/23/2020 3:11:46 PM (18 ms) : SNMP v2c
7/23/2020 3:11:46 PM (24 ms) : Walk 1.3.6.1.2.1.4.31.1.1.32
7/23/2020 3:11:46 PM (66 ms) : 1.3.6.1.2.1.4.31.1.1.32.1 = "1965575388" [ASN_COUNTER]
7/23/2020 3:11:46 PM (122 ms) : 1.3.6.1.2.1.4.31.1.1.32.2 = "0" [ASN_COUNTER]

-2008 error snmp

Created on Jul 23, 2020 8:14:45 PM by  tobybuck (0) 1

Last change on Jul 24, 2020 9:59:53 AM by  Moritz Heller [Paessler Support]



5 Replies

Votes:

0

Your Vote:

Up

Down

It seems like that the device does not answer to this OID and the request runs into a timeout, therefore, the walk stops. You can try to increase the timeout or to use the option "slow tweak" so the device will not be overloaded with SNMP requests.

Created on Jul 24, 2020 10:01:59 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I tried increasing the timeout to 50 then 100. I also tried Slow Tweak. It still fails in the same spot. Is there any way to tell it to skip that one and go on? I tried Manage Engine's snmp tester and it made it past this OID, but your utility is a lot better for clarity of output. Their's leaves a lot to be desired. I would really like to get your's working.

Thank you.

Created on Jul 24, 2020 4:25:08 PM by  tobybuck (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Toby,

You can also try to use the option "Scan Script" and use a SNMP walk script. In this script, you can list all OIDs which should be scanned. In this way, you can define where the tester should start again after the fail. The script could look like this:

walk=1.3.6.1.2.1.25.1
walk=1.3.6.1.2.1.1.3
walk=XXXXXX

Created on Jul 27, 2020 5:59:16 AM by  Moritz Heller [Paessler Support]

Last change on Jul 27, 2020 5:59:33 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks for the reply. I did use the Scan Script but it doesn't continue after the first one fails. It just scans the OIDs I specify and stops. I know there are OIDs after these because I can scan them manually.



Scan Script:
walk=1.3.6
walk=1.3.6.1.2.1.4.31.1.1.31.2
walk=1.3.6.1.2.1.4.31.1.1.32


Output:
<lines deleted>
7/27/2020 3:15:42 PM (95851 ms) : 1.3.6.1.2.1.4.31.1.1.29.1 = "0" [ASN_COUNTER]
7/27/2020 3:15:42 PM (96012 ms) : 1.3.6.1.2.1.4.31.1.1.29.2 = "0" [ASN_COUNTER]
7/27/2020 3:15:42 PM (96162 ms) : 1.3.6.1.2.1.4.31.1.1.30.1 = "448635406" [ASN_COUNTER]
7/27/2020 3:15:43 PM (96310 ms) : 1.3.6.1.2.1.4.31.1.1.30.2 = "4294967288" [ASN_COUNTER]
7/27/2020 3:15:43 PM (96485 ms) : 1.3.6.1.2.1.4.31.1.1.31.1 = "448635406" [ASN_COUNTER64]
7/27/2020 3:15:43 PM (96928 ms) : Error: -2008
7/27/2020 3:15:43 PM (96936 ms) : walk 1.3.6.1.2.1.4.31.1.1.31.2
7/27/2020 3:15:43 PM (97088 ms) : walk 1.3.6.1.2.1.4.31.1.1.32
7/27/2020 3:15:44 PM (97238 ms) : 1.3.6.1.2.1.4.31.1.1.32.1 = "2453515885" [ASN_COUNTER]
7/27/2020 3:15:44 PM (97391 ms) : 1.3.6.1.2.1.4.31.1.1.32.2 = "0" [ASN_COUNTER]

Created on Jul 27, 2020 8:25:49 PM by  tobybuck (0) 1

Last change on Jul 28, 2020 6:11:51 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Please note if you use this option, you can only entere OIDs without an index. Therefore, "1.3.6.1.2.1.4.31.1.1.31.2" does not work.
You can see the OID with result in the walk over "1.3.6.1.2.1.4.31.1.1.32" :
1.3.6.1.2.1.4.31.1.1.32.2 = "0" [ASN_COUNTER]

Please also note that a walk over 1.3.6 makes no sense since this is less than default:
Iso (1) .org (3) .dod (6) .internet (1) .private (4)

Please note that (.dod) means departments of defense and therefore every OID has also .internet (1) and 80% of OIDs also has .private (4).

Therefore, please let me know what you want to achieve. If you want to know the OIDs for your device, I recommend to contact the vendor for a MIB file or google after your device.

Created on Jul 28, 2020 6:18:41 AM by  Moritz Heller [Paessler Support]



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.