tmnxPtpTimeInfoOffFromMasterNs
TIMETRA-PTP-MIB ·
.1.3.6.1.4.1.6527.3.1.2.74.3.5.17
Object
scalar nanosecondsSNMPv2-SMIInteger32
The value of tmnxPtpTimeInfoOffFromMasterNs indicates the current
offset of the local PTP clock from the parent PTP clock, calculated by
the local clock, as per IEEE Std 1588-2008, section 11.2.
It represents the 'instantaneous' value of calculated time offset
from the parent 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 in
tmnxPtpTimeInfoLastCalc.
The active CPM calculates this offset each time the local PTP clock and
the parent PTP clock exchange sync, delay request, and delay response
messages. The standby CPM does not calculate this offset, returning a
value of 0 for tmnxPtpTimeInfoOffFromMasterNs.
If PTP sync and delay request packets have not yet been exchanged
between the local clock and the parent clock, both
tmnxPtpTimeInfoOffFromMasterNs and tmnxPtpTimeInfoLastCalc 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 the
master/parent 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
tmnxPtpTimeInfoOffFromMasterNs.
The system does not calculate the time offset between the local clock
and the parent PTP clock when tmnxPtpClockProfile is 'g8265dot1-2010
(1)'.
This corresponds to the 'currentDS.offsetFromMaster' data set member
defined in IEEE Std 1588-2008.
Context
- MIB
- TIMETRA-PTP-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.74.3.5.17- Type
- scalar
- Access
- readonly
- Status
- current
- Units
- nanoseconds
- Parent
- tmnxPtpTimeInformation
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar 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::tmnxPtpTimeInfoOffFromMasterNs.0'
More examples
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::tmnxPtpTimeInfoOffFromMasterNs'
Syntax
nanosecondsSNMPv2-SMIInteger32
- Source
- SNMPv2-SMIInteger32
- Base type
Integer32
Values & Constraints
Type Constraints
range: -2147483648..2147483647
Conformance
Member of