On Mon, May 30, 2016 at 01:58:42PM +0000, Rohit Borse wrote: > From PTP Master side code, can we know the PTP clock time status of > Remote Slave node using programmatic approach rather than using pmc > command.
If you don't want to use the pmc program, then you can send the appropriate management messages directly. See pmc_common.h and pmc_common.c for an example. > eg. If master A needs that clock time of master A is not in sync > with clock time of slave B, to send some signal to any dependent > module which would be helpful. That is not the way it works. If node A wants information about node B, then node A must request it. For your case, this implies that A will poll the state of B. > So how master A can know if PTP time of slave B is not in sync/or in > sync. 1. Send the "GET PORT_DATA_SET" request and check that portState is SLAVE. 2. Send the "GET CURRENT_DATA_SET" request and check offsetFromMaster. > Currently we are planning to decide if Maser clock is not in sync > with slave Clock, if pDelayReq message is not sent by Slave for some > defined timeout. Is this suitable logic? No, that won't work at all. The delay requests are sent periodically, regardless of the synchronization status. Cheers, Richard ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
