New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

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

Free PRTG
Download >>

 

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

 

Top Tags


View all Tags


What to do about "Could not find a table row matching the index you specified when adding the sensor

Votes:

0

Your Vote:

Up

Down

Hello,

So recently I started monitoring a few Cisco WLC's using the template provided in the relevant kb post. Everything seemed to be working quite well at first. However, over last weekend the error "Could not find a table row matching the index you specified when adding the sensor" occurred about a 100 times. All sensors eventually returned to a normal state. I've encountered the same problem with the monitoring of the VPN tunnels of a checkpoint firewall using a custom snmp table. When I keep on rescanning the sensor manually, the error eventually goes away,.

The weird thing is that I also use around 150 sensors (snmp custom table) per F5 load balancer to monitor things like virtual servers, pool members etc. without experiencing the same error.

Some more info: License: PRTG Unlimited Sensors: 5100 Hardware: VM 16 GB Ram 8 CPU cores SNMP: V3

Scanning Interval WLC AP: 10 minutes Scanning Interval Firewall: 120s

Thank you.

error-pe247 prtg snmp-custom-table

Created on Jul 15, 2019 7:15:23 AM by  Netwerkbeheerder01 (0) 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hi there,

I am afraid that there is no real solution to that :(

For PRTG it is an error that should be reported to the user, as PRTG is unable to retrieve the data. The only workaround, which would require some work, is to write a custom script (e.g. in PowerShell) that queries the data and ignores these errors:
https://www.paessler.com/manuals/prtg/exe_script_sensor
https://www.paessler.com/manuals/prtg/exe_script_advanced_sensor

Best regards.

Created on Jul 16, 2019 7:50:16 AM by  Dariusz Gorka [Paessler Support]



3 Replies

Votes:

0

Your Vote:

Up

Down

Hi there,

At the times, when the sensors throw these errors, are you able to manually walk the monitored OIDs via our SNMP Tester?
https://www.paessler.com/tools/snmptester

Best regards.

Created on Jul 15, 2019 8:49:41 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Dariusz,

I've tried what you suggested and indeed I am not able to walk the monitored OID's when this error occurs. Which is quite a shame, because the monitored things do indeed come back up eventually and then they are reachable by snmp-walk at the same index still.

The only solution I see at the moment is to somehow disable error PE247, but I have no idea if this is possible. Right now I am using a http notification trigger to immediately acknowledge when the sensor goes into an error state. Obviously this is not ideal, because I am not able to discriminate between error PE247 and all other events that cause the error to happen. A more suitable solution would be preferred, if there is any.

Thanks.

Created on Jul 16, 2019 6:59:42 AM by  Netwerkbeheerder01 (0) 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hi there,

I am afraid that there is no real solution to that :(

For PRTG it is an error that should be reported to the user, as PRTG is unable to retrieve the data. The only workaround, which would require some work, is to write a custom script (e.g. in PowerShell) that queries the data and ignores these errors:
https://www.paessler.com/manuals/prtg/exe_script_sensor
https://www.paessler.com/manuals/prtg/exe_script_advanced_sensor

Best regards.

Created on Jul 16, 2019 7:50:16 AM by  Dariusz Gorka [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.