Hi John,

I just realized that my unicast_request_duration was set to default (3600 sec). 
Setting it to a lower values (like 10 seconds) made the ptp client reelect the 
grand master and get tuned without any problem.

Hope it helps.

Regards,
Jawad

________________________________
From: John Lemonovich <john.lemonov...@foresys.com>
Sent: Monday, February 25, 2019 8:31 PM
To: jawad ahmed saleemi; linuxptp-users@lists.sourceforge.net
Subject: RE: [Linuxptp-users] Udpv6 support in unicast mode


Jawad,



We’re having the exact same issue.  Our slaves are various Intel FPGA Arria 10 
SoC FPGAs and our application is using 802.1AS (gPTP) – not unicast.  I did 
capture all the packets in tshark during the GM down and back up sequence, but 
even after the announce messages start coming in again from the GM – the slave 
won’t re-select our GM as the BMC.  If I restart ptp4l and/or bring the network 
interface down and back up – it will then resync.  I wondered what would happen 
if I set the gmCapable to 0, but our slaves still assume the GM role, even with 
this set to 0.  Let me know if you find something, and I’ll do the same.



Thanks,

John



From: jawad ahmed saleemi <jawad.sale...@hotmail.com>
Sent: Monday, February 25, 2019 5:36 AM
To: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] Udpv6 support in unicast mode



Hi,



In unicast mode, does the ptp4l slave recover if the grand master goes down and 
come up again. I am testing my setup in the unicast mode and when I restart the 
ptp grand master, the ptp slave does not reconnect to the grand master. I have 
to restart the ptp slave as well for it to chose the grand master again.



Here are my settings on the slave machine.



[ni6]

syncReceiptTimeout              0

network_transport               UDPv4

logSyncInterval         0

logMinPdelayReqInterval         0

logMinDelayReqInterval          0

announceReceiptTimeout          10

unicast_master_table    1



[unicast_master_table]

table_id                1

logQueryInterval                0

UDPv4           10.10.85.11





[global]



unicast_req_duration            3600

unicast_listen          1

uds_address             /var/run/ptp4l

udp_ttl         20

udp6_scope              0x0E

tx_timestamp_timeout            1

twoStepFlag             1





p2p_dst_mac             01:80:C2:00:00:0E

offsetScaledLogVariance         0xFFFF

ntpshm_segment          0

network_transport               UDPv4

net_sync_monitor                0

neighborPropDelayThresh         20000000

max_frequency           900000000

masterOnly              0



inhibit_multicast_service               1

ingressLatency          0

hybrid_e2e              1



dataset_comparison      ieee1588

clock_type              OC

clockClass              248

clockAccuracy           0xFE

assume_two_step         0



Any help would be much appreciated.

Thanks.



Best regards,

Jawad

________________________________

From: jawad ahmed saleemi 
<jawad.sale...@hotmail.com<mailto:jawad.sale...@hotmail.com>>
Sent: Thursday, February 21, 2019 7:26 PM
To: 
linuxptp-users@lists.sourceforge.net<mailto:linuxptp-users@lists.sourceforge.net>
Subject: [Linuxptp-users] Udpv6 support in unicast mode



Hello all,



We are using linuxptp at our work place and I was wondering why there is no 
support for Udpv6 in the unicast mode. I can not think of any technical reasons 
for that since it is supported in multicast mode via network_transport 
parameter.



Hoping to understand it better ??





Thanks.



Best regards,

Jawad




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

Reply via email to