schedulePeriod

THERMOSTAT-MIB · .1.3.6.1.4.1.57702.1.3.120.1.3

Object

Period within the day, from 1 to 4

Context

MIB
THERMOSTAT-MIB
OID
.1.3.6.1.4.1.57702.1.3.120.1.3
Type
column
Access
readonly
Status
current
Parent
scheduleEntry
Groups
1

Walk 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 'THERMOSTAT-MIB' -M '/opt/observium/mibs/nthermo:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'THERMOSTAT-MIB::schedulePeriod'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'THERMOSTAT-MIB' -M '/opt/observium/mibs/nthermo:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'THERMOSTAT-MIB::schedulePeriod.<scheduleIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'THERMOSTAT-MIB' -M '/opt/observium/mibs/nthermo:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'THERMOSTAT-MIB::schedulePeriod'

Syntax

Source
SchedulePeriodType
Base type
Enumeration
Type Description
Period within each day, 1 through 4, typically
maps as morning(1), day(2), evening(3), and night(4),
but there is no restriction in how they are used.

Values & Constraints

Type Values
1morning
2day
3evening
4night

Conformance