smLaunchStorageType
DISMAN-SCRIPT-MIB ·
.1.3.6.1.2.1.64.1.4.1.1.15
Object
This object defines if this row is kept in volatile storage
and lost upon reboot or if this row is backed up by stable
storage.
The value of smLaunchStorageType is only meaningful if the
value of the corresponding RowStatus object is active.
If smLaunchStorageType has the value permanent(4), then all
objects whose MAX-ACCESS value is read-create must be
writable, with the exception of the smLaunchStorageType and
smLaunchRowStatus objects, which shall be read-only.
Context
- MIB
- DISMAN-SCRIPT-MIB
- OID
.1.3.6.1.2.1.64.1.4.1.1.15- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- smLaunchEntry
- Groups
- 2
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DISMAN-SCRIPT-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-SCRIPT-MIB::smLaunchStorageType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DISMAN-SCRIPT-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-SCRIPT-MIB::smLaunchStorageType.<smLaunchOwner>.<smLaunchName>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DISMAN-SCRIPT-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DISMAN-SCRIPT-MIB::smLaunchStorageType'
Syntax
- Source
- SNMPv2-TCStorageType
- Base type
Enumeration
Type Description
Describes the memory realization of a conceptual row. A
row which is volatile(2) is lost upon reboot. A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage. A row which is permanent(4)
can be changed but not deleted. A row which is readOnly(5)
cannot be changed nor deleted.
If the value of an object with this syntax is either
permanent(4) or readOnly(5), it cannot be written.
Conversely, if the value is either other(1), volatile(2) or
nonVolatile(3), it cannot be modified to be permanent(4) or
readOnly(5). (All illegal modifications result in a
'wrongValue' error.)
Every usage of this textual convention is required to
specify the columnar objects which a permanent(4) row must
at a minimum allow to be writable.
Values & Constraints
Type Values
1 | other |
2 | volatile |
3 | nonVolatile |
4 | permanent |
5 | readOnly |
Conformance
Member of