tmnxPtpNeighbMonTimeMnPathDlyNs

TIMETRA-PTP-MIB · .1.3.6.1.4.1.6527.3.1.2.74.3.7.1.20

Object

column nanosecondsSNMPv2-SMIInteger32
The value of tmnxPtpNeighbMonTimeMnPathDlyNs indicates the current
value of the mean propagation time between the local PTP clock and a
master PTP clock, calculated by the local clock, as per IEEE Std
1588-2008, section 11.3, when Monitor Receiver has been enabled on a
given port
              
It represents the 'instantaneous' value of the calculated mean path
delay, using timestamp information from the most recent exchange of
sync and delay request/response messages.  There is no filtering
applied to the received sync and delay response messages, and there is
no averaging of this calculation over multiple exchanges of sync and
delay request/response messages.
              
The time that this mean path delay was last calculated is provided by
tmnxPtpNeighborMonTimeLastCalc.
              
The active CPM calculates the mean path delay each time the local PTP
clock and a master clock exchange sync, delay request, and delay
response messages.  The standby CPM does not calculate the mean path
delay, returning a value of 0 for this object.
              
If PTP sync and delay request packets have not yet been exchanged
between the local clock and a master clock, both
tmnxPtpNeighbMonTimeMnPathDlyNs and tmnxPtpNeighborMonTimeLastCalc
return a value of 0.
              
This mean path delay includes cable/fiber latency in the sync and delay
request path, and includes latency within network devices that do not
correct for internal latencies.  The mean path delay does not include
latency within network devices that are PTP transparent clocks, which
correct for these internal latencies.
              
Due to packet delay variation in the PTP sync and delay request flows,
there may be significant variation between successive calculated
values of tmnxPtpNeighbMonTimeMnPathDlyNs.
              
The system only calculates the mean path delay between the local clock
and a master clock when tmnxPtpClockProfile is 'g8275dot1-2014 (3)' or
'g8275dot2-2016 (4)' and Monitor Receiver has been enabled on the
specific port.

Context

MIB
TIMETRA-PTP-MIB
OID
.1.3.6.1.4.1.6527.3.1.2.74.3.7.1.20
Type
column
Access
readonly
Status
current
Units
nanoseconds
Parent
tmnxPtpPortNeighborEntry
Groups
1

Walk 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 'TIMETRA-PTP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-PTP-MIB::tmnxPtpNeighbMonTimeMnPathDlyNs'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-PTP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-PTP-MIB::tmnxPtpNeighbMonTimeMnPathDlyNs.<tmnxChassisIndex>.<tmnxPortPortID>.<tmnxPtpPortNeighborMacAddress>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-PTP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-PTP-MIB::tmnxPtpNeighbMonTimeMnPathDlyNs'

Syntax

Source
SNMPv2-SMIInteger32
Base type
Integer32

Values & Constraints

Type Constraints
range: -2147483648..2147483647

Conformance