Error / Status | Clock Sync Error
Learn strategies to fix Clock Sync Errors and understand common causes of this common issue.
Affected Products
| Hardware Model/Series | All |
| Software | All |
Message
Clock Sync Error can be seen in the Event log, reported by a Core or Peripheral
Definition
A Clock Sync error occurs when the device reporting the issue experiences delays in PTP delivery. When PTP jitter is large enough, the device's internal clock will need to adjust itself which will cause the device to report a clock sync error.
This can also be cause by a network interruption (no or incorrect QoS settings, switch reboot, spanning tree or the system's grandmaster going offline)
If a core is experiencing this problem, it is typical you will see clock sync errors on the peripherals and missing packet messages from devices on the network.
Solution | Workaround
You will not see this on a device (core) that is the Grandmaster.
This error is typically experienced when there is a QoS issue causing PTP Jitter on the network.
Core Troubleshooting
Easiest way prove PTP delivery is the cause is by temporally making that core the grandmaster on the network. If the clock sync errors do not show up, then you know root cause is the delivery of PTP to the core from the original grandmaster. Investigate the network path (QoS settings) from the Grandmaster to the affected Core.
Peripheral Troubleshooting
- It is important to identify which peripherals are experiencing the issue. Is it all peripherals or a subset of the peripherals in the design.
- If all peripherals are experiencing the problem, verify the core is not experiencing the issue.
- If the core is the grandmaster and all peripherals are experiencing the issue, verify the core switch QoS settings.
- If a subset of peripherals are experiencing the issue. Determine if the affected peripherals are all connected to the same switch. Review the Network configurations for the affected network paths.