Hi Richard,
It worked! I can now view the status of the ptp4l channels independently.
Thanks,
Daniel
-----Original Message-----
From: Richard Cochran <richardcoch...@gmail.com>
Sent: Sunday, September 27, 2020 8:57 PM
To: Zuckerbrod, Daniel <dzuckerb...@textronsystems.com>
Cc: Jacob Keller <jacob.e.kel...@intel.com>;
linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] PMC Reporting portState: Slave When Interface Not
Active
On Sun, Sep 27, 2020 at 06:36:07PM +0000, Zuckerbrod, Daniel wrote:
> Would that be by telling it which /dev/ptpx I am using?
No, the way to do it is to have each ptp4l instance have its own Unix Domain
Socket (UDS) for local management messages. Use the following ptp4l
configuration option for this.
uds_address
Specifies the address of the UNIX domain socket for receiving
local management messages. The default is /var/run/ptp4l.
Then, you should tell pmc to select the UDS address of the ptp4l instance of
interest. For that, use the following pmc command line options.
-u Select the Unix Domain Socket transport.
-b boundary-hops
Specify the boundary hops value in sent messages. The default is
1.
-d domain-number
Specify the domain number in sent messages. The default is 0.
-s uds-address
Specifies the address of the server's UNIX domain socket. The
default is /var/run/ptp4l.
For example:
ptp4l -i eth0 --uds_address /var/run/ptp4l.eth0
pmc -u -s /var/run/ptp4l.eth0
HTH,
Richard
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
