SNMP-VIEW-BASED-ACM-MIB :: vacmViewSpinLock

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSNMP-VIEW-BASED-ACM-MIBvacmViewSpinLock

vacmViewSpinLock

Module: SNMP-VIEW-BASED-ACM-MIB

OID (symbolic): SNMP-VIEW-BASED-ACM-MIB::vacmViewSpinLock

OID (numeric): 1.3.6.1.6.3.16.1.5.1

Node type: OBJECT-TYPE

Type: TestAndIncr

Access: read-write

Description: An advisory lock used to allow cooperating SNMP Command Generator applications to coordinate their use of the Set operation in creating or modifying views.

When creating a new view or altering an existing view, it is important to understand the potential interactions with other uses of the view. The vacmViewSpinLock should be retrieved. The name of the view to be created should be determined to be unique by the SNMP Command Generator application by consulting the vacmViewTreeFamilyTable. Finally, the named view may be created (Set), including the advisory lock. If another SNMP Command Generator application has altered the views in the meantime, then the spin lock's value will have changed, and so this creation will fail because it will specify the wrong value for the spin lock.

Since this is an advisory lock, the use of this lock is not enforced.

What is vacmViewSpinLock?

This read-write advisory lock lets cooperating SNMP command-generator applications coordinate their use of Set operations when creating or modifying MIB views; an application retrieves the lock, checks vacmViewTreeFamilyTable for a unique view name, then sets the new view including the current lock value, and the set fails if the lock value has changed due to another application's concurrent modification. Admins' management tools use this internally to avoid two SNMP managers clobbering each other's view changes, though as an advisory lock its use isn't enforced by the agent. For example, a management application reads the spin lock as 42, creates a new view referencing lock value 42, and the change succeeds only if no other application incremented the lock in the meantime.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.6.3.16.1.5.1
snmpwalk -v2c -c public <target> SNMP-VIEW-BASED-ACM-MIB::vacmViewSpinLock

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.6.3.16.1.5.1.1
snmpget -v2c -c public <target> SNMP-VIEW-BASED-ACM-MIB::vacmViewSpinLock.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.6.3.16.1.5.1.1 s <value>

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device or agent (VACM access-control mapping) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SNMP-VIEW-BASED-ACM-MIB::vacmViewSpinLock OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, any SNMPv3-capable network device or agent (VACM access-control mapping) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.6snmpV2DASAN-DHCP-MIB
1.3.6.1.6.3snmpModulesRAPID-CITY
Numeric OIDNameModule
1.3.6.1.6.3.16snmpVacmMIBSNMP-VIEW-BASED-ACM-MIB
1.3.6.1.6.3.16.1vacmMIBObjectsSNMP-VIEW-BASED-ACM-MIB
1.3.6.1.6.3.16.1.5vacmMIBViewsSNMP-VIEW-BASED-ACM-MIB
1.3.6.1.6.3.16.1.5.1vacmViewSpinLockSNMP-VIEW-BASED-ACM-MIB