Reference record for OID 1.3.6.1.6.3.1134.7.1
- Parent
- 1.3.6.1.6.3.1134.7 (v2AdminNotify)
- Node code
- 1
- Node name
- notifySpinLock
- Numeric OID
- 1.3.6.1.6.3.1134.7.1
- Type
- OBJECT-TYPE
- ASN.1 notation
-
- {iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminNotify(7) notifySpinLock(1)}
- {iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminNotify(7) notifySpinLock(1)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminNotify(7) notifySpinLock(1)}
- IRI notation
- /iso/identified-organization/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminNotify/notifySpinLock
- /iso/org/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminNotify/notifySpinLock
- /iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminNotify/notifySpinLock
- IRI from OID Repository
- /ISO/Identified-Organization/6/1/6/3/1134/7/1
Descriptions may differ between sources. The primary description is shown first.
Primary description: 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
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 notifySpinLock.
Parsed from file cacheflow-v2-adm.mib.txt
Company: cacheflow
Module: V2ADMIN-MIB
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
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 notifySpinLock.
Parsed from file cacheflow-v2-adm.mib.txt
Company: cacheflow
Module: V2ADMIN-MIB
Information from OID Repository
Child arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in IETF RFC 2576, section 3.
Information from MIBdepot
notifySpinLock 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
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 notifySpinLock."
::= { v2AdminNotify 1 }
First Registration Authority (inferred from ancestor 1.3.6)
Current Registration Authority (inferred from ancestor 1.3.6)
Direct children (1)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.6.3.1134.7.1.0 | notifySpinLock | 0 | 0 |
Siblings (2)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.6.3.1134.7.2 | notifyTable | 1 | 9 | The notification destination database. This table need only be implemented by entities which will send trap notifications or inf… |
| 1.3.6.1.6.3.1134.7.3 | notifyInformParametersTable | 1 | 5 | Database of additional parameters for notification destinations. This table need only be implemented by entities which are confi… |