PTP is supported over direct Ethernet encapsulation (that is, PTP ports) and UDP/IP encapsulation (that is, PTP peers). PTP ports operate below the routing plane. They can be used on appropriate ports irrespective of any type of router interface also on the port. PTP peers operate at the routing plane and have restrictions based on and across the following router instances.
Transmission and reception of PTP messages using PTP peers is supported in the following contexts:
Network interface in the Base routing instance (config>router>interface)
IES interface (config>service>ies>interface)
VPRN interface (config>service>vprn>interface)
Transmission and reception of PTP messages using PTP peers is not supported in the following contexts:
IES spoke SDP interface (config>service>ies>spoke-sdp>interface)
VPRN spoke SDP interface (config>service>vprn>spoke-sdp>interface)
VPRN transport tunnel (config>service>vprn>auto-bind-tunnel or config>service>vprn>spoke-sdp)
Any interface of the management router instance
Any interface of the vpls-management router instance
Any interface of a user created CPM router instance
It is important to note that there is only one PTP clock within the router. All PTP ports and PTP peers communicate into one clock instance. Only one router instance may have PTP peers configured, which means that only that router instance (or PTP port) can run the slave functionality and recover time from an external PTP clock. All other router instances only support the dynamic PTP peers. The PTP process in the router only includes outward server time toward the dynamic PTP peers. The dynamic PTP peers are shared across all router instances. If it is needed to control the number of dynamic peers that can be consumed by a routing instance, then it must be configured for that routing instance.