When querying a table at end of mib is reached, the last __send_sync_pdu will return a SNMP_ERR_NOSUCHNAME error, and netsnmptable sets netsnmp.Session.Error* accordingly. However this situation must not (always) be considered as error, it just means there are no further rows in the table.
There are multiple issues / things to figure out:
__send_syncpdu returns ambiguous value (meaning either STAT or SNMPERR)
error-status = SNMP_ERR_NOSUCHNAME is the way of reporting "End of MIB" in SNMPv1. Can it always be considered OK (end of table)? How about the other SNMPERR* codes?
SNMPv2 agents may report endOfMibView as "exception value" per variable binding, see RFC3416. How is the error-status set in this case?
When querying a table at end of mib is reached, the last __send_sync_pdu will return a SNMP_ERR_NOSUCHNAME error, and netsnmptable sets netsnmp.Session.Error* accordingly. However this situation must not (always) be considered as error, it just means there are no further rows in the table.
There are multiple issues / things to figure out: