dpStatusDateTimeStatustime – DATAPOWER-STATUS-MIB

Object

scalar SNMPv2-TCTimeStamp

The current local time. This time is obtained from the timezone settings
established on the Time Settings object and with the date and time
settings set on the System Control page.

Context

MIB: DATAPOWER-STATUS-MIB
OID: .1.3.6.1.4.1.14685.3.1.3.1
Type: scalar
Access: readonly
Status: current
Parent: dpStatusDateTimeStatus

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 'DATAPOWER-STATUS-MIB' -M '/opt/observium/mibs/ibm:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DATAPOWER-STATUS-MIB::dpStatusDateTimeStatustime.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'DATAPOWER-STATUS-MIB' -M '/opt/observium/mibs/ibm:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DATAPOWER-STATUS-MIB::dpStatusDateTimeStatustime'

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.