[SNMP4J] Problem with SNMP V3 MD5/DES

[Frank Fock]

Jackie and me analyzed the problem and it turned out
to be simply a too short timeout. When changing the
security level from authNoPriv to authPriv one should
consider increasing the timeout value, because encryption
of the SNMP PDUs takes CPU time and therefore could
cause delays.

Best regards,
Frank


Frank Fock wrote:

> OK, then it could be an interoperability problem. Could you
> please use Ethereal to log the exchanged UDP packets and
> then try the same with NET-SNMP? That would be great!
> (You can send me the Ethereal logs on private Email)
>
> If the NET-SNMP snmpgetnext can retrieve data, then it
> might be because they are using a different time synchronization
> algorithm. When we can compare the two logs we might be
> able to find out, why and how your agent is different.
>
> Thanks in advance,
> Frank
>
> Jackie Cheng wrote:
>
>> Frank,
>>
>> Download v1.0.4b. Same result.
>>
>> --Jackie
>>
>> ________________________________
>>
>> From: Frank Fock [mailto:fock at agentpp.com]
>> Sent: Mon 12/6/2004 11:37 PM
>> To: Jackie Cheng
>> Cc: snmp4j at agentpp.org
>> Subject: Re: [SNMP4J] Problem with SNMP V3 MD5/DES
>>
>>
>>
>> Hi Jackie,
>>
>> Please try  v1.0.4b. It will most likely fix the problem.
>>
>> Best regards,
>> Frank
>>
>> Jackie Cheng wrote:
>>
>>  
>>
>>> Hi Frank,
>>>
>>> Thanks for the promptly reply.
>>>
>>> The command I gave is like "java SnmpRequest -x DES -X password -D 
>>> DEBUG -p GETNEXT  -v 3 -a MD5 -A password -u jackie 192.168.151.55 
>>> 1.3.6.1.2.1". Is it possible to have 2 instances of SNMPs in this 
>>> case? (I run it in command line and one at once.)
>>>
>>> I downladed it 2 weeks ago and the "change.txt" contains this line 
>>> "[2004-10-13] Version 1.0.3a:". Therefore, I think I am using the 
>>> latest version.
>>>
>>> Thanks
>>>
>>> --Jackie
>>>
>>> -----Original Message-----
>>> From: Frank Fock [mailto:fock at agentpp.com]
>>> Sent: Monday, December 06, 2004 3:43 PM
>>> To: Jackie Cheng
>>> Cc: snmp4j at agentpp.org
>>> Subject: Re: [SNMP4J] Problem with SNMP V3 MD5/DES
>>>
>>>
>>> Hi Jackie,
>>>
>>> Are you using the latest SNMP4J version?
>>> From the log it seems that the time synchronization fails. This can 
>>> be caused by two managers (Snmp instances) using the same engine ID.
>>>
>>> Best regards,
>>> Frank
>>>
>>> Jackie Cheng wrote:
>>>
>>>
>>>   
>>
>>
>>
>>
>>
>>
>>  
>>
>
>
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://p15141779.pureserver.info/mailman/listinfo/snmp4j
>