2 of 2 people found this helpful
"Configure" is usually an indication that the address is incorrect. Check the PI message log on the computer hosting the PI-SNMP interface for more detail. Verify that the tag has precisely the same format that you are using in OiDVieW or Net-SNMP.
First off, I would double check the tag configuration and make sure that the OIDs are correct. You can then edit the Location5 of the tags which will enable tag-level debugging.
From the User Guide:
You do not need to stop and restart the interface after changing location5. Note that the interface takes up to two minutes to detect changes to point configuration.
With the additional debugging, you should be able to see where it fails. If possible, you may want to restart the interface to cause the interface to make a connection to the device and print out the error. If you can't restart the interface, then you can simply wait and then consult the SDK logs.
Feel free to share part of your logs here, if you don't fully understand the errors being thrown or contact Tech Support
Thank you for your suggestions. I just realized that the indexes of the OIDs relative to the hrProcessorLoad were wrong; editing the OIDs i realized that also the other "configure" have disappeared automatically.
Little OT about this protocol, I noticed a reindex in the CPU related OIDs after a reboot of the pc, do you know the reason why this happens? Is there any way to keep always the same indexes?