ipAddressSpinLock
IP-MIB ·
.1.3.6.1.2.1.4.33
Object
An advisory lock used to allow cooperating SNMP managers to
coordinate their use of the set operation in creating or
modifying rows within this table.
In order to use this lock to coordinate the use of set
operations, managers should first retrieve
ipAddressTableSpinLock. They should then determine the
appropriate row to create or modify. Finally, they should
issue the appropriate set command, including the retrieved
value of ipAddressSpinLock. If another manager has altered
the table in the meantime, then the value of
ipAddressSpinLock will have changed, and the creation will
fail as it will be specifying an incorrect value for
ipAddressSpinLock. It is suggested, but not required, that
the ipAddressSpinLock be the first var bind for each set of
objects representing a 'row' in a PDU.
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'IP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IP-MIB::ipAddressSpinLock.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'IP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IP-MIB::ipAddressSpinLock'
Syntax
- Source
- SNMPv2-TCTestAndIncr
- Base type
Integer32
Type Description
Represents integer-valued information used for atomic
operations. When the management protocol is used to specify
that an object instance having this syntax is to be
modified, the new value supplied via the management protocol
must precisely match the value presently held by the
instance. If not, the management protocol set operation
fails with an error of `inconsistentValue'. Otherwise, if
the current value is the maximum value of 2^31-1 (2147483647
decimal), then the value held by the instance is wrapped to
zero; otherwise, the value held by the instance is
incremented by one. (Note that regardless of whether the
management protocol set operation succeeds, the variable-
binding in the request and response PDUs are identical.)
The value of the ACCESS clause for objects having this
syntax is either `read-write' or `read-create'. When an
instance of a columnar object having this syntax is created,
any value may be supplied via the management protocol.
When the network management portion of the system is re-
initialized, the value of every object instance having this
syntax must either be incremented from its value prior to
the re-initialization, or (if the value prior to the re-
initialization is unknown) be set to a pseudo-randomly
generated value.
Values & Constraints
Type Constraints
range: 0..2147483647
Conformance
Member of
Compliance refinements
ipMIBCompliance2
noaccess
An agent is not required to provide write access to this
object. However, if an agent provides write access to any
of the other objects in the ipAddressGroup, it SHOULD
provide write access to this object as well.
object. However, if an agent provides write access to any
of the other objects in the ipAddressGroup, it SHOULD
provide write access to this object as well.