Here is a simple example to demonstrate the problem I am having
with the getnext command. Again for some reason when the manager
issues a getnext command to the agent the manager sends a second
request to the agent which then is typically filled with junk or the
next mib's value defined under the parent object. So the first
request is successfull and the second request by the manager is bogus.
I guess the second request is issued by the manager because it still
thinks there are other instances left to get, due to the agent's
response.
Can you please let me know what you are doing on the manager side? A
simple getnext (to what?) or a walk (which subtree?) and so on? Your
script works fine so far on my current and the 2.0.2 version. Please
try to state exactly what you are doing and what the unexpected
results look like.
Juergen