The solution is to contact the vendor and let them know there is a bug in the SNMP Agent.
You can use the following KB to roll the IP Domain log and enable the setTrace function for the specific device in question.
This will enable you to see the SNMP Agent responses in the IP domain log file that Smarts is receiving from the device. Avoid doing this when there is a discovery in progress for cleaner log output.
In addition, you can run a tcp dump filtered for the snmp traffic between the IP server and the specific device and provide this data to the vendor.
As mentioned in the cause Smarts expects the SNMP Agent to respond with the details of the requested oid or the following:
NOSUCHOBJECT
NOSUCHNAME
NOSUCHINSTANCE
Workaround:
There is no other workaround for this issue if you want to discover the device via SNMP.
Impact/Risks:
Discovery error generated and device will not be discovered.