Hi Dennis, Op 10-12-21 om 13:21 schreef Dennis Hagarty (dehagart):
the profile can have a large influence on this.
What PTP profiles are you using and what transport (L2 or L3?) What are the two BC's sending out in their announce message? How is the OC connected to VLAN2? Is it using another switch?
Let me try to answer your questions at the risk of saying silly being the rookie that I am.
At the moment I'm testing my setup in an VM-environment with 5 guests on a host, to see if it is a viable concept. In the ultimate situation it will consist of physical servers, switches and hardware timestamping, geographically separated. The OC might be on another switch.
The reason for creating VLAN 2 is because I wouldn't want to allow (untrusted) clients in VLAN1.
Both BC's send the grandmasterClockIdentity and other fields (like TimeSource) of the true, current GM in VLAN1, as well as their own unique ClockIdentity. And they adapt well, if BMCA causes a flip. So they seem to pass all that information on quite well, like a BC should, I assume.
I believe I'm using a custom PTP profile, because I took the default configuration of ptp4l and fiddled around a bit with a couple of settings.
My transport is L3-E2E multicast (tried unicast too, but that was not an improvement per se).
In VLAN1 everything works well. There's a GM and a backup-clock. And the two BC's behave as slaves/followers.
In VLAN2 I have my doubts. Both BC's seem to be in a master role and the OC appears to use them both more or less alternating, whereas I would prefer/expect one of the BC's to be silent and only become active when needed.
So, I guess my primary question (for now) is: if this approach is at all good practice; is it possible to have two BC's in one VLAN?
I found a picture on https://en.wikipedia.org/wiki/Precision_Time_Protocol_Industry_Profile that resembles what I have in mind, with one exception:
https://en.wikipedia.org/wiki/File:IEEE_1588_Network_Elements_170208_HK.jpgIn my plan, there are no subdomain B an C. Just one cloud, with two available BC's for redundancy.
Thanks for your help! -- Marco
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
