Open gclinch opened 5 years ago
The behavior is desired if you take a look at the actual packets sent over the wire.
When you set non-repeaters to 0 and max-repetitions to 1, it means that the agent response can only contain a single variable binding. And in that case, an extra round-trip is required to determine if the end of MIB view is reached, which leads to the extra line of SNMPv2-MIB::sysORID.10 = No more variables left in this MIB View
.
Of course to avoid confusion, this extra varbind should be ignored, and not returned by bulkCmd
(or bulkWalkCmd
in release 6.0+).
Resolved in release 7.0.2.
This could be similar to #169.
A bulkCmd with maxRepetitions = 1 or (expected number of records+1) causes an additional result to be generated, with the value "No more variables left in this MIB View". I haven't seen this happen for any other value of maxRepetitions.
My test code is at the end, I'm using sysORID simply as a static-length table. The parameter is the maxRepetitions to send:
Problematic:
Fine:
Test code: