Hi ANG,
Let's clarify the different ways people us PTP/gPTP:
1) PTP Multicast Transport Between Endpoints
-> Basic deployments where PTP is passed between endpoints via multicast is supported on all EXOS platforms.
-> In this case, PTP is treated like any other multicast traffic and the switch does not participate in PTP clocking operations
-> Specific configuration is generally not needed here, IGMP and IGMP snooping are enabled by default for all VLANs to facilitate multicast transport.
Related:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000079341&q=dante
2) PTP Clock Operation by Switches
-> If you want the switch to participate in PTP clocking operations, you'll need to be on specific platforms that have the relevant hardware to support PTP operation. This is a less common setup, hence not supported on many switches.
-> The switch can behave as a transparent clock, boundary clock, etc.
Related:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000081476&q=ptp%20configuration
3) gPTP Clock Operation by Switches
-> gPTP is often used in Audio/Video networks for AVB operation.
-> This is supported on most platforms that support the AVB feature pack ('enable AVB ports ...')
-> In this deployment, the switch does participate in gPTP time sync between endpoints
Most people using PTP are in bucket #1 where PTP is just passed between endpoints.
If you actually need the switch to participate in PTP clocking operations, you'll need specific hardware (sometimes a license as well).
Otherwise, gPTP is supported on most platforms for AVB (AVB License on non-universal, Base license on most Universal)
Hope that helps!
