tmnxPtpPeerMonTimeOffsetFrMastNs
TIMETRA-PTP-MIB ·
.1.3.6.1.4.1.6527.3.1.2.74.3.10.1.6
Object
column nanosecondsSNMPv2-SMIInteger32
The value of tmnxPtpPeerMonTimeOffsetFrMastNs indicates the current
offset of the local PTP clock from a master PTP clock, calculated by
the local clock, as per IEEE Std 1588-2008, section 11.2 when Monitor
Receiver has been enabled on a given peer.
It represents the 'instantaneous' value of calculated time offset
from a master PTP clock, 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 offset was last calculated is provided by
tmnxPtpPeerMonTimeLastCalc.
The active CPM calculates this offset each time the local PTP clock and
a master clock exchange sync, delay request, and delay response
messages. The standby CPM does not calculate this offset, 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
tmnxPtpPeerMonTimeOffsetFrMastNs and tmnxPtpPeerMonTimeLastCalc return
a value of 0.
Due to asymmetry in the latencies experienced by PTP sync and delay
request packets, the calculated offset from master may not be a true
indication of the actual offset of the local clock from a
master clock. As well, due to packet delay variation in the PTP
sync and delay request flows, there may be significant variation
between successive calculated values of tmnxPtpPeerMonTimeOffsetFrMastNs.
The system only calculates the time offset 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 peer.
Context
- MIB
- TIMETRA-PTP-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.74.3.10.1.6- Type
- column
- Access
- readonly
- Status
- current
- Units
- nanoseconds
- Parent
- tmnxPtpPeerStatusEntry
- 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 'TIMETRA-PTP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-PTP-MIB::tmnxPtpPeerMonTimeOffsetFrMastNs'
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::tmnxPtpPeerMonTimeOffsetFrMastNs.<vRtrID>.<tmnxPtpPeerIpAddrType>.<tmnxPtpPeerIpAddress>'
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::tmnxPtpPeerMonTimeOffsetFrMastNs'
Syntax
nanosecondsSNMPv2-SMIInteger32
- Source
- SNMPv2-SMIInteger32
- Base type
Integer32
Values & Constraints
Type Constraints
range: -2147483648..2147483647
Conformance
Member of