Hello Miroslav, Thanks for the input. I tried the method you suggested and one step change is working fine.
*Sequence followed:* My test setup contains 11 TSN nodes and switched on the Grand Master node first and switched on the rest of the 10 nodes one by one and they came into sync within my bounded time. *Problem:* If the GM is not switched ON then the one step jump is not happening, could you please let me know how to enable the nodes to have "multiple steps" so that I need not worry about the above sequence On Tue, 6 Aug 2019 at 13:04, Miroslav Lichvar <mlich...@redhat.com> wrote: > On Tue, Aug 06, 2019 at 12:58:11PM +0530, Alexander Sylvester wrote: > > HI Miroslav, > > > > So are you saying that each time I connect my Slave node, I have to make > > sure that my GM is running already and if I do so ptp4l should be able > > to make a step on the first update of the clock and reach synchronization > > much faster? Is my understanding correct? > > Yes. It's one way to get your requirements. ptp4l by default allows > one step on the first update. I think you either need to make sure the > first update is from the intended GM and not some random clock that > happens to be the GM before the real one is running, or allow multiple > steps, assuming that's really the problem you are hitting. > > -- > Miroslav Lichvar >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
