On Fri, Aug 10, 2018 at 12:14:21PM +1000, David Mirabito wrote: > We can stop the resets by adding `logAnnounceInterval 3` to the client > config to match the master, which we could consider a fix,
Right. > I had assumed: > * logAnnounceInterval would be how often we send an announce in the Master > state, thus is a property of the master No, it is defined by the profile, and all nodes must be use the same value. > * Since the Announce message contains the master's logAnnounceInterval (as > logMessageInterval), clients would wait their receiptTimeout multiples of > *that* time before complaining, otherwise we see this scenario where the > master explicitly says "I will announce every 8 seconds" and a client with > default config will be unhappy when a new announcement doesn't come within > 6 seconds. Although one could imagine the client to read the interval from the Announce message, there is nothing in 1588 that mandates this behavior. > I couldn't find much in 1588-2008 to see whose logAnnounceInterval controls > the an AnnounceReceiptTimeout transition - I suppose this means always use > local values, and clients don't "inherit" values from the master. Right. I think 1588 is clear on this point. In the few cases where configuration values can change dynamically at run time, this behavior is spelled out in detail. The portDS.logAnnounceInterval falls under: 8.2.5.4 Configurable members of the portDS data set There is a distinction between "configurable" and "dynamic". See 8.1.2. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
