RE: I don't know why the table iterator works well on snmp v1 but it doesn't work on snmp v2c or v3!

Hi...
> What are the access control settings in your snmpd.conf file?
> ==>
> These are the part of the settings.
> ------------
> com2sec private         localhost           private

> rocommunity public
> rwcommunity private
> ------------

Urghh!
No - don't mix "com2sec" and "r?community" directives.
That way madness lies.

For the time being, I'd suggest you move this snmpd.conf file
out of the way, and work with a much simpler one,
containing *just*

     rocommunity public
==> 
I rewrite my snmpd.conf file as you suggested.
Now, it has only 3 lines for access controlling.
--------------------
createUser jupiter MD5 "single pass phrase" AES
rouser jupiter noauth       
rocommunity public
--------------------

> 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
>
> What results/debug output do you get?
> ==>
> The results and debug output are...
> ----
> Error in packet
> Reason: (noSuchName) There is no such variable name in this MIB.
> Failed object: RADFINDER-MIB::rfcEngineAirIFType.1
> ----

Oh!   Not what I expected!
OK - try

      snmpgetnext -v 1  -c public ...   RADFINDER-MIB::rfcEngineAirIFType
      snmpgetnext -v 2c -c public ...   RADFINDER-MIB::rfcEngineAirIFType

What does that give you?
==>
I've got these:
------------
snmpgetnext -v1 -c public localhost   RADFINDER-MIB::rfcEngineAirIFType
snmpgetnext -v2c -c public localhost   RADFINDER-MIB::rfcEngineAirIFType
snmpgetnext -v3 -u jupiter localhost   RADFINDER-MIB::rfcEngineAirIFType
------------
RADFINDER-MIB::rfcEngineAirIFType.1 = INTEGER: WCDMA(30)
RADFINDER-MIB::rfcEngineAirIFType.1 = INTEGER: WCDMA(30)
RADFINDER-MIB::rfcEngineAirIFType.1 = INTEGER: WCDMA(30)
-------------
The results and debug output were fine for these requests.
But, still, I've got the same garbage values for snmptable queries via
v2c/v3.
What should I do?


> When I compare the numbers of get_first_data_point called via v1 and
> v2c/v3, in the v2c and v3 cases, they are exactly same.
> But the number of v1 case is smaller than v2 or v3 cases.
> Is this also normal?

No - but then it's not normal to get different results for v1 queries
compared than v2c/v3 either.

This sounds like a very strange situation all round!
Hence suggesting you simplify things as much as possible.

Dave






------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users