schedStorageType
DISMAN-SCHEDULE-MIB ·
.1.3.6.1.2.1.63.1.2.1.19
Object
This object defines whether this scheduled action is kept
in volatile storage and lost upon reboot or if this row is
backed up by non-volatile or permanent storage.
Conceptual rows having the value `permanent' must allow
write access to the columnar objects schedDescr,
schedInterval, schedContextName, schedVariable, schedValue,
and schedAdminStatus. If an implementation supports the
schedCalendarGroup, write access must be also allowed to
the columnar objects schedWeekDay, schedMonth, schedDay,
schedHour, schedMinute.
Context
- MIB
- DISMAN-SCHEDULE-MIB
- OID
.1.3.6.1.2.1.63.1.2.1.19- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- schedEntry
- 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-SCHEDULE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-SCHEDULE-MIB::schedStorageType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DISMAN-SCHEDULE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DISMAN-SCHEDULE-MIB::schedStorageType.<schedOwner>.<schedName>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DISMAN-SCHEDULE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DISMAN-SCHEDULE-MIB::schedStorageType'
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