On-site PTP synchronization failed, client directly connected to clock source

  • 0 Followed
  • 0Collected ,43Browsed

Network Topology

 


Problem Description

On-site PTP synchronization failed, client directly connected to clock source

Process Analysis

View configuration

ptp profile st2059-2

ptp mode bc

ptp domain 127

ptp time-offset suppression-threshold 900 suppression-count 40

ptp source 10.10.10.1

 

 interface Twenty-FiveGigE1/0/48

port link-mode bridge

speed 1000

 undo stp enable

ptp announce-interval 0

ptp min-delayreq-interval -3

ptp enable

Debugging revealed the following error

*Mar 27 15:31:24:301 2025 SDN01 PTP/7/ERROR: Instance 0 on interface Twenty-FiveGigE1/0/48 detected link fault, the peer port is out of response.

*Mar 27 15:31:24:330 2025 SDN01 PTP/7/PACKET:

InstanceID 0 on Twenty-FiveGigE1/0/48 received an Announce packet with length 64.

Transport specific        : 0x0

Message type              : Announce

PTP version               : 2

Message length            : 64

Domain number             : 127

Flag field                : 0x003C

Correction field          : 0

Source clock ID           : EC4670-FFFE-0AC385

Source port number        : 1

Sequence number           : 51072

Control field             : 5

Log message interval      : -2

Origin timestamp          : 0

Current UTC offset        : 37

Grandmaster clock quality :

Class                    : 6

Accuracy                 : 33

Offset (log variance)    : 13056

Grandmaster priority1     : 127

Grandmaster priority2     : 2

Grandmaster ID            : EC4670-FFFE-0AC385

StepsRemoved              : 0

Time source               : 0x20

 

 

 

Interface IfName detected a link error due to mismatched delay mechanisms on both ends.

The peer delay mechanism is E2E

Solution

Normal after modifying the delay mechanism

ptp delay-mechanism e2e

 

Please rate this case:   
0 Comments

No Comments

Add Comments: