>>>>> "NT" == Nitin Tiwari <Tiwari> writes: NT> I have two agents running in two different machines. Agent 'A' NT> tries to send a message to agent 'B' and both communicate NT> properly; the problem starts when i restart Agent 'B' and then NT> without restarting Agent 'A' I send a snmpget /snmpset command to NT> Agent 'B'. This time, I am getting a "not in time window". I see NT> that this goes into the usm_check_and_update_timeliness() in NT> snmpusm.c file and fails because it gets the engineid length same NT> for local and remote agents. This is all in SNMPV3.
I'm not sure why you have an agent sending requests to an agent. Is A really an agent or a manager? What *should* happen is when a given SNMP engine receives a not-in-time window for another engine it should update it's internal notion of what the authoritative clock is for the other device and resend. If you don't see that happening, I need to know more about what you are doing in A and B, and what they really are software wise and how you have configured them (have you manually set their engineIDs?) -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
