On 12/20/11, Dave Shield <d.t.shi...@liverpool.ac.uk> wrote:
> On 20 December 2011 11:41,  <basil.jos...@wipro.com> wrote:
>> [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.

Cisco TAC is unbelievably bad at anything snmp related.  If you do
open a service request and the answer isn't already somewhere on
cisco.com don't expect much from them..
(but to give credit where credit is due - I've stumbled across the
answer to my question on cisco.com months after the SR was closed
enough times that they apparently do keep a list of unresolved Qs for
future work)

> 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).

& if those don't work I'd try polling dot1qNextFreeLocalVlanIndex and
using that answer as the index for the dot1qVlanStaticTable entries:

dot1qNextFreeLocalVlanIndex OBJECT-TYPE
    SYNTAX      INTEGER (0|4096..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The next available value for dot1qVlanIndex of a local
        VLAN entry in dot1qVlanStaticTable.  This will report
        values >=4096 if a new Local VLAN may be created or else
        the value 0 if this is not possible.

        A row creation operation in this table for an entry with a local
        VlanIndex value may fail if the current value of this object
        is not used as the index. Even if the value read is used,
        there is no guarantee that it will still be the valid index
        when the create operation is attempted - another manager may
        have already got in during the intervening time interval.
        In this case, dot1qNextFreeLocalVlanIndex should be re-read
        and the creation re-tried with the new value.

        This value will automatically change when the current value is
        used to create a new row."
    ::= { dot1qVlan 4 }


 But I might be veering off into a ciscoism again; dunno how much help
it'll be with
> ... coding for a switch-like n/w component; which will be delivered in the 
> next month.

Regards,
Lee

------------------------------------------------------------------------------
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

Reply via email to