Gah, sorry - I goofed and pulled the 'ps' output from a different box than
the config. That indeed is the domain and does match the conf for any given
machine, but not when I mix'n'match (ttl, domain, and transport are
site-specific).
>From the problematic box:
bash-4.3# cat /etc/ptp4l.conf
[glob
On Wed, Apr 05, 2017 at 09:18:09AM +1000, David Mirabito wrote:
> The config is:
>
> [global]
> slaveOnly 1
> summary_interval 6
> priority1 255
>
> [ma2]
>
> And running as:
>/usr/sbin/ptp4l -f /etc/ptp4l.conf
>/usr/sbin/phc2sys -a -r -u 64 -n 5
Why are you using domain number 5 for ph
Hi,
The device is a:
00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354
(rev 03)
Using
bash-4.3# ethtool -i ma2
driver: igb
version: 5.3.0-k
firmware-version: 0.0.0
expansion-rom-version:
bus-info: :00:14.1
supports-statistics: yes
supports-test: yes
s
Possibly following on from David’s post.
We have a system with 18 boards in a rack, each board has a Altera SoC with the
STM Ethernet MAC connected via gigabit Ethernet to an Arista ptp-aware switch
and then a Spectracom GrandMaster.
The boards are running Linux kernel 3.15.0.
They lock quickly
On Tue, Apr 04, 2017 at 06:52:21PM +1000, David Mirabito wrote:
> Is it safe to assume, that given a crappy PTP network ptp4l would just
> degrade to ntp-like performance at worst? Or are there some other
> thresholds or sanity checks which would cause it to throw in the towel in
> situations where
