On 21/11/2007, Younger Wang <[EMAIL PROTECTED]> wrote: > Run the command: > Snmpgetnext -v 1 -c <community> <IP> > SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0."wes" > SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0.wes: > (Index out of range: 0 (vacmS ecurityModel)) > Get-Next was never sent out, because it found 0 invalid according to the MIB.
Hmmm... that raises an interesting question. Should "snmpgetnext" be applying the range checks at all? They make sense for the exact requests (GET and SET), because if the OID isn't a valid instance according to the MIB definitions, then the agent can't possibly process the request successfully. But that's not true for GETNEXT and GETBULK. Even if the OID doesn't (and can't possibly) match a valid instance, the agent should still return the next varbind that *is* valid. I'm inclined to amend the snmpget/snmpbulk commands to turn off the range validation checks by default. What do other people think? Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
