Note: I moved this to the testbed-admins list - mail regarding running
the Emulab sfotware in general is best directed to that list.
The error message (trimmed out below) would seem to indicate that the
SNMP community string you're using doesn't have write access. If it
didn't have read access or couldn't talk to the switch at all, it would
have recived a different error earlier.
Make sure the snmp_community column in your switch_stack_types table is
set correctly - I see that you did set it, but make sure it matches the
community string listed for 'read-write' access in the output of 'show
snmp' on the switch.
Thus spake chunhui Zhang(Evan) on Mon, Dec 07, 2009 at 10:15:25AM -0500:
> Hi,
>
> We setup two nodes at our site and connected them to a Cisco 2960 switch
> (experiment swith), I got the error "No owner of the VLAN lock "
> when I tried to swap in a experiment with two node and a link between them.
> Please refer to the following message,
>
> --------------------------------------------------------------------------------------------
> *** WARNING: snmpit:> ---------------------------------------------------------------------------------
> *** SNMP SET failed - In /usr/testbed/bin/snmpit
> *** SNMPIT set failed for device cisco1 (try 10 of 10)
> *** Variable was [vtpVlanEditOperation,1,2,INTEGER]
> *** Returned (undefined), ErrorNum was 6
> *** Error string is: noAccess
> *** WARNING: snmpit:
> *** SNMP SET failed - In /usr/testbed/bin/snmpit
> *** SNMPIT set failed for device cisco1 (try 10 of 10)
> *** Variable was [vtpVlanEditOperation,1,2,INTEGER]
> *** Returned (undefined), ErrorNum was 6
> *** Error string is: noAccess
> cisco1: VLAN edit buffer request failed - try 2 of 10.
> cisco1: No owner of the VLAN lock
> ...
> ...
> ...
> ...
> ERROR: Failed to obtain VLAN edit buffer lock
> *** Failed to create VLAN 2 after 3 tries - giving up
> Creating VLAN 2 as VLAN #2 on stack Experiment ... Failed
> *** ERROR: snmpit: Failed to create VLAN with id 2
> *** ERROR: tbswap: Failed to set up VLANs.