ciscoExtScsiLunDiscSpinLock
CISCO-EXT-SCSI-MIB ·
.1.3.6.1.4.1.9.9.299.1.1.2
Object
This object is used to facilitate triggerring
the LUN/target discovery by multiple managers.
The procedure for triggering LUN/target discovery
is as follows:
1. Retrieve the value of
ciscoExtScsiLunDiscSpinLock and determine the
value for ciscoExtScsiStartLunDisc,
ciscoExtScsiLunDiscOs, ciscoExtScsiLunDiscVsanID,
ciscoExtScsiLunDiscPortId and
ciscoExtScsiDiscType objects.
2. Set the value of ciscoExtScsiLunDiscSpinLock
to the retrieved value, and in the same PDU,
the value of ciscoExtScsiLunDiscOs
to the determined value. If the set fails for
the ciscoExtScsiLunDiscSpinLock object, go back
to step 1.
3. Set the value of ciscoExtScsiLunDiscSpinLock
to the retrieved value plus 1, and in the same
PDU, the value of ciscoExtScsiLunDiscVsanID to
the determined value. If the set fails for
the ciscoExtScsiLunDiscSpinLock object, go back
to step 1.
4. Set the value of ciscoExtScsiLunDiscSpinLock
to the retrieved value plus 2, and in the same
PDU, the value of ciscoExtScsiLunDiscPortId to
the determined value. If the set fails for the
ciscoExtScsiLunDiscSpinLock object, go back to
step 1.
5. Set the value of ciscoExtScsiLunDiscSpinLock
to the retrieved value plus 3, and in the same
PDU, the value of ciscoExtScsiDiscType to
the determined value. If the set fails for
the ciscoExtScsiLunDiscSpinLock object, go
back to step 1.
6. Set the value of ciscoExtScsiLunDiscSpinLock
to the retrieved value plus 4, and in the same
PDU, the value of ciscoExtScsiStartLunDisc to
the determined value. If the set fails for
the ciscoExtScsiLunDiscSpinLock object, go
back to step 1.
Note that if it is possible to include
ciscoExtScsiLunDiscVsanID,
ciscoExtScsiLunDiscPortId, ciscoExtScsiDiscType
and/or ciscoExtScsiStartLunDisc in the
(Set Request) PDU of an earlier step, then steps
3, 4 and/or 5 can be eliminated.
Context
- MIB
- CISCO-EXT-SCSI-MIB
- OID
.1.3.6.1.4.1.9.9.299.1.1.2- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- ciscoExtScsiConfiguration
- Groups
- 3
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 'CISCO-EXT-SCSI-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-EXT-SCSI-MIB::ciscoExtScsiLunDiscSpinLock.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-EXT-SCSI-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-EXT-SCSI-MIB::ciscoExtScsiLunDiscSpinLock'
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