mplsLdpSessionDiscontinuityTime
MPLS-LDP-MIB ·
cisco variant
·
.1.3.6.1.3.97.1.3.4.1.5
Object
The value of sysUpTime on the most recent occasion at
which any one or more of this session's counters
suffered a discontinuity. The relevant counters are
the specific instances associated with this session
of any Counter32 or Counter64 object contained in the
mplsLdpSessionStatsTable. If no such discontinuities have
occurred since the last re-initialization of the local
management subsystem, then this object contains a zero
value.
Also, an NMS can distinguish when a session
between a given Entity and Peer goes away and then is
're-established'. This value would change and
thus indicate to the NMS that this is a
different session.
Context
- MIB
- MPLS-LDP-MIB
- OID
.1.3.6.1.3.97.1.3.4.1.5- Type
- column
- Access
- readonly
- Status
- current
- Parent
- mplsLdpSessionEntry
- 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 'MPLS-LDP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-LDP-MIB::mplsLdpSessionDiscontinuityTime'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'MPLS-LDP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-LDP-MIB::mplsLdpSessionDiscontinuityTime.<index>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'MPLS-LDP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MPLS-LDP-MIB::mplsLdpSessionDiscontinuityTime'
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