Loading...
Loading...
Clock Syntonized shows FALSE in PTP Transparent clock (TC) mode as below : #sh ptp clock dataset time-properties CLOCK [Transparent Clock, domain 10] Current UTC Offset Valid: FALSE Current UTC Offset: 0 Leap 59: FALSE Leap 61: FALSE Time Traceable: FALSE Frequency Traceable: FALSE PTP Timescale: FALSE Time Source: Internal Oscillator Clock Syntonized: FALSE <<<<<<
GM1-----TC----GM2 When two or more Grandmaster(GM) clocks are present in the network and when switchover happens from one GM to another via interface shutdown or link down on the TC, the show command does not reflect Clock syntonized status correctly. There would be no issue in the functionality however.
User can remove and re-add the Transparent clock configuration to overcome the issue. no ptp clock transparent domain ptp clock transparent domain
To verify the functionality is not affected and whether it is only a display issue, enable PTP debugs and check PTP logs for the SERVO status lock. It should show as below : 2021/11/19 13:17:58.620714525 {timingd_R0-0}{1}: [iot-ptp] [4962]: (debug): [srvo] SRVO lock state:4 state:4 indicates that SRVO is in locked state and there is no issue in the functionality
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.