[SNMP4J] EngineBoots and EngineTime issue

["M. Joaquín Suárez Chulián"]

Hi.

There is no problem with authentication and encriptation. It was my 
fault. I was using the same engineID in the manger and the agent.

Sorry and thanks.

Joaquin Suarez

El 26/05/2011 13:17, "M. Joaquín Suárez Chulián" escribió:
> Hi Frank,
>
> I have an agent that is built for an embeded target. I know that the 
> agent works properly for the version 3 of the protocol because I use 
> an specific manager for this one.
>
> I need to build a manager using snmp4j library. In fact, I have one 
> that works fine without using authentication, but it fails when I use 
> authentication like MD5 or SHA.
>
> If I use Wireshark with the specific agent the result is something 
> like that:
>
> IP Manager 192.168.20.130
> IP Agent 192.168.20.80
>
> 1    0.000000    192.168.20.130    192.168.20.80    SNMP    get-request
> 2    0.003054    192.168.20.80    192.168.20.130    SNMP    report 
> 1.3.6.1.6.3.15.1.1.4.0
> 3    0.009106    192.168.20.130    192.168.20.80    SNMP    
> get-request 1.3.6.1.4.1.4761.99.11.1.1.0
> 4    0.013181    192.168.20.80    192.168.20.130    SNMP    report 
> 1.3.6.1.6.3.15.1.1.2.0
> 5    0.016548    192.168.20.130    192.168.20.80    SNMP    
> get-request 1.3.6.1.4.1.4761.99.11.1.1.0
> 6    0.021766    192.168.20.80    192.168.20.130    SNMP    
> get-response 1.3.6.1.4.1.4761.99.11.1.1.0
>
> In the third frame, EngineBoots and EngineTime values are differents 
> than EngineBoots and EngineTime values in the fourth frame so, If I'm 
> not mistaken, the manager synchronizes with the agent with the fourth 
> frame and in the next try the communication is possible (EngineBoots 
> and EngineTime values are the same in the frames number 5 and 6)
>
> But I use Wireshark with the snmp4j agents the result is shown below:
>
> 1    0.000000    192.168.20.130    192.168.20.80    SNMP    get-request
> 2    0.003408    192.168.20.80    192.168.20.130    SNMP    report 
> 1.3.6.1.6.3.15.1.1.4.0
> 3    0.058151    192.168.20.130    192.168.20.80    SNMP    
> get-request 1.3.6.1.4.1.4761.99.11.1.1.0
> 4    0.062492    192.168.20.80    192.168.20.130    SNMP    report 
> 1.3.6.1.6.3.15.1.1.2.0
> 5    1.999864    192.168.20.130    192.168.20.80    SNMP    
> get-request 1.3.6.1.4.1.4761.99.11.1.1.0
> 6    2.003975    192.168.20.80    192.168.20.130    SNMP    report 
> 1.3.6.1.6.3.15.1.1.2.0
> 7    4.000730    192.168.20.130    192.168.20.80    SNMP    
> get-request 1.3.6.1.4.1.4761.99.11.1.1.0
> 8    4.005022    192.168.20.80    192.168.20.130    SNMP    report 
> 1.3.6.1.6.3.15.1.1.2.0
>
> From 1 to 4 is the same, but in the fifth frame the manager doen't 
> syncronize with the agent and the communication isn't possible 
> (EngineBoots and EngineTime values are different between agent and 
> manager)
>
> I was looking for a solution but I haven't been able to find one. I 
> don't know if it a bug in the library or not.
>
> I would appreciate your help.
>
> Best regards,
>
> Joaquin Suarez
>