This article explains about PTP CLKSYNCD_FAULT issue caused due to the upstream source.
When you check the ptp lock-status where its failing for a particular interface Need to check the below shell level command from respective FPC.
show ptp lock-status detail | no-more
Sep 18 09:37:16
Lock Status:
Lock State : 3 (ACQUIRING)
Phase offset : -0.000000001 sec
State since : 2024-09-06 01:20:35 +08 (1w5d 08:16 ago)
Selected Master Details:
Upstream Master address : 24:fc:4e:ff:fe:12:fb:50
Slave interface : ae3.0 (xe-5/0/0, primary)
Clock reference state : Clock locked
1pps reference state : Clock qualified
Router0 vty)#
show ptp pdv-data 20
: T1(sec) T1(nsec) T2(sec) T2(nsec) Seq id CF Offset
S : 1726623140 440533903 1726623140 843125928 45426 1000020549 -597428524
D : 1726623140 809895377 1726623140 407573558 07283 101060 -402422879
S : 1726623140 378143631 1726623140 780705664 45425 999998869 -597436836
D : 1726623140 748772865 1726623140 346474046 07282 115908 -402414727
S : 1726623140 315753359 1726623140 718325432 45424 1000017221 -597445148
D : 1726623140 684318577 1726623140 282013270 07281 100844 -402406151
S : 1726623140 253363087 1726623140 655945192 45423 1000035569 -597453464
D : 1726623140 623750385 1726623140 221433606 07280 81288 -402398067
S : 1726623140 190972815 1726623140 593564944 45422 53901 402538228
D : 1726623140 559802145 1726623140 157493182 07279 80588 -402389551
S : 1726623140 128582543 1726623140 531144648 45421 32193 402529912
D : 1726623140 498775761 1726623140 096473390 07278 79044 -402381415
S : 1726623140 066192271 1726623140 468764456 45420 50589 402521596
D : 1726623140 438801377 1726623140 036494086 07277 66140 -402373431
S : 1726623140 003801999 1726623140 406383824 45419 68541 402513284
D : 1726623140 373860353 1726623139 971683142 07276 187556 -402364767
S : 1726623139 939656079 1726623140 342122984 45418 999962189 -597495284
D : 1726623140 318760129 1726623139 916585086 07275 182396 -402357439
S : 1726623139 877265807 1726623140 279702704 45417 999940505 -597503608
D : 1726623140 248867345 1726623139 846682774 07274 163540 3892619185
When issue is with FPC x interface xe-x/0/0 only so as a NPOA would request you to reset the same (xe-x/0/0)or keep it down for sometime say around 10-20 minutes during which we can see xe-y/0/0 becoming the primary slave & PTP clock getting synched.
Yes I see that offset values are very high in the non working SINT interface xe-x/0/0 due to which clock is not getting synched. You can try bouncing the interface & re-configuring for this problematic interface(xe-x/0/0) only.
However These high offset usually depends on upstream Need to check on the upstream source which is external to the device.