Hi Philip, you can capture PTP packets using tcpdump command with the "ether proto 0x88F7" parameter for L2 or "udp port 319 or udp port 320" in case of UDP. Wireshark is very helpful in understanding of PTP packets flow. Also, the pmc command is available for you to check the PTP port status and see what's going on. For example, "pmc -u -b 0 'GET PORT_DATA_SET" and pmc -u -b 0 'GET TIME_STATUS_NP' are the most useful ones in analyzing slave/master interactions. Regards, Alex From: Philip_Wang@alphanetworks.com [mailto:Philip_Wang@alphanetworks.com] Sent: December 3, 2019 21:16 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] PTP tx timestamp seem not get from NIC Dear Team, In my All-In-One environment, I check /var/log/user.log find below message. 2019-12-03T16:03:30.000 controller-0 ptp4l: warning [20954.517] clockcheck: clock jumped forward or running faster than expected! 2019-12-03T16:03:30.000 controller-0 ptp4l: notice [20954.517] port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.613] port 0015b2.fffe.a92e24-1 changed state 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.613] reconfiguring after port state change 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.613] master clock not ready, waiting... 2019-12-03T16:03:30.000 controller-0 ptp4l: notice [20954.861] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.914] port 0015b2.fffe.a92e24-1 changed state 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.914] reconfiguring after port state change 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.914] selecting CLOCK_REALTIME for synchronization 2019-12-03T16:03:30.000 controller-0 phc2sys: info [20954.914] selecting enp0s25 as the master clock 2019-12-03T16:03:35.000 controller-0 phc2sys: info [20959.816] rms 8125465923430 max 70368744177703 freq -3070283 +/- 72810449 delay 1662 +/- 172 2019-12-03T16:03:43.000 controller-0 ptp4l: info [20967.182] rms 17864936252211 max 70368748587963 freq +17842027 +/- 101360440 delay 173334 +/- 1003918 2019-12-03T16:03:43.000 controller-0 ptp4l: warning [20967.688] clockcheck: clock jumped forward or running faster than expected! 2019-12-03T16:03:43.000 controller-0 ptp4l: notice [20967.688] port 1: SLAVE to UNCALIBRATED on SYNCHRONIZATION_FAULT 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20967.720] port 0015b2.fffe.a92e24-1 changed state 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20967.720] reconfiguring after port state change 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20967.720] master clock not ready, waiting... 2019-12-03T16:03:43.000 controller-0 ptp4l: notice [20968.031] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20968.120] port 0015b2.fffe.a92e24-1 changed state 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20968.120] reconfiguring after port state change 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20968.120] selecting CLOCK_REALTIME for synchronization 2019-12-03T16:03:43.000 controller-0 phc2sys: info [20968.120] selecting enp0s25 as the master clock This message is seem that delay request packet TX timestamp is not get from NIC(Intel I210) cause port 1 state from SLAVE to UNCALIBRATED. Has any debug method can check the TX timestamp?? Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation.