This read-create Integer32, ranging 1 to 255, sets the network-wide priority of this clock source when configured for NCDP, where the lowest positive numeric value wins as highest priority, and per the description the NCDP algorithm falls back to other tiebreakers if multiple sources share the same priority. An admin sets this to steer which of several candidate clock sources across the network should be preferred as the root of the distribution tree. Assigning priority 1 to a highly stable BITS-fed source and higher numbers to backup sources ensures the network prefers the most reliable timing reference first.