PTP Multiprofile Restrictions
-
A maximum of three interop profiles with different domain numbers can be supported on the Cisco router.
-
The server clock profile must be mutually exclusive with the interop profile. For example, if the server clock profile is default profile, then the interop profile must not be the default profile.
-
The Interop port works as the server port. It cannot be used as a client port.
-
ITU-T G.8265.1 is not supported as the Interop profile.
-
All interop ports with the 1588-default profile or the G.8275.2 profile must use the same loopback interface as the server server port.
-
A server clock and port must be created before creating an Interop port.
-
The server clock must be hybrid if the interop port is running the G.8275.1 profile.
-
While configuring the PTP multiprofile, the best practice is to reduce the number of hops between the PTP grandmaster clock and the PTP slave router. We recommend a maximum of eight hops to mitigate network delays. You can check the number of hops between the PTP grandmaster and the PTP slave by executing the following command in the PTP slave router: Router#show ptp clock dataset current CLOCK [Boundary Clock, domain 44] Steps Removed: 7 Offset From Master: -1981ns Mean Path Delay: -443ns