[c-nsp] PTP design

[Raymond Lucas (AP)]

James,

When I went looking at PTP a year or so ago, the best resources I managed to find were these:

http://blog.meinbergglobal.com/category/ieee1588/

You might find some of you answers there.  We didn’t end up implementing anything meaningful so I can’t offer real world suggestions unfortunately.

Ray

From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of james list
Sent: Wednesday, 21 September 2016 5:01 a.m.
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] PTP design



Hi experts!

More than a vendor related question I’m wondering to discuss or get hints
regarding the upcoming mifid2 new PTP request (max divergence from UTC of 1
microsecond) implementation that will be requested since Jan 2018.

I’d like to setup in my DC two fully redundant PTP source, for this reason
I’m planning to use two different antennas, coax and supplier, but here the
first doubts:

- What is best design to provide redundancy ?

- Do I have to use multicast or unicast (like NTP) ?

- Is there any scalability issue ?

- If I use multicast, which are the multicast group used by the
PTP vendors ? Is there any ietf assigned group ?

- Do I have to dedicate a single dedicated vlan where the server
has to connect to get the multicast packets ?

I’ve many doubts and maybe we can share some commons ideas if anybody else
is going to setup the service…


Thanks in advance for any feedback


Regards

James
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


itevomcid