2009/6/24 김은영 <keyofm...@radiantech.net>:
> There are 3 tables in my MIB and I implemented the sub-agent to retrieve
> these tables through the table iterator helper. (mib2c.iterate.conf)
>
> When I get the table via snmp v1, it works well.
>
> But if I try to get those via snmp v2c or v3, the values of the first 2
> tables are destroyed and the last table is fine.
Hmmm... that doesn't really make sense.
When you say the first two tables are "destroyed",
do you mean that the the contents are actually removed
(i.e. a subsequent v1 walk also fails), or is it simply
that you can't see them using v2c or v3?
What are the access control settings in your snmpd.conf file?
> The followings are the result of snmptable operation via v1
> and the log from the sub-agent that I implemented.
I would suggest that you investigate this problem using a
simpler query. Try
snmpget -v 1 ..... RADFINDER-MIB::rfcEngineAirIFType.1
snmpget -v 2c ..... RADFINDER-MIB::rfcEngineAirIFType.1
(ignore SNMPv3 for now - concentrate on why v1 works but v2c doesn't).
What results/debug output do you get?
> Why are get_first_data_point and get_next_data_point
> called so many times like this?
That's normal.
"snmptable" actually sends a sequence of GETNEXT requests,
one for each entry in the table.
For *each* GETNEXT request, the agent will call 'get_first_data_point' (once)
followed by 'get_next_data_point' (once per row of the table)
During a complete walk, this adds up to a large number of invocations.
Dave
------------------------------------------------------------------------------
_______________________________________________
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
