I think, before create a new row you need to get a valid index with:
dot1qNextFreeLocalVlanIndex
--- On Tue, 12/20/11, Dave Shield <d.t.shi...@liverpool.ac.uk> wrote:
> From: Dave Shield <d.t.shi...@liverpool.ac.uk>
> Subject: Re: noCreation Error when trying to set VLAN on a switch
> To: basil.jos...@wipro.com
> Cc: net-snmp-coders@lists.sourceforge.net
> Received: Tuesday, December 20, 2011, 6:54 AM
> On 20 December 2011 11:41,
> <basil.jos...@wipro.com>
> wrote:
> > When I tried an snmpwalk on CISCO 2800, l got this.
> >
> > [root@localhost ~]# snmpwalk . . .
> dot1qVlanCurrentTable
> > Q-BRIDGE-MIB::dot1qVlanFdbId.0.1 = Gauge32: 0
> > Q-BRIDGE-MIB::dot1qVlanFdbId.0.2 = Gauge32: 0
> > Q-BRIDGE-MIB::dot1qVlanFdbId.0.28 = Gauge32: 0
>
> Take a look at the definition of dot1qVlanCurrentTable
> In particular, the INDEX clause:
>
> INDEX {
> dot1qVlanTimeMark, dot1qVlanIndex }
>
> There are two indexes listed for this table, so there are
> two
> index values for each entry.
>
> Now look at the definition of dot1qVlanStaticTable
> This has
>
> INDEX { dot1qVlanIndex }
>
> One index, hence one index value.
>
>
>
> > [root@localhost ~]# snmpset . . .
> dot1qVlanStaticName.4 s vlan4
> >
> dot1qVlanStaticRowStatus.4 i 4
> >
> > Error in packet.
> > Reason: commitFailed
> > Failed object: Q-BRIDGE-MIB::dot1qVlanStaticName.4
> >
> >
> > Does this commitFailed, mean something?
>
> It means it didn't work :-)
>
>
> I would repeat my advice to talk to Cisco about this.
> They know more about their kit than we do.
>
> But a quick look at the definition of the
> dot1qVlanStaticTable
> shows three other column objects, which you haven't given
> a value for. It might be worth specifying
> these as well.
>
> Alternatively, you could try using createAndWait(5)
> instead
> of createAndGo(4).
>
>
>
> >>The Net-SNMP agent doesn't support the
> Q-BRIDGE-MIB, as far as I know.
> >>So trying to SET elements of this MIB simply won't
> work.
> >
> > So its better to stop trying with Net-SNMP agent,
> isn’t it?
>
> Correct.
>
> > To be clear, I am asking; you didn’t mean that
> snmpset can’t be used for
> > this task, right?
> >
> > You meant that the snmpd is not capable.
>
> Exactly.
> The Net-SNMP *agent* doesn't support the Q-BRIDGE-MIB.
> I.e the Net-SNMP 'snmpd' program.
>
> The "snmpset" command is simply generating a suitable SNMP
> request
> packet - it can do this with no problem, and doesn't need
> any special code.
> The bulk of the work for supporting a new MIB is always in
> the agent.
>
> Dave
>
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app
> development. Create
> new or port existing apps to sell to consumers worldwide.
> Explore the
> Intel AppUpSM program developer opportunity.
> appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> _______________________________________________
> Net-snmp-coders mailing list
> Net-snmp-coders@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
