Dave Shield wrote?
> I'm inclined to amend the snmpget/snmpbulk commands to turn off the
> range validation checks by default.
s/snmpget/snmpgetnext/ ?
Sounds good.
+Thomas
-
Check out the new SourceForge.net Marketplace.
On Wed, 21 Nov 2007 09:42:25 + Dave wrote:
DS> Hmmm... that raises an interesting question.
DS>
DS> Should "snmpgetnext" be applying the range checks at all?
DS>
DS> They make sense for the exact requests (GET and SET), because
DS> if the OID isn't a valid instance according to the MIB defi
On 21/11/2007, Younger Wang <[EMAIL PROTECTED]> wrote:
> Run the command:
> Snmpgetnext -v 1 -c
> 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 sen
unger Wang
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield
Sent: 2007年11月21日 1:01
To: Younger Wang
Cc: [email protected]
Subject: Re: Wrong MIB objects in manpage examples
On 20/11/2007, Younger Wang <[EMAIL PROTECTED]> wro
On 20/11/2007, Younger Wang <[EMAIL PROTECTED]> wrote:
> In snmpcmd, vacmSecurityModel is used in example:
>
> snmpgetnext -c public -v 1 localhost vacmSecurityModel
> SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0."wes" = xxx
> It would make sense to change the example to:
>
> snmpgetnext -c publi
Hi,
In snmpcmd, vacmSecurityModel is used in example:
snmpgetnext -c public -v 1 localhost vacmSecurityModel
SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0."wes" = xxx
I tried many ways using the example, but net-snmp kept saying 'index out
of range'. And I read the MIB SNMP-VIEW-BASED-ACM-MIB:
