midcomRuleStorageType
MIDCOM-MIB ·
.1.3.6.1.2.1.171.1.1.3.1.6
Object
When retrieved, this object returns the storage
type of the policy rule. Writing to this object can
change the storage type of the particular row from
volatile(2) to nonVolatile(3) or vice versa.
Attempts to set this object to permanent will always
fail with an 'inconsistentValue' error. Note that this
error code is SNMP specific. If the MIB module is used
with other protocols than SNMP, errors with similar
semantics specific to those protocols should be
returned.
If midcomRuleStorageType has the value permanent(4),
then all objects in this row whose MAX-ACCESS value
is read-create must be read-only.
Context
- MIB
- MIDCOM-MIB
- OID
.1.3.6.1.2.1.171.1.1.3.1.6- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- midcomRuleEntry
- Groups
- 1
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 'MIDCOM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MIDCOM-MIB::midcomRuleStorageType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'MIDCOM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MIDCOM-MIB::midcomRuleStorageType.<midcomRuleOwner>.<midcomGroupIndex>.<midcomRuleIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'MIDCOM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MIDCOM-MIB::midcomRuleStorageType'
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