W
EB
C
ONFIGURATION
S
OFTWARE
R
EVISED
2018-09-21
T
IME
D
RAWING
N
O
. LP0991-G
2-113
N-Tron
®
Series NT24K
®
Software Manual
Boundary Clock
Delay Mechanism:
The Delay Mechanism specifies the method used by PTP to handle delay correction
values. E2E is the only delay mechanism currently supported.
Transport:
IPv4/UDP is the only network transport method currently supported.
Domain Number:
The Domain Number selects a PTP Domain. Only PTP packets in the same domain will
be received and processed, and all sent PTP packets will be tagged with the same Domain Number. The
range is 0-127. The default is 0.
Priority1:
This value sets the priority of this switch as a Master clock. It is the most important value used
by the Best Master Clock (BMC) algorithm of other PTP devices when selecting a Master clock. The range
is 0-255, with 0 being most important. The default is 128.
Priority2:
This value is used to break ties in the BMC algorithm. The range is 0-255, with 0 being most
important. The default is 128.
Default UTC Valid:
Current UTC Valid is a field in PTP packets that tells other devices whether the UTC
Offset field that is also being sent in the packet should be considered valid. The Current UTC Valid value is
set to this default at boot time, until it is updated by making a connection to a PTP Master. The default is
"False" because the switch does not boot with a valid calendar time. It can be changed for interoperability
reasons.
Default UTC Offset:
The Current UTC Offset value is set to this default at boot time. The range is 0-127.
The default is 36.
Default Timescale:
The Current Timescale value is set to this default at boot time. All times exchanged in
the PTP protocol are either "Arbitrary" or "PTP". Times that are "Arbitrary" cannot be converted to calendar
time correctly and may have no connection to external accurate time. Times that are "PTP" can be con-
verted to accurate calendar time using the UTC offset. The default is "Arbitrary" because the switch does
not boot with a valid calendar time. It can be changed for interoperability reasons.
Current UTC Valid:
A field in exchanged PTP packets that says whether the UTC Offset field that is also
being sent in the packet should be considered valid. This is a run-time value that is dynamically updated
based on the most recently connected PTP Master. It can be changed manually, but the set value will only
persist until the next time a connection is made to a PTP Master.
Current UTC Offset:
A field in exchanged PTP packets that provides the current offset to UTC. This is a
run-time value that is dynamically updated based on the most recently connected PTP Master. It can be
changed manually, but the set value will only persist until the next time a connection is made to a PTP
Master.
Current Timescale:
A field in exchanged PTP packets that provides the most recently received Timescale
value from the Master. This is a run-time value that is dynamically updated based on the most recently
connected PTP Master. It can be changed manually, but the set value will only persist until the next time a
connection is made to a PTP Master.
Current Timescale:
A field in exchanged PTP packets that provides the most recently received Timescale
value from the Master. This is a run-time value that is dynamically updated based on the most recently
connected PTP Master. It can be changed manually, but the set value will only persist until the next time a
connection is made to a PTP Master.
