Dear all,
I would know about the difference behaviour of pmc when launched on the 
ethernet interface or on the UDS. Suppose that I would get the PORT_DATA_SET of 
the local port. To do this I run pmc as follow:

$ sudo -E ./pmc -b 0 -i eth1 "GET PORT_DATA_SET"
sending: GET PORT_DATA_SET
                008063.fffe.db5d80-1 seq 0 RESPONSE MANAGEMENT PORT_DATA_SET
                                portIdentity            008063.fffe.db5d80-1
                                portState               INITIALIZING
                                logMinDelayReqInterval  3
                                peerMeanPathDelay       0
                                logAnnounceInterval     1
                                announceReceiptTimeout  3
                                logSyncInterval         0
                                delayMechanism          1
                                logMinPdelayReqInterval 0
                                versionNumber           2
                008063.fffe.db5d80-2 seq 0 RESPONSE MANAGEMENT PORT_DATA_SET
                                portIdentity            008063.fffe.db5d80-2
                                portState               MASTER
                                logMinDelayReqInterval  3
                                peerMeanPathDelay       0
                                logAnnounceInterval     1
                                announceReceiptTimeout  3
                                logSyncInterval         0
                                delayMechanism          1
                                logMinPdelayReqInterval 0
                                versionNumber           2
...

$ sudo -E ./pmc -b 0 -u "GET PORT_DATA_SET"
sending: GET PORT_DATA_SET
                00106f.fffe.223fc9-1 seq 0 RESPONSE MANAGEMENT PORT_DATA_SET
                                portIdentity            00106f.fffe.223fc9-1
                                portState               SLAVE
                                logMinDelayReqInterval  3
                                peerMeanPathDelay       0
                                logAnnounceInterval     1
                                announceReceiptTimeout  3
                                logSyncInterval         0
                                delayMechanism          1
                                logMinPdelayReqInterval 0
                                versionNumber           2

Using the ethernet interface I get the port dataset of all ports of the 
Boundary Clock where my local port is connected, but not the port dataset of 
the local port. Using UDS I get the port dataset of the local port but not of 
the boundary clock. Is there any special reason about this difference? Am I 
doing something wrong? It is a matter of standard or simply an implementation 
detail? I was using version 1.3 but I have seen it is the same on 1.6.

Thank you all

William


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to