No such instance (SNMP error 223) after reboot of Dell Poweredge Server

Hello Sven,

Since you use an older PRTG version please update first to the latest version of PRTG in order to see if the issue still remains, using the Auto-Update. Alternatively you can download the software from our Paessler Service Center using your registered email and password.

Once you have downloaded the latest version, you can install it directly over the version currently running. The configuration and database will not be affected by installing the newer version over the old and the configuration is automatically backed up before this process.

I updated PRTG to version v16.2.24.4470 but still have the same problem. After a couple of dayes I get the status " No such instance (SNMP error 223)" in PRTG. When I remove the sensor and add it the problem is gone for a couple of days. Sometimes problem can be forced by rebooting the server but not always.

I have this problem on several Dell PowerEdge Servers (all R730 family)

Hello Sven,
thank you for your reply.

The No such instance (SNMP error 223) message is directly related to changing SNMP Indexes. This means that the data contained in the SNMP Agent of the device was "re-ordered" and PRTG is no longer able to identify the data it was originally monitoring. The message No such instance is the reply of the device when PRTG asks for the OID that it was monitoring until now and the device tells PRTG that "this 'address' is not valid/nonexistent".

The Dell Poweredge sensors can be used both via the iDRAC interface or the Operating System's Interface (with the appropriate software installed). If one of these ways if giving you problems, try the other one. If that also fails please contact us via a support ticket so that we can check the exact data that the device provides via SNMP before and after the result, this will allow us to tell you what changed and you may be able to contact Dell with this information and ask for workarounds/fixes.

Best Regards,

OK, they were configured via the Idrac. I have now reconfigured them via the OS interface. Will keep you informed if this solves the problem.

Hello,

We have the same issue with this sensor on two of our Dell PowerEdge R730xd monitored through iDrac.

But we do not have restarted those servers, sensors were working right then they fall to state "No such instance (SNMP error 223)". One since 18 hours, the other since 8 hours.

Using Open Manage agent is not an option for us, cause we have bought idrac licenses to do out-of-band hardware monitoring.

Is there a way to tell PRTG to automatically update his lookup index as for device's network interfaces (Automatically update port name and number for SNMP Traffic sensors when the device changes them) ?

Regards.

Hello klmj,
thank you for your post.

I'm afraid that the Poweredge Health sensors are a lot more complex than the SNMP Traffic Sensors, as of now we're not able to track changing indexes in these sensor's I'm afraid.

If your device's indexes are changing during regular operation this could be a firmware/software issue in the SNMP Implementation, those indexes shouldn't change randomly. You might want to contact dell to discuss your case.

Feel free to contact us via a support case and we'll be able to provide instructions on how to run a "Walk" test to check the current SNMP Data, you can then compare that result with the result of a new test the next time the sensor fails again, this will allow you to spot what changed (and may tell us more about as to why it changed).

Best Regards,
Luciano Lingnau [Paessler Support]

Hello. We have this issue too. PRTG version 16.3.27.6636+ (preview), lots of Dell servers (R720, R730, R620 and some others, all thru iDrac interfaces), iDrac version 2.30.30.30. System being rebooted causes SOME disk sensors to show:

Hello qurvax,
thank you for your KB-post.

Essentially "The disk with serial number <s/n> could not be found" means that the unique serial number used to identify this disk is no longer present. This would be expected for instance when a disk is replaced.

Please contact us via a support ticket, this will allow us to troubleshoot the actual data expected by the sensor and returned by your iDrac's to check out what's causing the sensors to fail.

Best Regards,
Luciano Lingnau [Paessler Support]