Hello folks,

  I have a setup where we have a GM https://timemachinescorp.com/product/ptp-network-time-server-tm2000a/ and a linux client that works fine in the unicast setup we have. All is fine until the time server for some reason reboot. At that point the ptp4l daemon on the linux machine never sees the master clock even though its up and running.

Apr 01 21:12:03 oak ptp4l[11854]: [594698.101] selected /dev/ptp0 as PTP clock Apr 01 21:12:03 oak ptp4l[11854]: [594698.101] port 1: INITIALIZING to LISTENING on INIT_COMPLETE Apr 01 21:12:03 oak ptp4l[11854]: [594698.101] port 0: INITIALIZING to LISTENING on INIT_COMPLETE Apr 01 21:12:04 oak ptp4l[11854]: [594699.892] port 1: new foreign master 0479b7.fffe.d41853-1 Apr 01 21:12:08 oak ptp4l[11854]: [594703.891] selected best master clock 0479b7.fffe.d41853
Apr 01 21:12:08 oak ptp4l[11854]: [594703.891] updating UTC offset to 37
Apr 01 21:12:08 oak ptp4l[11854]: [594703.891] port 1: LISTENING to UNCALIBRATED on RS_SLAVE Apr 01 21:12:10 oak ptp4l[11854]: [594705.937] master offset 108448 s0 freq   -9034 path delay     15522 Apr 01 21:12:11 oak ptp4l[11854]: [594706.943] master offset 107842 s0 freq   -9034 path delay     15522 Apr 01 21:12:12 oak ptp4l[11854]: [594707.950] master offset 108695 s0 freq   -9034 path delay     15568 Apr 01 21:12:13 oak ptp4l[11854]: [594708.959] master offset 108383 s1 freq   -8911 path delay     15568 Apr 01 21:12:14 oak ptp4l[11854]: [594709.966] master offset         -7 s2 freq   -8772 path delay     15568 Apr 01 21:12:14 oak ptp4l[11854]: [594709.966] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED Apr 01 21:12:15 oak ptp4l[11854]: [594710.978] master offset       -144 s2 freq   -9276 path delay     15586 Apr 01 21:12:16 oak ptp4l[11854]: [594711.989] master offset       1236 s2 freq   -7679 path delay     15586 Apr 01 21:12:17 oak ptp4l[11854]: [594712.997] master offset       -506 s2 freq   -8912 path delay     15604 Apr 01 21:12:18 oak ptp4l[11854]: [594714.005] master offset        374 s2 freq   -8285 path delay     15586 Apr 01 21:12:19 oak ptp4l[11854]: [594715.013] master offset       -438 s2 freq   -9161 path delay     15626 Apr 01 21:12:20 oak ptp4l[11854]: [594716.022] master offset       -850 s2 freq   -9412 path delay     15658 Apr 01 21:12:21 oak ptp4l[11854]: [594717.028] master offset       -483 s2 freq   -9813 path delay     15695 Apr 01 21:12:22 oak ptp4l[11854]: [594718.037] master offset       1067 s2 freq   -8244 path delay     15685 Apr 01 21:12:23 oak ptp4l[11854]: [594719.044] master offset         53 s2 freq   -8608 path delay     15821 Apr 01 21:12:24 oak ptp4l[11854]: [594720.053] master offset        637 s2 freq   -8127 path delay     15821 Apr 01 21:12:25 oak ptp4l[11854]: [594721.062] master offset        246 s2 freq   -8394 path delay     15905 Apr 01 21:12:26 oak ptp4l[11854]: [594722.068] master offset       -539 s2 freq   -8808 path delay     15905 Apr 01 21:12:27 oak ptp4l[11854]: [594723.081] master offset       -352 s2 freq   -8922 path delay     15969 Apr 01 21:12:29 oak ptp4l[11854]: [594724.092] master offset       -853 s2 freq   -9038 path delay     15969 Apr 01 21:12:30 oak ptp4l[11854]: [594725.100] master offset        513 s2 freq   -8570 path delay     15818 Apr 01 21:12:31 oak ptp4l[11854]: [594726.109] master offset       -721 s2 freq   -9042 path delay     15818 Apr 01 21:12:32 oak ptp4l[11854]: [594727.116] master offset       -254 s2 freq   -9079 path delay     15721 Apr 01 21:12:33 oak ptp4l[11854]: [594728.125] master offset        687 s2 freq   -8535 path delay     15790 Apr 01 21:12:34 oak ptp4l[11854]: [594729.133] master offset        440 s2 freq   -8478 path delay     15790 Apr 01 21:12:38 oak ptp4l[11854]: [594734.042] port 1: SLAVE to LISTENING on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES Apr 01 21:12:38 oak ptp4l[11854]: [594734.042] selected local clock 64006a.fffe.6ac793 as best master Apr 01 21:12:46 oak ptp4l[11854]: [594741.623] selected local clock 64006a.fffe.6ac793 as best master
The last two lines keep repeating. A restart of the ptp4l daemon recovers from this problem, and i am not sure if that is the expected behavior. I would assume that ptp4l should recover back after it sees the GM again on the network. The GM logs do show that the client has connected up , but ptp4l never shows that in its logs. Am i missing a line in the config ?

--
cheers,

Hussam
(Hussamuddin Nasir)

Netlab & GENI Operations Team

-------------------------------------------------------------------
Laboratory for Adv. Networking  Phone  : (859)218-0059
James F Hardymon Building       Fax    : (859)323-3740
301 Rose Street, Rm 237         E-mail : na...@netlab.uky.edu
Lexington, KY 40506-0495        Web    : http://www.netlab.uky.edu

                        University of Kentucky
                        **********************
-------------------------------------------------------------------



_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to