Symptom

On a platform that supports multiple PTP source tracking, a change to one of the tracked sources causes the advertized clock class to drop to the uncalibrated clock class (which will vary depending on the profile in use; could be 135, 165, or a configured value).

Conditions

The platform must support multi-source tracking, which can be checked with: RP/0/0/CPU0:ios#show ptp ctrlr database | inc multi Thu Oct 10 12:45:12.659 PDT Platform supports tracking multiple timing sources = FALSE The most likely cause of this issue is having more than 1 qualified source, and then a source being removed or added. These should not affect the servo state and so the advertized clock class should stay the same, but instead it drops.

Workaround

None; the condition recovers automatically.

Further Problem Description