usrHistoryIntervalStart
RMON2-MIB ·
.1.3.6.1.2.1.16.18.3.1.2
Object
The value of sysUpTime at the start of the interval over
which this sample was measured. If the probe keeps track of
the time of day, it should start the first sample of the
history at a time such that when the next hour of the day
begins, a sample is started at that instant.
Note that following this rule may require that the probe delay
collecting the first sample of the history, as each sample
must be of the same interval. Also note that the sample that
is currently being collected is not accessible in this table
until the end of its interval.
Context
- MIB
- RMON2-MIB
- OID
.1.3.6.1.2.1.16.18.3.1.2- Type
- column
- Access
- readonly
- Status
- current
- Parent
- usrHistoryEntry
- 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 'RMON2-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RMON2-MIB::usrHistoryIntervalStart'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'RMON2-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RMON2-MIB::usrHistoryIntervalStart.<usrHistoryControlIndex>.<usrHistorySampleIndex>.<usrHistoryObjectIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'RMON2-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RMON2-MIB::usrHistoryIntervalStart'
Syntax
- Source
- SNMPv2-TCTimeStamp
- Base type
Unsigned32- Based on
- SNMPv2-SMITimeTicks
Type Description
The value of the sysUpTime object at which a specific
occurrence happened. The specific occurrence must be
defined in the description of any object defined using this
type.
If sysUpTime is reset to zero as a result of a re-
initialization of the network management (sub)system, then
the values of all TimeStamp objects are also reset.
However, after approximately 497 days without a re-
initialization, the sysUpTime object will reach 2^^32-1 and
then increment around to zero; in this case, existing values
of TimeStamp objects do not change. This can lead to
ambiguities in the value of TimeStamp objects.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of