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 error # -2003

Votes:

0

Your Vote:

Up

Down

we are facing intermittent issue, for every five minutes the interface is going down and again its coming up .

there is now any fluctuation in link.

Below is the error code .

No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003)

How to overcome this error ?

error-2003 prtg-network-monitor snmp-error#2003

Created on Oct 19, 2015 8:44:19 AM by  SBSnetwork (0) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

Thank you for your KB Post. Such short-time errors on only one device point to an issue on the device actually (otherwise you would see many SNMP Sensors on other devices also showing errors in the same time). There are SNMP Compatibility Options that may help here with such connectivity issues on the SNMP on the target NetApp. It seems the errors are rather sporadic, I would suggest to try using a longer scanning interval here on the SNMP Disk Sensors (usually 5 or 10 minutes is fine for disk sensors). Then you could try working with a longer timeout. It may help, but if the device responds with "No such name..."-error in these cases, there is very little PRTG can do, other than showing you the error. This looks like there is an issue with keeping the SNMP connection towards the target. It seems the connection is quite unstable. Please make sure that the "Retry" is enabled on "Failed Requests" in the "SNMP Compatibility Options" and you can try to slightly increase the "SNMP Timeout" in the "SNMP Credentials"-Settings (but please do not set the timeout higher than the scanning interval). You can also try a "SNMP Delay" of 50 to 100 milliseconds, that helps as well sometimes. http://abload.de/img/snmpsettingsoiqv1.png To verify the issue, you could use our SNMP Tester (https://www.paessler.com/tools/snmptester), run it on the PRTG Host, and perform a "Scan available standard interfaces" against the target device, in the very moment the sensors are in error in PRTG. Do you then see the same errors? Then it really points to an issue on the device.

best regards.

Created on Oct 20, 2015 12:06:52 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Still we are facing the same issue . Can anyone help us on this error .

Created on Oct 26, 2015 11:36:58 AM by  SBSnetwork (0) 1



Votes:

0

Your Vote:

Up

Down

Hello there,

What happens when you do an interface scan using our SNMP-Tester when this error occurs?

Kind regards.

Created on Oct 27, 2015 3:31:21 PM by  Erhard Mikulik [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.