Hi
I have a node synced to external GM, on bringing the node interface
down, the system is still showing in sync state.
PTP configuration:
[global]
#
# Default Data Set
#
tx_timestamp_timeout 50
twoStepFlag 1
slaveOnly 1
priority1 128
priority2 128
domainNumber 24
#utc_offset 37
clockClass 255
clockAccuracy 0xFE
offsetScaledLogVariance 0xFFFF
free_running 0
freq_est_interval 1
or
"[{\"name\":\"pool3_profile\",\"interface\":\"0000:4b:00.0\",\"ptp4lOpts\":\"-s
-2\",\"phc2sysOpts\":\"-a -r -n 24 --step_threshold=1
--summary_interval -4\",\"ptp4lConf\":\"[global]\\n#\\n# Default Data
Set\\n#\\ntx_timestamp_timeout 50\\ntwoStepFlag
1\\nslaveOnly 1\\npriority1
128\\npriority2
128\\ndomainNumber 24\\n#utc_offset
37\\nclockClass 255\\nclockAccuracy
0xFE\\noffsetScaledLogVariance
0xFFFF\\nfree_running 0\\nfreq_est_interval
1\\n\",\"ptpSchedulingPolicy\":\"SCHED_FIFO\",\"ptpSchedulingPriority\":10,\"ptpClockThreshold\":{\"holdOverTimeout\":5,\"maxOffsetThreshold\":600,\"minOffsetThreshold\":-600}}]"
},
ptp4l & phc2sys logs:
I0823 06:21:35.362239 931306 daemon.go:136] Phc2sysOpts: -a -r -n 24
--step_threshold=1 --summary_interval -4 -m -z /var/run/ptp4l.0.socket
-t [ptp4l.0.config]
I0823 06:21:35.362242 931306 daemon.go:136] PtpSchedulingPolicy: SCHED_FIFO
I0823 06:21:35.362245 931306 daemon.go:140] PtpSchedulingPriority: 10
I0823 06:21:35.362248 931306 daemon.go:207]
------------------------------------
I0823 06:21:35.362253 931306 daemon.go:317] /bin/chrt -f 10
/usr/sbin/phc2sys -a -r -n 24 --step_threshold=1 --summary_interval -4
-m -z /var/run/ptp4l.0.socket -t [ptp4l.0.config]
I0823 06:21:35.362288 931306 daemon.go:317] /bin/chrt -f 10
/usr/sbin/ptp4l -f /var/run/ptp4l.0.config -s -2 -m
I0823 06:21:36.362339 931306 daemon.go:370] Starting phc2sys...
I0823 06:21:36.362353 931306 daemon.go:371] phc2sys cmd: /bin/chrt -f
10 /usr/sbin/phc2sys -a -r -n 24 --step_threshold=1 --summary_interval
-4 -m -z /var/run/ptp4l.0.socket -t [ptp4l.0.config]
I0823 06:21:36.362449 931306 daemon.go:347]
phc2sys[1692771696]:[ptp4l.0.config] PTP_PROCESS_STATUS:1
I0823 06:21:37.362513 931306 daemon.go:370] Starting ptp4l...
I0823 06:21:37.362534 931306 daemon.go:371] ptp4l cmd: /bin/chrt -f
10 /usr/sbin/ptp4l -f /var/run/ptp4l.0.config -s -2 -m
I0823 06:21:37.362642 931306 daemon.go:347]
ptp4l[1692771697]:[ptp4l.0.config] PTP_PROCESS_STATUS:1
phc2sys[110285.573]: [ptp4l.0.config] Waiting for ptp4l...
option slaveOnly is deprecated, please use clientOnly instead
ptp4l[110285.573]: [ptp4l.0.config] selected /dev/ptp5 as PTP clock
ptp4l[110285.618]: [ptp4l.0.config] port 1 (ens2f0): INITIALIZING to
LISTENING on INIT_COMPLETE
ptp4l[110285.618]: [ptp4l.0.config] port 0 (/var/run/ptp4l.0.socket):
INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[110285.618]: [ptp4l.0.config] port 0 (/var/run/ptp4lro):
INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[110285.618]: [ptp4l.0.config] port 1 (ens2f0): LISTENING to
FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[110285.618]: [ptp4l.0.config] port 1 (ens2f0): unexpected socket error
ptp4l[110285.682]: [ptp4l.0.config] port 1 (ens2f0): link down
ptp4l[110285.682]: [ptp4l.0.config] selected local clock
b49691.fffe.bafa00 as best master
ptp4l[110285.682]: [ptp4l.0.config] port 1 (ens2f0): master state
recommended in slave only mode
ptp4l[110285.682]: [ptp4l.0.config] port 1 (ens2f0): assuming the
grand master role
ptp4l[110285.682]: [ptp4l.0.config] port 1 (ens2f0):
defaultDS.priority1 probably misconfigured
phc2sys[110286.573]: [ptp4l.0.config] Waiting for ptp4l...
phc2sys[110287.574]: [ptp4l.0.config] reconfiguring after port state change
phc2sys[110287.574]: [ptp4l.0.config] selecting ens2f0 for synchronization
phc2sys[110287.574]: [ptp4l.0.config] selecting CLOCK_REALTIME as the
master clock
phc2sys[110287.574]: [ptp4l.0.config] ens2f0 sys offset 37 s0
freq -13085 delay 435
phc2sys[110288.575]: [ptp4l.0.config] ens2f0 sys offset 23 s2
freq -13099 delay 504
phc2sys[110289.575]: [ptp4l.0.config] ens2f0 sys offset 30 s2
freq -13069 delay 504
phc2sys[110290.576]: [ptp4l.0.config] ens2f0 sys offset 6 s2
freq -13084 delay 514
phc2sys[110291.576]: [ptp4l.0.config] ens2f0 sys offset 3 s2
freq -13085 delay 505
phc2sys[110292.576]: [ptp4l.0.config] ens2f0 sys offset -19 s2
freq -13106 delay 506
phc2sys[110293.577]: [ptp4l.0.config] ens2f0 sys offset -29 s2
freq -13122 delay 504
phc2sys[110294.577]: [ptp4l.0.config] ens2f0 sys offset -14 s2
freq -13116 delay 504
phc2sys[110295.578]: [ptp4l.0.config] ens2f0 sys offset 1 s2
freq -13105 delay 510
timedatectl output:
eccd@pool3-dc286-wk3-srv5-1003:~> timedatectl
Local time: Wed 2023-08-23 07:17:42 UTC
Universal time: Wed 2023-08-23 07:17:42 UTC
RTC time: Wed 2023-08-23 07:17:42
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
I think phc2sys is still syncing to the local phc clock in nic.
I was thinking node will go to a non synchronized state on interface
down, why is it taking the GM role, even after giving clientOnly
option?
Any pointers?
-Nobin
_______________________________________________
Linuxptp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
