Precision Time Protocol is used to synchronize clocks throughout the network. On a local area network, it achieves clock accuracy in the sub-microsecond range, making it suitable for measurement and control systems. RouterOS supports IEEE 1588-2008, PTPv2. Support is hardware dependant, please see the supported device list below.
|port||Sub-menu used for adding, removing, or viewing assigned ports|
|status||Sub-menu that shows PTP ports, their state, and delay on slave ports|
|comment (string; Default: )|
Short description of the PTP profile
|name (string; Default: )||Name of the PTP profile|
|delay-mode (auto | e2e | ptp; Default: auto)||Configures delay mode for PTP profile|
|priority1 (integer [0..255]; auto; Default: auto)||the priority value for influencing grandmaster election|
|profile (802.1as; default; g8275.1; Default: default)|
IEEE 1588-2008 includes a profile concept defining PTP operating parameters and options.
IEEE 802.1AS is an adaptation of PTP for use with Audio Video Bridging and Time-Sensitive Networking. Uses delay-mode=p2p, transport-mode=l2; recommends using priority1=auto.
g8275.1 profile is for frequency and phase synchronization in a fully PTP-aware network. Only allows priority1=auto (128), priority2=128, domain=24, delay-mode=e2e, transport=l2.
default profile, PTPv2 default configuration, allows for more configuration options than other profiles, but default values with auto settings correspond to: priority1=128. priority2=128, domain=0,transport=ipv4, delay-mode=e2e
|transport (auto; ipv4; l2; Default: auto)||transport protocol to be used: IPv4 or layer2|
For more details regarding Precision Time Protocol please see the following standards IEEE 1588 and IEEE 802.1as.
We strongly recommend keeping default/auto values, as there are different requirements between profiles. And assigning them manually can result in misconfiguration.
To configure the device to participate in PTP you first need to create a PTP profile:
Only 1 PTP profile is supported per device
After creating a PTP profile, you need to assign ports to it:
To monitor the PTP profile, use the monitor command:
|clock-id:||local clock ID|
|priority1:||priority1 value, depending on the PTP profile selected, an adjustable value used to influence the grandmaster election.|
|priority2:||priority2 value, non-adjustable in RouterOS|
|i-am-gm: yes | no||shows if the device is a grandmaster clock|
|gm-clock-id:||grandmaster clock ID - Within a domain, a clock that is the ultimate source of time for clock synchronization using the protocol.|
|master-clock-id:||master clock ID - In the context of a single Precision Time Protocol (PTP) communication path, a clock that is the source of time to which all other clocks on that path synchronize.|
|slave-port:||shows which port is going towards the master or grandmaster clock|
|freq-drift:||frequency drift in PPB (parts per billion) - time that would be lost every second in relation to the master clock, IF there was no synchronization.|
|offset:||difference between clock values|
|hw-offset:||offset difference from the hardware clock|
|slave-port-delay:||the time it takes for a packet to be delivered to a directly connected device|
CRS326-24G-2S+ supported only on Gigabit Ethernet ports
CRS328-24P-4S+ supported only on Gigabit Ethernet ports
CRS317-1G-16S+ supported on all ports
CRS326-24S+2Q+ supported on SFP+ and QSFP+ interfaces
CRS312-4C+8XG supported on all ports
CRS318-16P-2S+ supported only on Gigabit Ethernet ports
Not supported on: