Sensors offline after moving to new remote probe

Hi there,

The error indicates that the new Remote Probe is not allowed to gather the data needed for the sensor from the target device. This is because you have to define which exact IPs are allowed able to gather this data.

You'll need to adjust this setting on all your Cisco Devices to the new Probe's IP, PRTG is not able to do this for you as the setting is not within PRTG but rather directly on the target device.

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

While logically this makes sense, I do not think this is entirely true. Some devices on the new probe are working fine, just majority are not. All the devices have the same SNMP server settings. So how are some devices able to read the SNMP data on the new probe with the root probe IP?

Reading through documentation, I thought I read that the sensor data was not held on the remote probes and was still held on the root probe for collection anyway?

For a company that has 10's of thousands of sensors over thousands of devices, it is virtually impossible to make individual changes to work in PRTG. If this is truly the case, this makes PRTG an impossibility to move devices between probes as now admins will need to touch every device to update SNMP settings.

Hi there,

There are some device which allow every incoming IP to query SNMP data, these would work without any configuration change.

That's right, but the monitoring calls are sent from the new Remote Probe's IP.

Please understand that this is not primarily because of PRTG, but rather the SNMP protocol itself allows for this configuration.

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

So to further the questions on the SNMP settings that you are suggesting, I have some devices that have randomly gone offline in our primary probe. I cannot ping from either the probe or switch in either direction from eachother. Ping works otherwise and the device is online.

If I move these devices over to a new probe it comes back online, even without ANY SNMP settings in the switch. If I move it back to the original probe that there actually is SNMP info created, it goes offline.

So seeing this, I am not sure the answer is SNMP device settings on the switch. It seems a good number of switches worked fine on the new probe and mostly Router Sensors that went offline. EX: Ping was fine, but all the other SNMP Health sensors went offline

It seems we are in a no win situation as we created new probes due to inconsistencies seen with the primary, but then ones that work on the Prim dont work on the remote probe and ones that dont work on the prim do work on the remote probe. This just defies all logic.

Hi there,

Thank you for your message.

I think it's a good idea to continue with this topic in a dedicated Support Ticket. You'll get an email shortly.

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

Hello,

I am having the same problem as user PM-Performance, what was the solution given?

Any solution for this issue ? I am seeing the sensors of servers not working after moving to new remote probe.

It can happen for many reasons, if the sensors work when moving them back to the previous probe, it means the new probe doesnt have access to poll these devices, it can be something blocked in the network at a firewall level, it can be that your new probe ip address is not allowed to poll the devices and you need to add the ip to the allow list that some devices have. It will depend on what kind of sensors they are, WMI sensors can be testes with the WMI tester, SNMP sensors with the SNMP tester. And Ping sensors should work if there is network routing from the probe to the target devices.