When setting up  GrandMaster clock using the DU profile and PtpConfigDualCardWPC example configuration, I needed to set a specific value for the PTP grandmaster 'priority2' field in order to enforce useful time selection in our lab.  However, the cluster-compare templates we have hard-code this value and the value of the 'priority1' field to 128, and the value of the 'domain' to 24.  These are all expected to be user-settable and do not have performance implications, so our cluster-compare template should allow them to be any (valid) value
    

All
    

1000%
    

    1. Set up an SNO with the DU profile and a GrandMaster configuration based on either of the WPC examples
    2. Change the priority1 priority2 and/or domain fields to some other value
    3. Run cluster-compare
    

@@ -101,7 +109,7 @@
       #
       twoStepFlag 1
       priority1 128
-      priority2 128
+      priority2 64
       domainNumber 24
       #utc_offset 37
       clockClass 6
    

No difference detected