Hi,
According to the SNMP standard GETNEXT (and also GET) request should not
return
errors (an error status).
Instead GETNEXT should skip unaccessible objects and GET should return a
noSuchInstance
exception (or noSuchObject if the object is not supported at all).
Thus, the best way would be to temporaly set the access of non available
objects to NOACCESS.
The rest would then do SNMP4J-Agent.
If you really want to return an error, you may return genErr or
resourceUnavailable.
Best regards,
Frank
Am 15.11.2013 15:29, schrieb m k:
Hello,
In our project, there is a possibility that certain resources may become unavailable, limiting the
values we can offer for polling. Rather than return a cached value or a default value that may
mislead the user into thinking this is the "real" data, we'd prefer to let them now that
the resource can't be retrieved presently. Is there a good way to do this in SNMP4J? I've noticed
the protocol supports a "General SNMP Error", is there a way to deliver this when a value
cannot be polled?
Regardless, if the above approach is not feasible, then is there a standard
practice (sending some default values, etc.)?
Thank you
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
