Some of the recommended PTP parameters for ordinary and boundary clock do not match the values included in https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.12/ztp/source-crs/PtpConfigSlave.yaml and https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.12/ztp/source-crs/PtpConfigBoundary.yaml, causing confusion to customers and partners on what are the parameters they should use.

Seen at least in the OCP 4.12 and 4.13 documentation

Always

1. Compare the "Recommended PTP ordinary clock configuration" and "Recommended PTP boundary clock configuration" from the documentation at https://docs.openshift.com/container-platform/4.12/networking/using-ptp.html#configuring-linuxptp-services-as-boundary-clock_using-ptp with the corresponding values in the https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.12/ztp/source-crs repository

The following ptp4lConf values are different:

30c31
<   fault_reset_interval 4    (this is in the documentation)
---
>   fault_reset_interval -4   (this is the repo)
53a55
>   clock_class_threshold 7   (this parameter is present in the repo and missing in the documentation)

Same recommended values in both places for consistency.