Why does net-snmp generate an extra request internally?

While testing my 'network simulator' agent, I'm finding that Net-SNMP
appears to be generating an extra (ie. unexpected) getnext request
internally
that gets handed down to agents.

In my environment, I have a MIB variable instance at
1.2.840.10006.300.43.1.3.0
(IEEE8023-LAG-MIB::dot3adTablesLastChanged) and the 'next' variable in the
list is SNMPv2-MIB::sysDescr.0 (at 1.3.6.1.2.1.1.0)
Ie. its on the border from the 1.2.x branch and the 1.3.x branch.

So... if I make a request GetNext(1.2.840.10006.300.43.1.3.0) I get the
answer
for sysDescr.0 like you would expect.

Internally, my agent received that request and answered it,
but then in the same request list, there is another request 'GetNext (1.3)'

What causes this extra request to be inserted?

Since I currently have the following sub-trees in my MIB collection:

1.0...
1.2...
1.3...

I can see it happen when transitioning from the last 1.0.x variable to the
first
variable in the 1.2 branch, and also when transitioning from the last 1.2.x
variable
to the first variable in the 1.3 branch.

Can someone shed some light on whats going on and why?

TIA
Fulko

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p

_______________________________________________
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