We are using
NET-SNMP 5. 1. 1.
Our test mib
contains the following MIB objects.
1. Scalars Group
(contains five objects) =============>registered with NET-SNMP Library using
scalar_group (netsnmp_register_scalar_group())helper
2. TableOne (three
columns, but no rows created) =====>registered with NET-SNMP Library
using table.c (netsnmp_register_table()) helper
3. TableTwo (three
columns, but no rows created)
=====>
----- do -----
4. TableThree (three
columns, but no rows created)
=====> -----
do -----
5. TableFour (three
columns, but no rows created)
=====> -----
do -----
6. TableFive (three
columns, Two rows created)
=====>
----- do -----
We are observing
following misbehaviors.
1. GETNEXT on the
last scalar object:
NET-SNMP Library calls the table handlers in the following order.
a. getnext on table-one (our application returns
SNMP_NOSUCHINSTANCE)
b. getnext on table-two (our application returns
SNMP_NOSUCHINSTANCE)
c. getnext on table-three (our application returns
SNMP_NOSUCHINSTANCE)
d. getnext on table-two (our application returns
SNMP_NOSUCHINSTANCE)
e. getnext on table-three (our application returns
SNMP_NOSUCHINSTANCE)
f. getnext on table-three (our application returns
SNMP_NOSUCHINSTANCE)
g. getnext on table-four (our application returns
SNMP_NOSUCHINSTANCE)
h. getnext on table-five (our application
returns valid values)
We are not
able to understand, the iterations c-->d, d--->e, and e-->f. Did
anybody face this kind of problem? When we searched in the mail archives,
we found a message about infinite loop in getnext processing. But, that
was way back in 2001. Are we missing something? Any light on
this issue will be greatly appreciated.
2. GETNEXT on the
non-existing scalar object
Above behavior repeats in infinite loop.
Please help us.
Thanks
Mahesh
