Re: [Linuxptp-users] ptp4l and Broadcom 5720 problem
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
From: Jay S. <li...@sh...> - 2022-06-07 09:13:44
|
On 07/06/2022 09:17, Miroslav Lichvar wrote: > On Mon, Jun 06, 2022 at 04:10:19PM +0100, Jay Shardlow wrote: >> Hello all, after a bit of advice/help. I've got some CentOS 7 servers and I >> need to get them running ptp4l (from linuxptp) as clients, with the >> grandmaster being a Meinberg appliance. One with an Intel i350 works fine. >> Another with a Broadcom 5720 does not. Both servers are connected to the >> same network for their PTP. I suspect I know why the Broadcom doesn't work, >> but I was wondering if anyone could point me in the right direction on how >> to get it to do so. > > Do the servers have the same configuration? Usually it's a firewall > issue. If the issue was with missing timestamps, ptp4l would print an > error. In my experience, BCM5720 works fine with UDPv4 PTP. > They're not identical, but they're both CentOS 7.9 running linuxptp 2.0.2. No firewall on the Broadcom server. To my untrained eye the only real difference is the Hardware Recieve Filter Modes. Elsewhere in our environment we have combos of Solarflare/sfptpd, Intel i350/ptpd, Intel X520/ptpd which all work fine, though they either support HWTSTAMP_FILTER_ALL or at least HWTSTAMP_FILTER_PTP_V2_EVENT. Though I've literally just read that ptp4l prefers to have HWTSTAMP_FILTER_PTP_V2_EVENT, but will fall back to HWTSTAMP_FILTER_PTP_V2_L4_EVENT or HWTSTAMP_FILTER_PTP_V2_L4_EVENT (the latter two available on the Broadcom). At this point I'm slightly out of my depth and out of ideas. The Broadcom obviously does work (or they wouldn't advertise it as such), so must be something with my environemnt, but I have no idea what. J |