sapDcpTimeEventOccured

TIMETRA-SAP-MIB · .1.3.6.1.4.1.6527.3.1.2.4.3.151.1
Commands MIB view Table view

Object

scalar SNMPv2-TCTimeStamp 
The value of sapDcpTimeEventOccured indicates the actual time the
event was detected in the system which may differ from the time that
event was collected by the logging infrastructure.

Context

MIB
TIMETRA-SAP-MIB
OID
.1.3.6.1.4.1.6527.3.1.2.4.3.151.1
Type
scalar
Access
notifyonly
Status
current
Parent
sapNotificationObjects
Groups
1

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 'TIMETRA-SAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-SAP-MIB::sapDcpTimeEventOccured.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-SAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-SAP-MIB::sapDcpTimeEventOccured'

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.

Conformance

Member of
tmnxSapDcpNotifyObjsV11v0Group