Reference record for OID 1.3.6.1.6.3.1134.5.1

parent

1.3.6.1.6.3.1134.5 (v2AdminAccessControl)

node code

1

node name

acSpinLock

dot oid

1.3.6.1.6.3.1134.5.1

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminAccessControl(5) acSpinLock(1)}

{iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminAccessControl(5) acSpinLock(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminAccessControl(5) acSpinLock(1)}

iri oid

/iso/identified-organization/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminAccessControl/acSpinLock

/iso/org/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminAccessControl/acSpinLock

/iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminAccessControl/acSpinLock

iri by oid_info

/ISO/Identified-Organization/6/1/6/3/1134/5/1

Description by mibdepot

An advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of the Set operation in creating view trees.

The values of viewTreeSpinLock, acSpinLock, and notifySpinLock
[if the notifyTable is implemented] should be accessed in
harmony to provide interlocks on the creation of new views.

When creating a new view or altering an existing view, it is
important to understand the potential interactions with other
users of the view. The spinlocks for each table which allows
the creation of named views should be retrieved. The name of
the view to be created should be determined to be unique on
the managed system by consulting each table containing named
views. Finally, the named view may be created, including the
advisory spinlocks.

Since this is an advisory lock, entities acting in an agent
role do not enforce the use of acSpinLock.

Parsed from file cacheflow-v2-adm.mib.txt
Company: cacheflow
Module: V2ADMIN-MIB

Information by oid_info

Child arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in IETF RFC 2576, section 3.

Information by mibdepot

acSpinLock OBJECT-TYPE
        SYNTAX       TestAndIncr
        MAX-ACCESS   read-write
        STATUS       current
        DESCRIPTION
              "An advisory lock used to allow several cooperating SNMPv2
              entities, all acting in a manager role, to coordinate their
              use of the Set operation in creating view trees.

              The values of viewTreeSpinLock, acSpinLock, and notifySpinLock
              [if the notifyTable is implemented] should be accessed in
              harmony to provide interlocks on the creation of new views.

              When creating a new view or altering an existing view, it is
              important to understand the potential interactions with other
              users of the view.  The spinlocks for each table which allows
              the creation of named views should be retrieved.  The name of
              the view to be created should be determined to be unique on
              the managed system by consulting each table containing named
              views.  Finally, the named view may be created, including the
              advisory spinlocks.

              Since this is an advisory lock, entities acting in an agent
              role do not enforce the use of acSpinLock."
        ::= { v2AdminAccessControl 1 }

First Registration Authority (recovered by parent 1.3.6)

Defense Communication Agency

Current Registration Authority (recovered by parent 1.3.6)

US DoD

Children (1)

Brothers (1)