7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
System management
• Assume port 1/1/10 is connected to a PTP timeTransmitter clock (using a port, a SAP, or an IES IP
interface) and 1/1/15 is connected to a PTP timeReceiver clock (using a port, a SAP, or an IES IP
interface).
To enable PTP TC in this scenario, you must enable the ptp-hw-timestamp command on both ports. To
disable PTP TC, run the no form of the command on both ports.
• Assume port 1/1/10 is connected to a PTP timeTransmitter clock (using a port, a SAP, or an IES IP
interface) and ports 1/1/15 and 1/1/16 have PTP timeReceivers (using a port, a SAP, or an IES IP
interface), with a PTP session to the PTP timeTransmitter clock that is connected on port 1/1/10.
To enable PTP TC, the ptp-hw-timestamp command must be enabled on all three ports.
In this scenario, it is not possible to disable PTP TC only towards the timeReceiver connected on port
1/1/15. The functionality must be disabled on all three ports.
Additionally, note that the PTP messages coming in on port 1/1/10 are not forwarded out of any ports
other than 1/1/15 and 1/1/16, when the ptp-hw-timestamp command is enabled on port 1/1/10. Nokia
recommends that when a set of PTP ports are enabled for ptp-hw-timestamp, the operator must
ensure that PTP messages are forwarded to only the specific set of ports where the TC option is
enabled, and not to other ports. Forwarding PTP messages to other ports that do not belong to the
specific set may result in incorrect updates.
• You can enable PTP TC for a set of SAPs and also transparently forward PTP packets on other SAPs,
while both SAPs share a common uplink to forward PTP messages. To implement this scenario, use
MPLS tunnels with network ports as the uplinks. Nokia recommends the following configuration.
– PTP hardware port-based timestamping must be disabled on the access ports where SAPs are
configured. These access ports are typically used to connect to either PTP timeTransmitter or PTP
timeReceivers that need to establish and exchange PTP messages transparently.
– PTP hardware port-based timestamping must be enabled on the access ports where SAPs are
configured and the TC function is required. These access ports are typically used to connect to
either the PTP timeTransmitter or PTP timeReceivers.
– PTP hardware port-based timestamping must be enabled on the network ports where the MPLS
tunnels originate and terminate. In this case, the PTP TC function updates only the PTP messages
that are not MPLS encapsulated.
– See PTP message transparent forwarding for additional support information.
6.5.7.4 PTP message transparent forwarding
On bootup, port-based hardware timestamping is enabled by default on all ports on the 7210 SAS-Mxp,
7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx 1/10GE, 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28, and
7210 SAS-T, and the node processes both transit packets and locally destined PTP packets. Use the ptp-
hw-timestamp command to disable port-based hardware timestamping in the following cases:
• to allow the node to transparently forward PTP packets when MPLS uplinks are used
• when PTP is enabled and used to synchronize and time the node (that is, PTP messages are originated
and terminated by the node acting as a PTP OC-timeReceiver or BC)
• on ports that receive PTP packets that will be forwarded transparently
When PTP port-based hardware timestamp is disabled, the node does not update the correction field
in PTP messages. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more
information about the ptp-hw-timestamping command.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
274
SPACER TEXT
To Next Page
Loading...