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

One SNMP device not working after moving PRTG

Votes:

0

I recently moved my PRTG installation from one server to another, using the instructions found here:

How can I move/migrate my PRTG installation to another computer

Most things worked straight away, but I'm having trouble restoring the connection with a Powerware UPS, which is also the only device that uses SNMP v1 (all others use v3).

I can ping the device from the PRTG server, and I receive SNMP traps from it, and SNMP traffic to other devices on the same network can traverse the firewall(s), but on this one device I get SNMP error # -2003 in both PRTG and the SNMP Tester software.

I thought maybe it was because I was missing the Powerware MIBs on the new server, but even after re-importing them with the MIB Importer tool I still get the same error.
I have also tried re-creating the device, but when trying to add the Powerware SNMP library sensor(s) it stays on Preparing sensor settings... for a long time and then gives the same error (2003).
I've tried for hours to figure out what may be causing this and I'm not getting anywhere - any suggestions what else to try?

Edit: Improved formatting

error-2003 move prtg snmp snmp-error#2003 snmp-library ups

Created on Jul 9, 2015 1:49:04 PM

Last change on Jul 14, 2015 6:26:06 AM by Luciano Lingnau [Paessler]



Best Answer

Accepted Answer

Votes:

9

Hey Lomax,

I don't know the web interface of your UPC, so i can't give more than "lightweight Information", but i think this can't be the only configuration. I don't say that it is a misconfiguration on the IP-Interface itself (as shown on your screengrab), moreover the SNMP options. SNMP v1 & v2 is working with communities and these communities can be activated to an ip range (ex. 192.168.0.0/24 or 192.168.0.0/24 or also both together :) ) or only to one IP-Adress.

If your "new" PRTG shouldn't have the same IP, than i think this is your Problem.

Check your SNMP options in your UPC (theses one where you can edit the community). I think this is the problem.

Created on Jul 13, 2015 6:50:21 AM



6 Replies

Votes:

4

Hey Lomax,

could it be that your new PRTG-Server is in a another network than the old one? Maybe not the same IP?

Than it could be, that your configured Community on the UPS is only looking for one IP-Adress and not for a IP-Range. You said you got the error on both (PRTG and SNMP Tester), is the last one on the same server (your new PRTG)?

Please check the SNMP config of your UPS, maybe this could help you.

If everything is right, text me here again.

Sascha

Created on Jul 10, 2015 7:15:31 AM



Votes:

0

Thank you Sascha, you're correct.

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

That means that PRTG didn't get any reply from the device, on some devices you can filter the IP addresses that can perform SNMP monitoring (as a security feature). This can lead to results like this when moving PRTG (and using a new IP address on the Server/Probe).

There's a "checklist for SNMP Not Working at this thread:
My SNMP sensors don’t work. What can I do?

Created on Jul 10, 2015 12:03:04 PM by Luciano Lingnau [Paessler]



Votes:

0

Many thanks for your replies! I realise it sounds like it's just some simple configuration error - and it may be that it is - but I have checked all the obvious things such as SNMP community and firewall configuration. Yes, the UPS and the PRTG server are on different subnets (192.168.0.0/24 and 192.168.1.0/24 respectively), but about half the devices I'm monitoring are on the same subnet as the UPS. I am also able to ping the UPS from the PRTG server. As you can see from the screengrab below, the configuration options on the UPS are quite minimal:

I already read the "Checklist for SNMP Not Working" page, and I've tried temporarily disabling the firewall both on the PRTG server and the interconnecting router, with no change. Mysterious!

Created on Jul 11, 2015 2:25:05 PM



Accepted Answer

Votes:

9

Hey Lomax,

I don't know the web interface of your UPC, so i can't give more than "lightweight Information", but i think this can't be the only configuration. I don't say that it is a misconfiguration on the IP-Interface itself (as shown on your screengrab), moreover the SNMP options. SNMP v1 & v2 is working with communities and these communities can be activated to an ip range (ex. 192.168.0.0/24 or 192.168.0.0/24 or also both together :) ) or only to one IP-Adress.

If your "new" PRTG shouldn't have the same IP, than i think this is your Problem.

Check your SNMP options in your UPC (theses one where you can edit the community). I think this is the problem.

Created on Jul 13, 2015 6:50:21 AM



Votes:

0

Thanks Sascha, your answer made it clear that I had to dig deeper in the UPS config, so I enabled Telnet and after looking around in the menus I found the correct option.

Everyone who posted here was right:
The IP address for read access was set to that of the old PRTG server - updating it to the new IP address gave PRTG access to the UPS.
Annoyingly there is no provision for changing this through the web interface, which is what caused all the confusion; had I been presented with the option in the web UI I would have immediately understood it needed changing!

Created on Jul 13, 2015 5:00:59 PM

Last change on Jul 14, 2015 6:22:39 AM by Luciano Lingnau [Paessler]



Votes:

0

Hello Lomax, Thank you for your feedback, it's great to hear that you got it working and thank you again Sascha for your assistance.

Created on Jul 14, 2015 6:24:21 AM by Luciano Lingnau [Paessler]




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.