On 2 May 2012 10:20, Giuseppe Modugno <g.modu...@elettronika.it> wrote: > Robert suggested to use SNMP_ERR_RESOURCEUNAVAILABLE in response to GET > requests of variables related to malfunction hardware sub-sections. > > Recently I was reading RFC 3416 (Version 2 of the Protocol Operations > for the Simple Network Management Protocol (SNMP)) where there is the > explanation of resourceUnavailable error. It seems it should be used in > answers to SET requests, and not GET. It seems the genError is a better > error code for GET response messages.
Yes - having looked at the RFC, I would tend to agree. resourceUnavailable is only relevant when processing a SET request. For problems encountered when processing a GET request, genErr is the more appropriate error. (You could perhaps make a case for returning noSuchInstance, but genErr is probably less misleading) Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
