2009/3/12 Young, Alistair <[email protected]>: > Attaching a packet sniffer it looks like, when the first request is > sent, there's a whole series of exchanges between net-snmp and my other > agent (over a period of around 4 seconds), which culminates in my other > agent returning the requested value.
That sounds quite possible. The "client" (i.e. the proxying system) needs to synchronise with the internal clock on the "server" for the SNMPv3 request to succeed. This is handled automatically, but may well take longer than the timeout for the original management app. > However, by this time, the snmpget > request has returned "NULL". The next request is fine (and seems to > only involve a single get/response pair - presumably net-snmp is now > able to maintain the details of the second agent): One possibility might be to insert a dummy MIB module, which sent a query to the remote system when the proxy server first starts up. From then on, the two should be in sych, and any subsequent requests should work first time. The details are left as an exercise for the student :-) Dave ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ 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
