Szablon: Webnative ptp: Różnice pomiędzy wersjami
Z Elproma Wiki Knowledge Base
| Linia 17: | Linia 17: | ||
| Enabled PTP as Master/Slave. | | Enabled PTP as Master/Slave. | ||
|- | |- | ||
! scope="row" colspan="3"| | ! scope="row" colspan="3"|PTP Options | ||
|- | |- | ||
| | | Domain number | ||
| | | Number [0...255] | ||
| | | A domain does define the scope of PTP message communication, state, operations, data sets, and timescale. Devices synchronize only to PTP devices within same domain. Multiple domains mayy be used in signle network. | ||
|- | |||
| Profile | |||
| IEEE1588/802.1AS | |||
| Defines whether synchronization is performed using standard PTP (<b>IEEE1588</b>) or gPTP (<b>802.1AS</b>). | |||
|- | |||
| Transport layer | |||
| L2/L4 | |||
| <b>L2 (Ethernet)</b>: PTP packets are encapsulated directly in Ethernet frames (IEEE 802.3 network transport) | |||
<b>L4 (UDP)</b>: PTP packets are exchanged over UDP/IPv4 | |||
|- | |||
| IP mode | |||
| multicast/unicast/hybrid | |||
| | |||
|- | |||
| Delay mechanism | |||
| E2E/P2P | |||
| </b>E2E</b>: Delay is measured end-to-end. Delay is calculated for the whole path | |||
<b>P2P</b>: Delay is measured peer-to-peer. If transparent clocks are present in a network, they need to support peer-delay mechanism (and have it enabled) | |||
|- | |||
| gPTP Slave type | |||
| Slave-only/Master-capable | |||
| Defines whether gPTP Slave device may become a Master in the network in case there is no other available. Cannot become Grandmaster. | |||
|- | |||
! scope="row" colspan="3"|PTP Master configuration | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|- | |||
| | |||
| | |||
| | |||
|} | |} | ||
[[Category:{{{model}}} User Manual]] | [[Category:{{{model}}} User Manual]] | ||
Wersja z 14:15, 18 maj 2023
The PTP page of {{{model}}} time server is used to configure and run PTP protocol.
Switching on PTP enables PTP grandmaster daemon.
PTP options
| Option name | Value type/possible values | Description |
|---|---|---|
| PTP | Disabled/Grandmaster/Slave | Enabled PTP as Master/Slave. |
| PTP Options | ||
| Domain number | Number [0...255] | A domain does define the scope of PTP message communication, state, operations, data sets, and timescale. Devices synchronize only to PTP devices within same domain. Multiple domains mayy be used in signle network. |
| Profile | IEEE1588/802.1AS | Defines whether synchronization is performed using standard PTP (IEEE1588) or gPTP (802.1AS). |
| Transport layer | L2/L4 | L2 (Ethernet): PTP packets are encapsulated directly in Ethernet frames (IEEE 802.3 network transport)
L4 (UDP): PTP packets are exchanged over UDP/IPv4 |
| IP mode | multicast/unicast/hybrid | |
| Delay mechanism | E2E/P2P | E2E: Delay is measured end-to-end. Delay is calculated for the whole path
P2P: Delay is measured peer-to-peer. If transparent clocks are present in a network, they need to support peer-delay mechanism (and have it enabled) |
| gPTP Slave type | Slave-only/Master-capable | Defines whether gPTP Slave device may become a Master in the network in case there is no other available. Cannot become Grandmaster. |
| PTP Master configuration | ||
[[Category:{{{model}}} User Manual]]