Hi All, In our solution, we have sub-agent and which registered with master agent netsnmpd 5.5 for some standard MIB for some sub-range (say for some rows in ifTable MIB). We use range_subid (10) and range_ubound (15) parameters from netsnmp_handler_registration structure. Every things work fine upto 15 columns in ifTable (range_ubound =15). Sub-agent can register chunk subid correctly and snmptable can show sub-agent rows with other rows from master agent in ifTable.
But if we registered with range_ubound = 22 (max column in ifTable i.e. upto column ifSpecific), 1) sub-agent can register the MIB correctly (we can see using handler::register token log and tcpdump). 2) Then when we query for snmptable (snmptable -v2c -c public localhost ifTable), netsnmpd sends GetNext-PUD OID (ok), 3) Then agentX replies with value in 1st request (which is ok), 4) But in next response time agentX does NOT set value-representation endOfMibView. 5) So netsnmpd keeps on querying with same OID again and again, since agentX does not set endOfMibView in response and the query is going to forever loop. But if we do not register as sub-range (chunk registration) and register whole ifTable MIB, the snmptable query for ifTable works fine for all columns. So like to know whether there is any known issue in agentX lib 5.6 regarding endOfMibView when chunk registration (range_ubound) exceeds some MAX value (in case 15)? In yes, whether there is any workaround for this issue? Thank you in advance. Regards, Nilanjan
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
