PTPv2
Precision Time Protocol (PTP) is used to synchronize network clocks. It is best suited to situations where time accuracy is of the utmost importance, as it supports accuracy in the sub‑microsecond range. Conversely, NTP accuracy is in the range of milliseconds or tens of milliseconds.
The following CLI commands have been added:
config system ptp
set status {enable | disable}
set mode {multicast | hybrid}
set delay-mechanism {E2E | P2P}
set request-interval <integer>
set interface <interface>
end
Command |
Description |
---|---|
status {enable | disable} |
Enable/disable setting the FortiGate system time by synchronizing with an PTP server (default = disable). |
mode {multicast | hybrid} |
Use multicast or hybrid transmission (default = multicast). |
delay-mechanism {E2E | P2P} |
Use End to End (E2E) or Peer to Peer (P2P) delay detection (default = E2E). |
request-interval <integer> |
The logarithmic mean interval between the delay request messages sent by the client to the server, in seconds (default = 1). |
interface <interface> |
The interface that the PTP client will reply through. |
This example uses the following topology:
To configure a FortiGate to act as a PTP client that synchronizes itself with a Linux PTP server:
- Enable debug messages:
diagnose debug application ptpd -1
This command will provide details to debug the PTP communication with the server.
- Check the system date:
execute date
current date is: 2019-01-01
- Configure PTP in global mode:
config system ptp
set status enable
set interface wan2
end
- Check the system date again after synchronization with the PTP server
execute date
current date is: 2019-08-20