poeLastUpdateTime – CUMULUS-POE-MIB

Object

scalar SNMPv2-TCTimeStamp

The system uptime timestamp when the objects in this MIB were last
updated. The default for the update period is every 300 seconds or 5
minutes.

Context

MIB: CUMULUS-POE-MIB
OID: .1.3.6.1.4.1.40310.3.1.4
Type: scalar
Access: readonly
Status: current
Parent: poeSystemValues

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CUMULUS-POE-MIB' -M '/opt/observium/mibs/cumulus:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CUMULUS-POE-MIB::poeLastUpdateTime.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'CUMULUS-POE-MIB' -M '/opt/observium/mibs/cumulus:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CUMULUS-POE-MIB::poeLastUpdateTime'

Syntax

SNMPv2-TCTimeStamp

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.