On Sat, Nov 30, 2013 at 09:46:46PM +0100, Delio Brignoli wrote:
>
> Yes, but... 802.1AS does not have a different state machine for
> slave-only operation, instead a non grand-master capable time-aware
> system has a property1 value of 255 (see second paragraph of section
> 8.6.2.1). Additionally, according to point f.5 of section
> 10.3.12.1.4 updtRolesTree(), if the current portPriorityVector is
> the portPriorityVector of the time-aware system (i.e. we have not
> yet received an announce message with better portPriorityVector) the
> portRole should be set to MasterPort which makes the txAnnounce
> method reachable.
This brings to mind two questions.
1. Does omitting the announce message from a slave only node cause you
interoperability problems?
2. What is the point of the slave only node's announce messages?
[ The announce messages will not affect the outcome of the peer's
BMC election, except to make it slower. ]
Thanks,
Richard
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Linuxptp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
