Precision Time Protocol (PTP) provides time synchronization among devices with submicrosecond accuracy. It provides also precise frequency synchronization.

Basic concepts

PTP profile

PTP profiles (PTP standards) include:

· IEEE 1588 version 2—1588v2 defines high-accuracy clock synchronization mechanisms. It can be customized, enhanced, or tailored as needed. 1588v2 is the latest version.

· IEEE 802.1AS—802.1AS is introduced based on IEEE 1588. It specifies a profile for use of IEEE 1588-2008 for time synchronization over a virtual bridged local area network (as defined by IEEE 802.1Q). 802.1AS supports point-to-point full-duplex Ethernet and IEEE 802.11 links.

· SMPTE ST 2059-2—ST2059-2 is introduced based on IEEE 1588. It specifies a profile specifically for time synchronization of audio or video equipment in a professional broadcast environment. It includes a self-contained description of parameters, their default values, and permitted ranges.

· AES67-2015—AES67-2015 is introduced based on IEEE 1588. It specifies a profile specifically for time synchronization of professional equipment for broadcast, music production, and film and television post-production. It includes a self-contained description of parameters, their default values, and permitted ranges.

PTP domain

A PTP domain refers to a network that is enabled with PTP. A PTP domain has only one reference clock called "grandmaster clock (GM)." All devices in the domain synchronize to the clock.

PTP instance

If the device belongs to multiple PTP domains, you must configure and associate a PTP instance with each PTP domain. You can configure PTP settings such as PTP profile and clock node type on a PTP instance. These settings take effect only on the PTP domain associated with the PTP instance. PTP instances are isolated from each other, allowing different PTP timing systems to run on a network without affecting each other.

Optimal PTP domain

Each PTP instance has a reference clock and clock information. For a device that has multiple PTP instances running simultaneously, you must select an optimal PTP instance and use the clock source traced by this PTP instance to synchronize the system time of the device. The domain with which the optimal PTP associates is the optimal domain.

Clock node and PTP port

A node in a PTP domain is a clock node. A port enabled with PTP is a PTP port. PTP defines the following types of basic clock nodes:

· Ordinary Clock (OC)—A PTP clock with a single PTP port in a PTP domain for time synchronization. It synchronizes time from its upstream clock node through the port. If an OC operates as the clock source, it sends synchronization time through a single PTP port to its downstream clock nodes.

· Boundary Clock (BC)—A clock with more than one PTP port in a PTP domain for time synchronization. A BC uses one of the ports to synchronize time from its upstream clock node. It uses the other ports to synchronize time to the relevant upstream clock nodes. If a BC operates as the clock source, such as BC 1 in Figure 1, it synchronizes time through multiple PTP ports to its downstream clock nodes.

· Transparent Clock (TC)—A TC does not keep time consistency with other clock nodes. A TC has multiple PTP ports. It forwards PTP messages among these ports and performs delay corrections for the messages, instead of performing time synchronization. TCs include the following types:

¡ End-to-End Transparent Clock (E2ETC)—Forwards all PTP packets in the network. It participates in the calculation of the delay on the entire link.

¡ Peer-to-Peer Transparent Clock (P2PTC)—Forwards only Sync, Follow_Up, and Announce messages and terminates other PTP messages. It participates in the calculation the delay on each link.

· Grant-port/request-port—The IEEE 1588 version 2 PTP profile supports unicast negotiation. To configure unicast negotiation, you can specify PTP ports as request-ports or grant-ports. A grant-port grants and provides PTP service. A request-port requests and receives PTP service. Typically, a grant-port is in master state. A request-port is in slave state when selected as the port for time synchronization and in listening state when not selected.

Figure 1 shows the positions of these types of clock nodes in a PTP domain.

IMPORTANT:

When multiple PTP domains are configured on the device, the synchronization performance might fluctuate or decrease, and synchronization failure might occur because of limitation of hardware resources. OC and BC clock nodes do much more work than TCs. As a best practice, configure the device operating in multiple domains as an OC or BC clock node in a maximum of one PTP instance, to decrease calculations, minimize mutual influences between the domains, and optimize the synchronization performance.

Figure 1 Clock nodes in a PTP domain

‌

In addition to these basic types of clock nodes, PTP introduces hybrid clock nodes. For example, a TC+OC has multiple PTP ports in a PTP domain. One port is the OC type, and the others are the TC type.

A TC+OC forwards PTP messages through TC-type ports and performs delay corrections. In addition, it synchronizes time through its OC-type port. TC+OCs include these types: E2ETC+OC and P2PTC+OC.

Master-member/subordinate relationship

The master-member/subordinate relationship is automatically determined based on the Best Master Clock (BMC) algorithm. You can also manually specify a role for the clock nodes.

The master-member/subordinate relationship is defined as follows:

· Master/Member node—A master node sends a synchronization message, and a member node receives the synchronization message.

· Master/Member clock—The clock on a master node is a master clock (parent clock). The clock on a member node is a member clock.

· Master/Subordinate port—A master port sends a synchronization message, and a subordinate port receives the synchronization message. The master and subordinate ports can be on a BC or an OC.

A port that neither receives nor sends synchronization messages is a passive port.

Clock source type

The following clock sources are available for a clock node:

· Local clock source—38.88 MHz clock signals generated by a crystal oscillator inside the clock monitoring module. You cannot configure a time class or accuracy for a local clock source.

· ToD clock source—Clock signals generated by a ToD clock device. The signals are received and sent by a ToD port on the device. The device transmits the received ToD clock signals to the clock monitoring module which then sends them to all interface modules. You can configure a time class and accuracy for a ToD clock source.

The clock node decides which clock source to use based on a specific algorithm.

Grandmaster clock

As shown in Figure 1, the grandmaster clock (GM) is the ultimate source of time for clock synchronization in a PTP domain. It is elected automatically by the clock nodes in the PTP domain. The clock nodes exchange PTP messages and elect the GM by comparing the clock priority, time class, and time accuracy carried in the PTP messages.

You can also specify a GM manually.

Grandmaster clock selection and master-member/subordinate relationship establishment

A GM can be manually specified. It can also be elected through the BMC algorithm as follows:

1. The clock nodes in a PTP domain exchange announce messages and elect a GM by using the following rules in descending order:

a. Clock node with higher priority 1.

b. Clock node with higher time class.

c. Clock node with higher time accuracy.

d. Clock node with higher priority 2.

e. Clock node with a smaller port ID (containing clock number and port number).

The master nodes, member nodes, master ports, and subordinate ports are determined during the process. Then a spanning tree with the GM as the root is generated for the PTP domain.

2. The master node periodically sends announce messages to the member nodes. If the member nodes do not receive announce messages from the master node, they determine that the master node is invalid, and they start to elect another GM.

Optimal domain selection

If only one PTP instance is configured on the device, this PTP instance is the optimal instance of the device. If multiple PTP instances are configured on the device, the optimal PTP instance (domain) is selected by using the following rules in descending order:

1. Activated instance (with a domain configured).

2. Instance on which the device is an OC or BC clock node.

3. Instance on which the clock source has a higher priority 1 value

4. Instance on which the clock source has a higher time class.

5. Instance on which the clock source has higher time accuracy.

6. Instance on which the clock source has a lower offset from the GM.

7. Instance on which the clock source has a higher priority 2 value.

8. Instance associated with a PTP domain that has a smaller domain ID.

The PTP instance on which the ptp active force-state command is configured has the lowest priority.

Synchronization mechanism

After master-member relationships are established between the clock nodes, the master and member clock nodes exchange PTP messages and record the message transmit and receive time. Based on the timestamps, each member clock calculates the path delay and time offset between them and the master clock and adjusts their time accordingly for time synchronization with the master clock.

PTP defines two path delay measurement mechanisms: Request_Response_ and Peer Delay, both of which are based on network symmetry.

Request_Response

The Request_Response mechanism measures the average path delay between the master and member clock nodes by using the PTP messages as shown in Figure 2. A TC between master and member clock nodes does not calculate the path delay. It forwards PTP messages and carries the Sync message residence time on it to the downstream clock node.

This mechanism can be implemented in one of the following two modes:

· Two-step mode—t1 is carried in the Follow_Up message as shown in Figure 2.

· Single-step mode—t1 is carried in the Sync message, and no Follow_Up message is sent.

Figure 2 shows the Request_Response mechanism in two-step mode.

1. The master clock sends a Sync message to the member clock, and records the sending time t1. Upon receiving the message, the member clock records the receiving time t2.

2. After sending the Sync message, the master clock immediately sends a Follow_Up message that carries time t1.

3. The member clock sends a Delay_Req message to the master clock, and records the sending time t3. Upon receiving the message, the master clock records the receiving time t4.

4. The master clock returns a Delay_Resp message that carries time t4.

After this procedure, the member clock obtains all the four timestamps and can make the following calculations:

· Round-trip delay between the master and member clocks: (t2 – t1) + (t4 – t3)

· One-way delay between the master and member clocks: [(t2 – t1) + (t4 – t3)] / 2

· Offset between the member and master clocks: (t2 – t1) – [(t2 – t1) + (t4 – t3)] / 2 or [(t2 – t1) – (t4 – t3)] / 2

Figure 2 Request_Response mechanism (two-step node)

Peer Delay

The Peer Delay mechanism measures the average path delay between two clock nodes. The two clock nodes (BC, TC, or OC) implementing this mechanism send Pdelay messages to each other, and calculate the one-way link delay between them independently. The message interaction process and delay calculation method are identical on the two nodes. TCs that exist between master and member clock nodes divide the synchronization path into multiple links and participate in delay calculation. The link delays and Sync message residence time on the TCs are carried to downstream nodes.

This mechanism can be implemented in one of the following two modes:

· Two-step mode

As shown in Figure 3, Pdelay messages include Pdelay_Req, Pdelay_Resp, and Pdelay_Resp_Follow_Up messages. t2 is carried in the Pdelay_Resp message, and t3 is carried in the Pdelay_Resp_Follow_Up message.

· Single-step mode:

Pdelay messages include Pdelay_Req and Pdelay_Resp messages. t3 – t2 is carried in the Pdelay_Resp, and no Pdelay_Resp_Follow_Up message is sent.

Figure 3 uses Clock node B as an example to describe the Peer Delay mechanism.

1. Clock node B sends a Pdelay_Req message to Clock node A, and records the sending time t1. Upon receiving the message, Clock node A records the receiving time t2.

2. Clock node A sends a Pdelay_Req message that carries t2 to Clock node B, and records the sending time t3. Upon receiving the message, Clock node B records the receiving time t4.

3. Clock node A immediately sends a Pdelay_Resp_Follow_Up message carrying t3 to Clock node B after sending the Pdelay_Req message.

After this procedure, Clock node B obtains all the four timestamps and can make the following calculations:

· Round-trip delay between Clock node A and Clock node B: (t2 – t1) + (t4 – t3)

· One-way delay between Clock node A and Clock node B: [ (t2 – t1) + (t4 – t3)] / 2 = [ (t4 – t1) – (t3 – t2) ] / 2

· Time offset between the member clock and the master clock: Sync message receiving time on the member clock – Sync message sending time on the master clock – Total one-way delays on all links – Total Sync message residence time on all TCs.

Figure 3 Peer Delay mechanism (two-step mode)

Protocols and standards

· IEEE Std 1588-2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, 2008

· IEEE 802.1AS, Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area Networks

· SMPTE ST 2059-2, SMPTE Profile for Use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications

· AES67-2015, AES Standard for Audio Applications of Networks-High-Performance Streaming Audio-Over-IP Interoperability, 2015

Configuration restrictions and guidelines

Before configuring PTP, determine the PTP profile and define the scope of the PTP domain and the clock node role of each device in the domain.

In a PTP domain that runs the IEEE 1588 version 2 or IEEE 802.1AS PTP profile, specify the BC or OC clock node type for the devices in the domain as a best practice. A TC clock node is mainly used for forwarding PTP messages. When receiving a PTP message, a TC multicasts the message from all its PTP interfaces except the inbound interface of the PTP message. To deploy a TC in the domain, plan the TC location and number and location of PTP interfaces on the TC manually to prevent PTP forwarding loops.

For correct time synchronization, make sure the system time is not earlier than year 2035. To view the current system time, execute the display clock command.

Only the default MDC supports PTP. Non-default MDCs do not support PTP or PTP commands. For more information about MDCs, see Virtual Technologies Configuration Guide.

Only the following MPUs and interface modules support PTP:

· LSUM1MPUS10XEB0, LSUM1SUPXD0, LSUM1MPUS06XEC0, LSUM1MPUS10XE0, LSUM1MPUS06XEB0, LSUM1MPUS10XEA0, and LSUM1SUPXES0 MPUs.

¡ For an LSUM1SUPXES0 MPU to run PTP, you must install it on an S10508X, S10508X-V, or S10516X switch and use it together with LSUM2GP40TS8FD0 interface modules. If SH interface modules are used simultaneously, you can use only the LSUM2GP40TS8FD0 interface module to connect and synchronize time with the upstream node. The SH interface modules can be used only to synchronize the downstream nodes.

¡ Only the LSUM1SUPXES0 MPU supports ToD clocks.

¡ To run PTP on an LSUM1SUPXD0 or LSUM1MPUS10XE0 MPU, upgrade the CPLD of the module first if the CPLD version does not support PTP. For the CPLD upgrade method, contact technical support.

¡ The network ports on an LSUM1MPUS10XEB0 MPU support PTP.

· SH interface modules and FD interface modules LSUM2GP40TS8FD0, LSUM1GP48FD0, LSUM1GT48FD0, LSUM1TGS16FD0, LSUM1TGT24FD0, LSUM1GP40TS8FD0, LSUM1CGS2FE0, and LSUM1TGS24FD0.

¡ To run PTP on an LSUM1CGS20XSH0 or LSUM1CGS32XSH0 interface module, upgrade the CPLD of the module first if the CPLD version does not support PTP. For the CPLD upgrade method, contact technical support.

¡ For clock synchronization, do not connect the device to the upstream PTP device if the device uses the LSUM1GP40TS8FD0 interface module as its local clock source.

¡ PTP time synchronization between interface modules in a chassis depends on their types and their CPLD versions, as shown in Table 1.

You can use the display version command to identify the CPLD version of the interface modules. If the CPLD version of an interface module does not meet the requirement, upgrade the CPLD. If the CPLD version of an LSUM1CGS32XSH0 interface module is 001, upgrade the CPLD to 002 or later. For the CPLD upgrade method, contact technical support.

Table 1 Requirements for PTP synchronization between interface modules

Requirements for PTP synchronization between interface modules
Interface module A		Interface module B
· LSUM1TGS48RSH0 · LSUM1CGS8SH0 · LSUM1TGS48SH0 · LSUM2TGS48SH0 · LSUM1YGS24CSSH0 · LSUM1CGS8QSSH0 · LSUM1YGS48XSH0	CPLD 001	· LSUM1TGS48RSH0 · LSUM1CGS8SH0 · LSUM1TGS48SH0 · LSUM2TGS48SH0 · LSUM1YGS24CSSH0 · LSUM1CGS8QSSH0 · LSUM1YGS48XSH0	CPLD 001
	CPLD 001	LSUM1CGS20XSH0	CPLD 002
	CPLD 002 or later	· LSUM1TGS48RSH0 · LSUM1CGS8SH0 · LSUM1TGS48SH0 · LSUM2TGS48SH0 · LSUM1YGS24CSSH0 · LSUM1CGS8QSSH0 · LSUM1YGS48XSH0	CPLD 002 or later
		LSUM1CGS20XSH0	CPLD 003 or later
		LSUM2GP40TS8FD0	N/A
		LSUM1CGS32XSH0	CPLD 002 or later
LSUM1CGS20XSH0	CPLD 002	LSUM1CGS20XSH0	CPLD 002
	CPLD 002	· LSUM1TGS48RSH0 · LSUM1CGS8SH0 · LSUM1TGS48SH0 · LSUM2TGS48SH0 · LSUM1YGS24CSSH0 · LSUM1CGS8QSSH0 · LSUM1YGS48XSH0	CPLD 001
	CPLD 003 or later	LSUM1CGS20XSH0	CPLD 003 or later
		· LSUM1TGS48RSH0 · LSUM1CGS8SH0 · LSUM1TGS48SH0 · LSUM2TGS48SH0 · LSUM1YGS24CSSH0 · LSUM1CGS8QSSH0 · LSUM1YGS48XSH0	CPLD 002 or later
		LSUM2GP40TS8FD0	N/A
		LSUM1CGS32XSH0	CPLD 002 or later
LSUM1CGS32XSH0	CPLD 002 or later	LSUM1CGS32XSH0	CPLD 002 or later
		· LSUM1TGS48RSH0 · LSUM1CGS8SH0 · LSUM1TGS48SH0 · LSUM2TGS48SH0 · LSUM1YGS24CSSH0 · LSUM1CGS8QSSH0 · LSUM1YGS48XSH0	CPLD 002 or later
		LSUM1CGS20XSH0	CPLD 003 or later
		LSUM2GP40TS8FD0	N/A

PTP tasks at a glance

Configuring PTP (IEEE 1588 version 2)

1. Specifying PTP for obtaining the time

2. (Optional.) Enabling unicast forwarding of PTP messages

3. (Optional.) Creating a PTP instance

4. Specifying a PTP profile

Specify the IEEE 1588 version 2 PTP profile.

5. Configuring clock nodes

¡ Specifying a clock node type

¡ (Optional.) Configuring an OC to operate only as a member clock

6. Specifying a PTP domain

7. Enable PTP.

For an interface to run PTP, run PTP globally and on the interface.

¡ Enabling PTP globally

¡ Enabling PTP on a port

8. Configuring PTP ports

¡ (Optional.) Configuring the role of a PTP port

¡ Configuring the mode for carrying timestamps

¡ Specifying a delay measurement mechanism for a BC or an OC

¡ Configuring one of the ports on a TC+OC clock as an OC-type port

¡ Enabling unicast negotiation on PTP ports

9. (Optional.) Configuring PTP message transmission and receipt

¡ Setting the interval for sending announce messages and the timeout multiplier for receiving announce messages

¡ Setting the interval for sending Pdelay_Req messages

¡ Setting the interval for sending Sync messages

¡ Setting the minimum interval for sending Delay_Req messages

¡ Setting the interval for sending Delay-Resp messages

10. (Optional.) Configuring parameters for PTP messages

¡ Specifying the protocol for encapsulating PTP messages as UDP

¡ Configuring a source IP address for multicast PTP message transmission over UDP

¡ Configuring a destination IP address for unicast PTP message transmission over UDP

¡ Configuring the MAC address for non-Pdelay messages

¡ Setting a DSCP value for PTP messages transmitted over UDP

¡ Specifying a VLAN tag for PTP messages

¡ Disabling PTP path tracing

11. (Optional.) Adjusting and correcting clock synchronization

¡ Setting the delay correction value

¡ Setting the cumulative offset between the UTC and TAI

¡ Setting the correction date of the UTC

¡ Configuring ToD input or output

¡ Configuring the PTP offset threshold and PTP synchronization suppressions

12. (Optional.) Setting ToD clock parameters

13. (Optional.) Configuring a priority for a clock

14. (Optional.) Configuring PTP logging

15. (Optional.) Enabling SNMP notification for the PTP module

Configuring PTP (IEEE 802.1AS)

1. Specifying PTP for obtaining the time

2. (Optional.) Creating a PTP instance

3. Specifying a PTP profile

Specify the IEEE 802.1AS PTP profile.

4. Configuring clock nodes

¡ Specifying a clock node type

¡ (Optional.) Configuring an OC to operate only as a member clock

5. Specifying a PTP domain

6. Enable PTP.

For an interface to run PTP, run PTP globally and on the interface.

¡ Enabling PTP globally

¡ Enabling PTP on a port

7. Configuring PTP ports

¡ (Optional.) Configuring the role of a PTP port

¡ Configuring one of the ports on a TC+OC clock as an OC-type port

8. (Optional.) Configuring PTP message transmission and receipt

¡ Setting the interval for sending announce messages and the timeout multiplier for receiving announce messages

¡ Setting the interval for sending Pdelay_Req messages

¡ Setting the interval for sending Sync messages

9. (Optional.) Specifying a VLAN tag for PTP messages

10. (Optional.) Disabling PTP path tracing

11. (Optional.) Adjusting and correcting clock synchronization

¡ Setting the delay correction value

¡ Setting the cumulative offset between the UTC and TAI

¡ Setting the correction date of the UTC

¡ Configuring ToD input or output

¡ Configuring the PTP offset threshold and PTP synchronization suppressions

12. (Optional.) Setting ToD clock parameters

13. (Optional.) Configuring a priority for a clock

14. (Optional.) Configuring PTP logging

15. (Optional.) Enabling SNMP notification for the PTP module

Configuring PTP (SMPTE ST 2059-2)

1. Specifying PTP for obtaining the time

2. (Optional.) Enabling unicast forwarding of PTP messages

3. (Optional.) Creating a PTP instance

4. Specifying a PTP profile

Specify the SMPTE ST 2059-2 PTP profile.

5. Configuring clock nodes

¡ Specifying a clock node type

¡ (Optional.) Configuring an OC to operate only as a member clock

6. Specifying a PTP domain

7. Enable PTP.

For an interface to run PTP, run PTP globally and on the interface.

¡ Enabling PTP globally

¡ Enabling PTP on a port

8. Configuring PTP ports

¡ (Optional.) Configuring the role of a PTP port

¡ Configuring the mode for carrying timestamps

¡ Specifying a delay measurement mechanism for a BC or an OC

9. (Optional.) Configuring PTP message transmission and receipt

¡ Setting the interval for sending announce messages and the timeout multiplier for receiving announce messages

¡ Setting the interval for sending Pdelay_Req messages

¡ Setting the interval for sending Sync messages

¡ Setting the minimum interval for sending Delay_Req messages

10. (Optional.) Configuring parameters for PTP messages

¡ Configuring a source IP address for multicast PTP message transmission over UDP

¡ Configuring a destination IP address for unicast PTP message transmission over UDP

¡ Setting a DSCP value for PTP messages transmitted over UDP

¡ Specifying a VLAN tag for PTP messages

¡ Disabling PTP path tracing

11. (Optional.) Adjusting and correcting clock synchronization

¡ Setting the delay correction value

¡ Setting the cumulative offset between the UTC and TAI

¡ Setting the correction date of the UTC

¡ Configuring ToD input or output

¡ Configuring the PTP offset threshold and PTP synchronization suppressions

12. (Optional.) Setting ToD clock parameters

13. (Optional.) Configuring a priority for a clock

14. (Optional.) Configuring PTP logging

15. (Optional.) Enabling SNMP notification for the PTP module

Configuring PTP (AES67-2015)

1. Specifying PTP for obtaining the time

2. (Optional.) Enabling unicast forwarding of PTP messages

3. (Optional.) Creating a PTP instance

4. Specifying a PTP profile

Specify the AES67-2015 PTP profile.

5. Configuring clock nodes

¡ Specifying a clock node type

¡ (Optional.) Configuring an OC to operate only as a member clock

6. Specifying a PTP domain

7. Enable PTP.

For an interface to run PTP, run PTP globally and on the interface.

¡ Enabling PTP globally

¡ Enabling PTP on a port

8. Configuring PTP ports

¡ (Optional.) Configuring the role of a PTP port

¡ Configuring the mode for carrying timestamps

¡ Specifying a delay measurement mechanism for a BC or an OC

¡ Configuring one of the ports on a TC+OC clock as an OC-type port

9. (Optional.) Configuring PTP message transmission and receipt

¡ Setting the interval for sending announce messages and the timeout multiplier for receiving announce messages

¡ Setting the interval for sending Pdelay_Req messages

¡ Setting the interval for sending Sync messages

¡ Setting the minimum interval for sending Delay_Req messages

10. (Optional.) Configuring parameters for PTP messages

¡ Configuring a source IP address for multicast PTP message transmission over UDP

¡ Configuring a destination IP address for unicast PTP message transmission over UDP

¡ Setting a DSCP value for PTP messages transmitted over UDP

¡ Specifying a VLAN tag for PTP messages

¡ Disabling PTP path tracing

11. (Optional.) Adjusting and correcting clock synchronization

¡ Setting the delay correction value

¡ Setting the cumulative offset between the UTC and TAI

¡ Setting the correction date of the UTC

¡ Configuring ToD input or output

¡ Configuring the PTP offset threshold and PTP synchronization suppressions

12. (Optional.) Setting ToD clock parameters

13. (Optional.) Configuring a priority for a clock

14. (Optional.) Configuring PTP logging

15. (Optional.) Enabling SNMP notification for the PTP module

Specifying PTP for obtaining the time

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Specify PTP for obtaining the time.	clock protocol ptp mdc 1	By default, the device uses NTP to synchronize the system time. For more information about the clock protocol command, see device management commands in Fundamentals Command Reference.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Specify PTP for obtaining the time.

clock protocol ptp mdc 1

By default, the device uses NTP to synchronize the system time.

For more information about the clock protocol command, see device management commands in Fundamentals Command Reference.

Enabling unicast forwarding of PTP messages

About this task

To improve time synchronization accuracy, enable unicast forwarding of PTP messages for all E2ETC clock nodes on the time synchronization path when PTP messages are transmitted in unicast mode in a PTP domain.

If unicast forwarding of PTP messages is enabled for an E2ETC, the E2ETC will unicast PTP messages.

If unicast forwarding of PTP messages is disabled for an E2ETC, the E2ETC will forward PTP messages from all PTP interfaces on it.

Restrictions and guidelines

Only an E2ETC clock node supports this task. Do not configure this task for a non-E2ETC clock node.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable unicast forwarding of PTP messages for an E2ETC clock node.	ptp unicast-forward enable	By default, unicast forwarding of PTP messages is disabled for an E2ETC clock node.

Creating a PTP instance

About this task

A PTP instance is uniquely identified by its ID on a device. For easy identification and management, you can also set a name for a PTP instance.

Restrictions and guidelines

Do not set the same name for different PTP instances.

If you create PTP instances with the same ID but different names, the most recent configuration takes effect.

The default PTP instance with an ID of 0 has been created by default. You cannot delete the default PTP instance. PTP settings configured in system view take effect only on PTP instance 0. To configure settings for a PTP instance other than PTP instance 0, enter PTP instance view.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a PTP instance.	ptp instance ptp-instance-id [ name ptp-instance-name ]	By default, PTP instance numbered 0 and named default-instance exists.

Specifying a PTP profile

Restrictions and guidelines

You must specify a PTP profile before configuring PTP settings. Changing the PTP profile clears all settings under the profile.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Specify a PTP profile.	ptp profile { 1588v2 \| 8021as \| aes67-2015 \| st2059-2 }	By default, no PTP profile is configured, and PTP is not running on the device.

Configuring clock nodes

Specifying a clock node type

Restrictions and guidelines

Before you specify a clock node type, specify a PTP profile.

If the ptp unicast-forward enable command has been configured, you can specify only the E2ETC clock node type for the device.

Changing or removing the clock node type restores the default settings of the PTP profile.

If the device belongs to multiple PTP domains, you can specify the BC or OC clock node type for the device in only one domain. An E2ETC+OC or P2PTC+OC clock node is identified as an OC clock node if the ptp port-mode oc command has been configured on it to specify the OC port type. In other domains, you must specify the TC clock node type for the device. TC clock nodes include also the E2ETC and P2PTC clock nodes as well as the E2ETC+OC and P2PTC+OC clock nodes not configured with the ptp port-mode oc command that specifies the OC port type.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Specify a clock node type for the device.	· IEEE 1588v2 profile: ptp mode { bc \| e2etc \| e2etc-oc \| oc \| p2ptc \| p2ptc-oc } · IEEE 802.1AS profile: ptp mode { bc \| oc \| p2ptc \| p2ptc-oc } · AES67-2015 and SMPTE ST 2059-2 profiles: ptp mode { bc \| e2etc \| oc \| p2ptc }	By default, no clock node type is specified.

Configuring an OC to operate only as a member clock

About configuring an OC to operate only as a member clock

An OC can operate either as a master clock to send synchronization messages or as a member clock to receive synchronization messages. This task allows you to configure an OC to operate only as a member clock.

If an OC is operating only as a member clock, you can use the ptp force-state command to configure its PTP port as a master port or passive port.

Restrictions and guidelines

This task is applicable only to OCs.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Configure the OC to operate only as a member clock.	ptp slave-only	By default, an OC operates as a master or member clock. This command is mutually exclusive with the ptp unicast-negotiate command.

Specifying a PTP domain

About PTP domains

Within a PTP domain, all devices follow the same rules to communicate with each other. Devices in different PTP domains cannot exchange PTP messages.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Specify a PTP domain for the device.	ptp domain value	By default, the device does not belong to any domain. Do not configure the same domain for different PTP instances.

Enabling PTP globally

Restrictions and guidelines

For an interface to run PTP, you must enable PTP globally and on the interface.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable PTP globally.	ptp global enable	By default, PTP is enabled globally.

Enabling PTP on a port

About enabling PTP on a port

A port enabled with PTP becomes a PTP port.

Restrictions and guidelines

You can enable PTP on only one port on an OC.

As a best practice, enable PTP on a port after PTP settings are configured. In an IRF fabric, PTP is enabled automatically on IRF physical interfaces after PTP settings are configured.

To enable PTP on a Layer 3 Ethernet interface that has been assigned to a VPN instance, you must specify this VPN instance in the ptp source ip-address vpn-instance vpn-instance-name command to transmit PTP messages in multicast mode over IPv4 UDP.

For a PTP-enabled interface to run PTP correctly, do not add that interface to an aggregation group.

You cannot enable PTP on an aggregate member interface.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Enable PTP on the port.	ptp enable	By default, PTP is disabled on a port.

Configuring PTP ports

Configuring the role of a PTP port

About configuring the role of a PTP port

You can configure the master, passive, or slave role for a PTP port.

For an OC that operates in slave-only mode, you can perform this task to change its PTP port role to master or slave.

Restrictions and guidelines

By default, the PTP port roles are automatically negotiated based on the BMC algorithm. If you use this task to change the role of one PTP port, all the other PTP ports in the PTP domain stop working. For these PTP ports to function, you must specify a role for each of them by using this task. As a best practice, enable automatic negotiation of PTP port roles based on the BMC algorithm.

You can configure only one subordinate port on the device.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Configure the role of the PTP port.	ptp force-state { master \| passive \| slave }	By default, the PTP port role is automatically calculated through BMC. This command is mutually exclusive with the ptp unicast-negotiate command.
5. Return to system view.	quit	N/A
6. (Optional.) Enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
7. Activate the port role configuration.	ptp active force-state	By default, the port role configuration is not activated.

Configuring the mode for carrying timestamps

About the mode for carrying timestamps

Timestamps can be carried in either of the following modes:

· Single-step mode—The following messages contain the message sending time:

¡ Sync message in the Request_Response and Peer Delay mechanisms.

¡ Pdelay_Resp message in the Peer Delay mechanism.

· Two-step mode—All messages contain the message sending time, except for the following messages:

¡ Sync message in the Request_Response and Peer Delay mechanisms.

¡ Pdelay_Resp message in the Peer Delay mechanism.

Restrictions and guidelines

The IEEE 802.1AS PTP profile supports only the two-step mode.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Configure the mode for carrying timestamps.	ptp clock-step { one-step \| two-step }	By default, the two-step mode is used for carrying timestamps.

Specifying a delay measurement mechanism for a BC or an OC

About the delay measurement mechanism

PTP defines two transmission delay measurement mechanisms: Request_Response and Peer Delay. For correct communication, ports on the same link must share the same delay measurement mechanism.

Restrictions and guidelines

Follow these restrictions and guidelines when you configure this task:

· IEEE 1588 version 2, SMPTE ST 2059-2, or AES67-2015 PTP profile:

¡ You can configure this task only for a BC or OC clock node.

¡ The E2ETC, E2ETC+OC, P2PTC, and P2PTC+OC clock nodes do not support this task. The E2ETC and E2ETC+OC clock nodes support both the request-response and peer delay measurement mechanisms. The P2PTC clock node supports only the peer delay measurement mechanism.

· IEEE 802.1AS PTP profile: Supports only the peer delay measurement mechanism and does not support this task.

· The ptp delay-mechanism p2p command and ptp unicast-negotiate command are mutually exclusive.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Specify a delay measurement mechanism for a BC or an OC.	ptp delay-mechanism { e2e \| p2p }	When the PTP profile is IEEE 1588 version 2, AES67-2015, or SMPTE ST 2059-2, the request-response delay measurement mechanism applies. When the PTP profile is IEEE 802.1AS, the peer delay measurement mechanism applies.

Configuring one of the ports on a TC+OC clock as an OC-type port

About configuring one of the ports on a TC+OC clock as an OC-type port

All ports on a TC+OC (E2ETC+OC or P2PTC+OC) are TC-type ports by default. This feature allows you to configure one of the ports on a TC+OC clock as an OC-type port.

Restrictions and guidelines

This task is applicable only to E2ETC+OCs and P2PTC+OCs.

This task is not available for the SMPTE ST 2059-2 or AES67-2015 PTP profile.

For time synchronization accuracy, the OC-type port on an E2ETC+OC or P2PTC+OC must be specified as the master port.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Specify the OC port type.	ptp port-mode oc	By default, the port type for all ports on a TC+OC is TC.

Enabling unicast negotiation on PTP ports

About this task

On a network where the IEEE 1588 version 2 PTP profile runs, you can use this task to establish master-subordinate relations between PTP ports by specifying the request-ports and grant-ports. A grant-port grants and provides PTP service. A request-port requests and receives PTP service. Typically, a grant-port is in master state. A request-port is in slave state when selected as the port for time synchronization and in listening state when not selected.

A request-port initiates a PTP link connection request to a specific grant-port. Then they negotiate PTP parameters and exchange PTP messages to synchronize the client time to the server. Plan the network in advance and specify the ports on the member (client) clock nodes as request-ports and the ports on the master (server) clock nodes as grant-ports.

Restrictions and guidelines

Only the IEEE 1588 version 2 profile supports this task.

Follow these restrictions and guidelines to configure unicast negotiation under the IEEE 1588 version 2 PTP profile:

· The ptp transport-protocol udp command must be configured for unicast negotiation to take effect.

· The E2ETC, P2PTC, and P2PTC-OC clock nodes do not support unicast negotiation

· The ptp unicast-negotiate command is mutually exclusive with the ptp slave-only, ptp force-state, and ptp delay-mechanism p2p commands.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter PTP instance view.	ptp instance ptp-instance-id	To configure parameters for PTP instance 0, skip this step.
4. Enable unicast negotiation and specify the port as a grant-port or request port.	ptp unicast-negotiate { grant-port \| request-port }	By default, unicast negotiation is disabled on a PTP port.

Configuring PTP message transmission and receipt

Setting the interval for sending announce messages and the timeout multiplier for receiving announce messages

About this task

A master node periodically sends announce messages at the specified interval. If a member node does not receive any announce message from the master node after the timeout expires, it determines that the master node is invalid. The timeout = timeout multiplier × interval at which the master node sends announce messages.

The interval at which the master node sends announce messages depends on whether unicast negotiation is enabled.

· If unicast negotiation is not enabled, the master node uses the value configured by using the ptp announce-interval command on its interface as the interval.

· If unicast negotiation is enabled, you must configure the interval on the request-port of the client. The request-port uses the configured interval to negotiate with the grant-port on the server for the interval at which the grant-port sends announce messages to the client. If the negotiation succeeds, the grant-port sends announce messages at the configured interval to the client. If the negotiation fails, the grant-port does not send announce messages to the client.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Set the interval for sending announce messages.	ptp announce-interval interval	The default settings vary by PTP profile. · IEEE 1588 version 2 or AES67-2015—The interval argument value is 1 and the interval for sending announce messages is 2 (21) seconds. · IEEE 802.1AS—The interval argument value is 0 and the interval for sending announce messages is 1 (20) second. · SMPTE ST 2059-2—The interval argument value is –2 and the interval for sending announce messages is 1/4 (2-2) seconds.
5. Set the number of intervals before a timeout occurs.	ptp announce-timeout multiple-value	By default, a timeout occurs when three intervals are reached.

Setting the interval for sending Pdelay_Req messages

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Set the interval for sending Pdelay_Req messages.	ptp pdelay-req-interval interval	By default, the interval argument value is 0 and the interval for sending peer delay request messages is 1 (20) second. For the SMPTE ST 2059-2 or AES67-2015 PTP profile, set the interval argument to a value in the range of ptp syn-interval interval to ptp syn-interval interval plus 5 as a best practice.

Setting the interval for sending Sync messages

About this task

The master node sends Sync messages to the member nodes periodically. The interval at which the master node sends Sync messages to member nodes depends on whether unicast negotiation is enabled.

· If unicast negotiation is not enabled, use this task to configure the interval on the master node.

· If unicast negotiation is enabled, you must configure the interval on the request-port of the client. The request-port uses the configured interval to negotiate with the grant-port on the server for the interval at which the grant-port sends Sync messages to the client. If the negotiation succeeds, the grant-port sends Sync messages at the configured interval to the client. If the negotiation fails, the grant-port does not send Sync messages to the client.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Set the interval for sending Sync messages.	ptp syn-interval interval	The default settings vary by PTP profile. · IEEE 1588 version 2—The interval argument value is 0 and the interval for sending Sync messages is 1 (20) second. As a best practice, set the interval to –2 or –4. If you set the interval to –6, the clock synchronization accuracy might be reduced. · IEEE 802.1AS, AES67-2015, or SMPTE ST 2059-2—The interval argument value is –3 and the interval for sending Sync messages is 1/8 (2-3) seconds.

Setting the minimum interval for sending Delay_Req messages

About the minimum interval for sending Delay_Req messages

When receiving a Sync or Follow_Up message, an interface can send Delay_Req messages only when the minimum interval is reached.

Restrictions and guidelines

This task is not available for the IEEE 802.1AS PTP profile.

In PTP multicast transport mode, this command takes effect only when configured on the master clock. The master clock sends the value to a member clock through PTP messages to control the interval for the member clock to send Delay_Req messages. To view the interval, execute the display ptp interface command on the member clock.

In PTP unicast transport mode, this command takes effect when configured on member clocks. It does not take effect when configured on the master clock.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Set the minimum interval for sending Delay_Req messages.	ptp min-delayreq-interval interval	The interval argument value is 0 and the minimum interval for sending delay request messages is 1 (20) second. For the SMPTE ST 2059-2 PTP profile, set the interval argument to a value in the range of ptp syn-interval interval to ptp syn-interval interval plus 5 as a best practice.

Setting the interval for sending Delay-Resp messages

About this task

This task, configured on a unicast negotiation request-port, specifies the interval at which the grant-port sends Delay_resp messages to the request-port. After receiving a Delay_req message from a request port, the grant-port responds by sending a Delay_resp message and starts a timer defined by this command. The grant-port will not send another Delay_resp message until it receives a Delay_req message after the timer expires.

Restrictions and guidelines

This task is available only for the IEEE 1588 version 2 PTP profile and is configured on unicast negotiation request-ports.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter PTP instance view.	ptp instance ptp-instance-id	To configure parameters for PTP instance 0, skip this step.
4. Set the interval for sending Delay_resp messages.	ptp delay-resp-interval interval	By default, the value of the interval argument is 0 and the minimum interval for sending Delay_resp messages is 1 (20) second.

Configuring parameters for PTP messages

Specifying the protocol for encapsulating PTP messages as UDP

About PTP message encapsulation protocols

PTP messages can be encapsulated in IEEE 802.3/Ethernet packets or UDP packets.

Restrictions and guidelines

The IEEE 802.1AS PTP profile can transport PTP messages only over IEEE 802.3/Ethernet and does not support this task.

The SMPTE ST 2059-2 or AES67-2015 PTP profile can transport PTP messages only over UDP and does not support this task.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Configure the protocol for encapsulating PTP messages as UDP.	ptp transport-protocol udp	By default, PTP messages are encapsulated in IEEE 802.3/Ethernet packets.

Configuring a source IP address for multicast PTP message transmission over UDP

About configuring a source IP address for multicast PTP message transmission over UDP

To transport multicast PTP messages over UDP, you must configure a source IP address for the messages.

Restrictions and guidelines

If both a source IP address for multicast PTP message transmission over UDP and a destination address for unicast PTP message transmission over UDP are configured, the system unicasts the messages.

This task is not available for the IEEE 802.1AS PTP profile.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Configure a source IP address for multicast PTP message transmission over UDP.	ptp source ip-address [ vpn-instance vpn-instance-name ]	By default, no source IP address is configured for multicast PTP message transmission over UDP. If the PTP interface has been assigned to a VPN instance by using the ip binding command, use the VPN instance in this command.

Configuring a destination IP address for unicast PTP message transmission over UDP

About configuring a destination IP address for unicast PTP message transmission over UDP

To transport unicast PTP messages over UDP, you must configure a destination IP address for the messages.

Restrictions and guidelines

If both a source IP address for multicast PTP message transmission over UDP and a destination address for unicast PTP message transmission over UDP are configured, the system unicasts the messages.

This task is not available for the IEEE 802.1AS PTP profile.

Prerequisites

Configure an IP address for the current interface, and make sure the interface and the peer PTP interface can reach each other.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Configure a destination IP address for unicast PTP message transmission over UDP.	ptp unicast-destination ip-address	By default, no destination IP address is configured for unicast PTP message transmission over UDP.

Configuring the MAC address for non-Pdelay messages

About the MAC address for non-Pdelay messages

Pdelay messages include Pdelay_Req, Pdelay_Resp, and Pdelay_Resp_Follow_Up messages. The destination MAC address of Pdelay messages is 0180-C200-000E by default, which cannot be modified. The destination MAC address of non-Pdelay messages is either 0180-C200-000E or 011B-1900-0000.

Restrictions and guidelines

This feature takes effect only when PTP messages are encapsulated in IEEE 802.3/Ethernet packets.

This task is not available for the IEEE 802.1AS, SMPTE ST 2059-2, or AES67-2015 PTP profile.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Configure the destination MAC address for non-Pdelay messages.	ptp destination-mac mac-address	The default destination MAC address is 011B-1900-0000.

Setting a DSCP value for PTP messages transmitted over UDP

About DSCP values for PTP messages

The DSCP value determines the sending precedence of PTP messages transmitted over UDP.

Restrictions and guidelines

This task is not available for the IEEE 802.1AS PTP profile.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Set a DSCP value for PTP messages transmitted over IPv4 UDP.	ptp dscp dscp	By default, the DSCP value for PTP messages transmitted over IPv4 UDP is 56.

Specifying a VLAN tag for PTP messages

About specifying a VLAN tag for PTP messages

Perform this task to configure the VLAN ID and the 802.1p precedence in the VLAN tag carried by PTP messages.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Specify a VLAN tag for PTP messages.	ptp vlan vlan-id [ dot1p dot1p-value ]	By default, PTP messages do not have a VLAN tag.

Disabling PTP path tracing

About this task

PTP path tracing traces the clock nodes that the clock signals traverse from the GM to the device. The system can obtain complete path tracing information only when all clock nodes on the path are enabled with PTP path tracing. If a device on the path does not support PTP path tracing, disable this feature to prevent PTP intercommunication issues.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Disable PTP path tracing.	ptp path-trace disable	By default, PTP path tracing is enabled.

Adjusting and correcting clock synchronization

Setting the delay correction value

About setting the delay correction value

PTP performs time synchronization based on the assumption that the delays in sending and receiving messages are the same. However, this is not practical. If you know the offset between the delays in sending and receiving messages, you can set the delay correction value for more accurate time synchronization.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
3. (Optional.) Assign the interface to a PTP instance and enter interface PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
4. Set a delay correction value.	ptp asymmetry-correction { minus \| plus } value	The default is 0 nanoseconds. Delay correction is not performed.

Setting the cumulative offset between the UTC and TAI

About setting the cumulative offset between the UTC and TAI

There is an offset between Coordinated Universal Time (UTC) and TAI (International Atomic Time, in English). This task allows you to adjust the offset between the UTC and TAI on the device.

Restrictions and guidelines

This setting takes effect only when configured on the master clock node, and the local clock of the master clock node is the GM.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Set the cumulative offset between the UTC and TAI.	ptp utc offset utc-offset	The default is 0 seconds.

Setting the correction date of the UTC

About setting the correction date of the UTC

This task allows you to adjust the UTC at the last minute (23:59) of the specified date.

Restrictions and guidelines

If you configure the setting multiple times, the most recent configuration takes effect.

This setting takes effect only when configured on the master clock node, and the local clock of the master clock node is the GM.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the correction date of the UTC.	ptp utc { leap59-date \| leap61-date } date	By default, the correction date of the UTC is not configured.

Configuring ToD input or output

About configuring ToD input or output

To use a ToD clock, you must configure ToD input or output:

· ToD input—The device obtains clock signals from an external ToD clock and synchronizes ToD to all cards on the device.

· ToD output—The device operates as a ToD clock to synchronize ToD to other devices in the PTP network.

To implement more accurate time synchronization, you can specify a delay correction value.

When the device connects to a ToD clock source correctly and is configured with this setting, all PTP instances configured on the device use the ToD clock source as its GM.

Restrictions and guidelines

Only the ToD clocks on the active MPU can be used as clock sources. The ToD clocks on the standby MPU cannot be used as clock sources.

To use a ToD clock source, you must use the ptp { tod0 | tod1 } command to specify whether to send or receive ToD clock signals.

You can configure this setting only after associating a minimum of one PTP instance with a domain.

The device automatically deletes the ToD clock configuration if all PTP domain configurations are deleted.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure ToD input or output.	ptp { tod0 \| tod1 } { input [ delay input-delay-time ] \| output [ delay output-delay-time ] }	The tod0 keyword can be used only with the input keyword, and the tod1 keyword can be used only with the output keyword. By default, the device receives signals from an external ToD clock.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Configure ToD input or output.

ptp { tod0 | tod1 } { input [ delay input-delay-time ] | output [ delay output-delay-time ] }

The tod0 keyword can be used only with the input keyword, and the tod1 keyword can be used only with the output keyword.

By default, the device receives signals from an external ToD clock.

Configuring the PTP offset threshold and PTP synchronization suppressions

About this task

If the calculated offset exceeds the threshold, the device will suppress PTP time synchronization. Only when the suppression count reaches the specified value, the device performs PTP time synchronization. This prevents the device from synchronizing to an incorrect PTP time when the PTP time provided by the master device is instable.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure parameters for PTP instance 0, skip this step.
3. Configure the PTP offset threshold and the number of times PTP time synchronization is suppressed.	ptp time-offset { suppression-count suppression-count \| suppression-threshold threshold-value } *	By default, the PTP time offset threshold is 3000 nanoseconds and PTP time synchronization is suppressed twice.

Setting ToD clock parameters

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Set ToD clock parameters.	ptp clock-source { tod0 \| tod1 } { accuracy acc-value \| class class-value \| time-source ts-value }	By default, the time accuracy is 32, the time class is 6, and the attribute value is 32 for a ToD clock.

Configuring a priority for a clock

About configuring a priority for a clock

Priorities for clocks are used to elect the GM. The smaller the priority value, the higher the priority.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enter PTP instance view.	ptp instance ptp-instance-id	To configure settings for PTP instance 0, skip this step.
3. Configure the priority for the specified clock for GM election through BMC.	ptp priority clock-source { local \| tod0 \| tod1 } { priority1 priority1 \| priority2 priority2 }	The default value varies by PTP profile: · IEEE 1588 version 2, AES67-2015, or SMPTE ST 2059-2—The priority 1 and priority 2 values are both 128. · IEEE 802.1AS PTP profile—The priority 1 value is 246 and the priority 2 value is 248.

Configuring PTP logging

About this task

PTP logs help monitor the clock source status. The following PTP logs are available:

· PTP log that indicates a lower time class

Each PTP clock source has a class value. For a ToD clock source, you can set its class value by using the ptp clock-source command. The higher the value, the lower the class. When the class value of the clock source crosses the class threshold, the system outputs a log for notification.

· PTP log that indicates a higher time offset between the external reference clock and the PTP clock

If the device uses an external reference clock, it periodically calculates the time offset between the external reference clock and the PTP clock. When the offset exceeds the threshold, the device outputs a log for notification

· PTP logs that indicate a higher time-offset-sum peak-to-peak value

The PTP module calculates the time-offset-sum peak-to-peak value at specific intervals and compares the value with the threshold configured by this command. If the value is larger than the threshold, the system outputs a log for notification.

· PTP logs that indicate the time-locked or time-unlocked state

When the time offset of the PTP reference clock crosses the PTP time locking threshold, the PTP time is put into unlocked state. The system outputs a time-unlocked log for notification. When the time offset of the PTP reference clock drops to or below the PTP time locking threshold, the PTP time is put into locked state. The system outputs a time-locked log for notification.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure the class threshold for the clock source.	ptp alarm-threshold clock-source-class class-value	By default, the class threshold for the clock source is 6. Only the IEEE 1588 version 2 PTP profile supports this configuration.
3. Configure the time-offset threshold between the external reference clock and the PTP clock.	ptp alarm-threshold time-offset time-offset-value	By default, the time-offset threshold is 500 ns between the external reference clock and the PTP clock. Only the IEEE 1588 version 2 PTP profile supports this configuration.
4. Set the time-offset-sum peak-to-peak threshold.	ptp alarm-threshold time-offset-sum pk-pk threshold-value	By default, the time-offset-sum peak-to-peak threshold is 500 ns. Only the IEEE 1588 version 2 PTP profile supports this configuration.
5. Set the PTP time locking and unlocking thresholds.	ptp alarm-threshold { time-lock lock-value \| time-unlock unlock-value } *	By default, the PTP time locking threshold is 200 ns and unlocking threshold is 300 ns.

Enabling SNMP notification for the PTP module

About this task

To get informed of important events of the PTP module, enable SNMP notification for the PTP module.

The notifications generated for the PTP module will be sent to the SNMP module of the device. Configure SNMP notification parameters for the notifications to be output as needed.

For information about SNMP and SNMP notifications, see SNMP configuration in Network Management and Monitoring Configuration Guide.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable SNMP notification for the PTP module.	snmp-agent trap enable ptp	By default, SNMP notification is enabled for the PTP module.

Display and maintenance commands for PTP

Execute display commands in any view and the reset command in user view.

Task	Command
Display PTP clock information.	display ptp clock [ all \| instance ptp-instance-id ]
Display the delay correction history.	display ptp corrections [ all \| instance ptp-instance-id ]
Display information about foreign master nodes.	display ptp foreign-masters-record [ interface interface-type interface-number ] [ all \| instance ptp-instance-id ]
Display PTP information on one or all interfaces.	display ptp interface [ interface-type interface-number \| brief ] [ all \| instance ptp-instance-id ]
Display brief PTP information on all interfaces.	display ptp interface brief
Display brief information about the PTP synchronization path from the GM to the device.	display ptp path-trace
Display parent node information for the PTP device.	display ptp parent [ all \| instance ptp-instance-id ]
Display historical role change information for PTP ports.	display ptp port-history [ interface interface-type interface-number ] [ all \| instance ptp-instance-id ]
Display PTP statistics.	display ptp statistics [ interface interface-type interface-number ] [ all \| instance ptp-instance-id ]
Display PTP clock time properties.	display ptp time-property [ all \| instance ptp-instance-id ]
Clear PTP statistics.	reset ptp statistics [ interface interface-type interface-number ] [ all \| instance ptp-instance-id ]

‌

PTP configuration examples

Example: Configuring PTP configuration(IEEE 1588 version 2, IEEE 802.3/Ethernet transport, multicast transmission)

Network configuration

As shown in Figure 4, configure PTP (IEEE 1588 version 2, IEEE 802.3/Ethernet transport, multicast transmission) to enable time synchronization between Device A and Device C.

· Specify the IEEE 1588 version 2 PTP profile and the IEEE 802.3/Ethernet transport protocol for PTP messages on Device A, Device B, and Device C.

· Use the IEEE 802.3/Ethernet transport protocol for PTP messages.

· Assign Device A, Device B, and Device C to the same PTP domain. Specify the OC clock node type for Device A and Device C, and E2ETC clock node type for Device B. All clock nodes elect a GM through BMC in the PTP domain.

· Use the default Request_Response delay measurement mechanism on Device A and Device C.

Figure 4 Network diagram

‌

Procedure

1. Configure Device A:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceA] ptp mode oc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Specify PTP for obtaining the time.

[DeviceA] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

2. Configure Device B:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile 1588v2

# Specify the E2ETC clock node type.

[DeviceB] ptp mode e2etc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# Enable PTP on GigabitEthernet 1/0/2.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

3. Configure Device C:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceC] ptp mode oc

# Specify a PTP domain.

[DeviceC] ptp domain 0

# Enable PTP globally.

[DeviceC] ptp global enable

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet 1/0/1.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

Verifying the configuration

When the network is stable, perform the following tasks:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 0

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master P2P Two 0

# Display PTP clock information on Device B.

[DeviceB] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : E2ETC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 N/A P2P Two 0

GE1/0/2 0 N/A P2P Two 0

The command outputs show that Device A is elected as the GM, GigabitEthernet1/0/1 on Device A is the master port, and Device B has synchronized to Device A.

Example: Configuring PTP (IEEE 1588 version 2, IPv4 UDP transport, multicast transmission)

Network configuration

As shown in Figure 5, configure PTP (IEEE 1588 version 2, IPv4 UDP transport, multicast transmission) to enable time synchronization between the devices.

· Specify the IEEE 1588 version 2 PTP profile for Device A, Device B, and Device C.

· Use the IPv4 UDP transport protocol for PTP messages.

· Assign Device A, Device B, and Device C to the same PTP domain. Specify the OC clock node type for Device A and Device C, and P2PTC clock node type for Device B. All clock nodes elect a GM through BMC in the PTP domain.

· Specify the peer delay measurement mechanism (p2p) for Device A and Device C.

Figure 5 Network diagram

‌

Procedure

1. Configure Device A:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceA] ptp mode oc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceA] ptp source 10.10.1.1

# Specify PTP for obtaining the time.

[DeviceA] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the IPv4 UDP transport protocol and the peer delay measurement mechanism, and enable PTP.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp transport-protocol udp [DeviceA-GigabitEthernet1/0/1] ptp delay-mechanism p2p

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

2. Configure Device B:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile 1588v2

# Specify the P2PTC clock node type.

[DeviceB] ptp mode p2ptc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceB] ptp source 10.10.2.1

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the IPv4 UDP transport protocol and enable PTP.

[DeviceB] interface gigabitethernet 1/0/1

DeviceB-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# On GigabitEthernet 1/0/2, specify the IPv4 UDP transport protocol and enable PTP.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

3. Configure Device C:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceC] ptp mode oc

# Specify a PTP domain.

[DeviceC] ptp domain 0

# Enable PTP globally.

[DeviceC] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceC] ptp source 10.10.3.1

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the IPv4 UDP transport protocol and the peer delay measurement mechanism, and enable PTP.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp [DeviceC-GigabitEthernet1/0/1] ptp delay-mechanism p2p

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

Verifying the configuration

When the network is stable, perform the following tasks:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 0

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master P2P Two 0

# Display PTP clock information on Device B.

[DeviceB] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : P2PTC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 N/A P2P Two 0

GE1/0/2 0 N/A P2P Two 0

The command outputs show that Device A is elected as the GM, GigabitEthernet1/0/1 on Device A is the master port, and Device B has synchronized to Device A.

Example: Configuring multiple PTP instances (IEEE 1588 version 2, multicast transmission)

As shown in , configure two PTP instances on a PTP network.

· PTP instance 1: Assign Device A, Device B, and Device C to PTP instance 1.

¡ Specify the IEEE 1588 version 2 PTP profile and IEEE 802.3/Ethernet transport of PTP messages for the devices and assign the devices to PTP domain 1.

¡ Specify the OC clock node type for Device A and Device C and E2ETC clock node type for Device B. All these clock nodes elect a GM through BMC.

¡ Use the default Request_Response delay measurement mechanism on all clock nodes in PTP instance 1.

· PTP instance 2: Assign Device D, Device B, and Device E to PTP instance 2.

¡ Specify the IEEE 1588 version 2 PTP profile and IPv4 UDP transport of PTP messages for the devices and assign the devices to PTP domain 2.

¡ Specify the OC clock node type for Device D and Device E and P2PTC clock node type for Device B. All the clock nodes elect a GM through BMC.

¡ Use the peer delay measurement mechanism on Device D and Device E.

Figure 6 Network diagram

‌

Procedure

1. Configure PTP instance 1 (IEEE 802.3/Ethernet transport of PTP messages)

a. Configure Device A:

# Enable PTP globally.

<DeviceA> system-view

[DeviceA] ptp global enable

# Create a PTP instance, specifying its ID as 1 and name as ptp1, and enter its view.

[DeviceA] ptp instance 1 name ptp1

[DeviceA-ptp-instance-1]

# Specify the IEEE 1588 version 2 PTP profile.

[DeviceA-ptp-instance-1] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceA-ptp-instance-1] ptp mode oc

# Specify PTP domain 1.

[DeviceA-ptp-instance-1] ptp domain 1

[DeviceA-ptp-instance-1] quit

# Specify PTP for obtaining the time on the default MDC.

[DeviceA] clock protocol ptp mdc 1

# Assign GigabitEthernet 1/0/1 to PTP instance 1, enter interface PTP instance view, and enable PTP.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp instance 1

[DeviceA-GigabitEthernet1/0/1-ptp-instance-1] ptp enable

[DeviceA-GigabitEthernet1/0/1-ptp-instance-1] quit

[DeviceA-GigabitEthernet1/0/1] quit

b. Configure Device B:

# Enable PTP globally.

<DeviceB> system-view

[DeviceB] ptp global enable

# Create a PTP instance, specifying its ID as 1 and name as ptp1, and enter its view.

[DeviceB] ptp instance 1 name ptp1

[DeviceB-ptp-instance-1]

# Specify the IEEE 1588 version 2 PTP profile.

[DeviceB-ptp-instance-1] ptp profile 1588v2

# Specify the E2ETC clock node type.

[DeviceB-ptp-instance-1] ptp mode e2etc

# Specify PTP domain 1.

[DeviceB-ptp-instance-1] ptp domain 1

[DeviceB-ptp-instance-1] quit

# Specify PTP for obtaining the time on the default MDC.

[DeviceB] clock protocol ptp mdc 1

# Assign GigabitEthernet 1/0/1 to PTP instance 1, enter interface PTP instance view, and enable PTP.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] ptp instance 1

[DeviceB-GigabitEthernet1/0/1-ptp-instance-1] ptp enable

[DeviceB-GigabitEthernet1/0/1-ptp-instance-1] quit

[DeviceB-GigabitEthernet1/0/1] quit

# Assign GigabitEthernet 1/0/2 to PTP instance 1, enter interface PTP instance view, and enable PTP.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp instance 1

[DeviceB-GigabitEthernet1/0/2-ptp-instance-1] ptp enable

[DeviceB-GigabitEthernet1/0/2-ptp-instance-1] quit

[DeviceB-GigabitEthernet1/0/2] quit

c. Configure Device C:

# Enable PTP globally.

<DeviceC> system-view

[DeviceC] ptp global enable

# Create a PTP instance, specifying its ID as 1 and name as ptp1, and enter its view.

[DeviceC] ptp instance 1 name ptp1

[DeviceC-ptp-instance-1]

# Specify the IEEE 1588 version 2 PTP profile.

[DeviceC-ptp-instance-1] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceC-ptp-instance-1] ptp mode oc

# Specify PTP domain 1.

[DeviceC-ptp-instance-1] ptp domain 1

[DeviceC-ptp-instance-1] quit

# Specify PTP for obtaining the time on the default MDC.

[DeviceC] clock protocol ptp mdc 1

# Assign GigabitEthernet 1/0/1 to PTP instance 1, enter interface PTP instance view, and enable PTP.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp instance 1

[DeviceC-GigabitEthernet1/0/1-ptp-instance-1] ptp enable

[DeviceC-GigabitEthernet1/0/1-ptp-instance-1] quit

[DeviceC-GigabitEthernet1/0/1] quit

2. Configure PTP instance 2 (IPv4 UDP transport of PTP messages)

a. Configure Device D:

# Enable PTP globally.

<DeviceD> system-view

[DeviceD] ptp global enable

# Create a PTP instance, specifying its ID as 2 and name as ptp2, and enter its view.

[DeviceD] ptp instance 2 name ptp2

[DeviceD-ptp-instance-2]

# Specify the IEEE 1588 version 2 PTP profile.

[DeviceD-ptp-instance-2] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceD-ptp-instance-1] ptp mode oc

# Specify PTP domain 2.

[DeviceD-ptp-instance-2] ptp domain 2

# Specify the source IP address for multicast PTP messages transmitted over IPv4 UDP.

[DeviceD-ptp-instance-2] ptp source 10.10.1.1

[DeviceD-ptp-instance-2] quit

# Specify PTP for obtaining the time on the default MDC.

[DeviceD] clock protocol ptp mdc 1

# Assign GigabitEthernet1/0/1 to PTP instance 2 and enter interface PTP instance view. Specify IPv4 UDP transport of PTP messages and the peer delay measurement mechanism and enable PTP.

[DeviceD] interface gigabitethernet 1/0/1

[DeviceD-GigabitEthernet1/0/1] ptp instance 2

[DeviceD-GigabitEthernet1/0/1-ptp-instance-2] ptp transport-protocol udp

[DeviceD-GigabitEthernet1/0/1-ptp-instance-2] ptp delay-mechanism p2p

[DeviceD-GigabitEthernet1/0/1-ptp-instance-2] ptp enable

[DeviceD-GigabitEthernet1/0/1-ptp-instance-2] quit

[DeviceD-GigabitEthernet1/0/1] quit

b. Configure Device B:

# Create a PTP instance, specifying its ID as 2 and name as ptp2, and enter its view.

<DeviceB> system-view

[DeviceB] ptp instance 2 name ptp2

# Specify the IEEE 1588 version 2 PTP profile.

[DeviceB-ptp-instance-2] ptp profile 1588v2

# Specify the P2PTC clock node type.

[DeviceB-ptp-instance-2] ptp mode p2ptc

# Specify PTP domain 2.

[DeviceB-ptp-instance-2] ptp domain 2

# Specify the source IP address for multicast PTP messages transmitted over IPv4 UDP.

[DeviceB-ptp-instance-2] ptp source 10.10.2.1

[DeviceB-ptp-instance-2] quit

# Specify PTP for obtaining the time on the default MDC. (Skip this step if this setting has been configured.)

[DeviceB] clock protocol ptp mdc 1

# Assign GigabitEthernet 1/0/3 to PTP instance and enter interface PTP instance view. Specify IPv4 UDP transport of PTP messages and enable PTP.

[DeviceB] interface gigabitethernet 1/0/3

[DeviceB-GigabitEthernet1/0/3] ptp instance 2

[DeviceB-GigabitEthernet1/0/3-ptp-instance-2] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/3-ptp-instance-2] ptp enable

[DeviceB-GigabitEthernet1/0/3-ptp-instance-2] quit

[DeviceB-GigabitEthernet1/0/3] quit

# Assign GigabitEthernet 1/0/4 to PTP instance and enter interface PTP instance view. Specify IPv4 UDP transport of PTP messages and enable PTP.

[DeviceB] interface gigabitethernet 1/0/4

[DeviceB-GigabitEthernet1/0/4] ptp instance 2

[DeviceB-GigabitEthernet1/0/4-ptp-instance-2] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/4-ptp-instance-2] ptp enable

[DeviceB-GigabitEthernet1/0/4-ptp-instance-2] quit

[DeviceB-GigabitEthernet1/0/4] quit

c. Configure Device E:

# Enable PTP globally.

<DeviceE> system-view

[DeviceE] ptp global enable

# Create a PTP instance, specifying its ID as 2 and name as ptp2, and enter its view.

[DeviceE] ptp instance 2 name ptp2

[DeviceE-ptp-instance-2]

# Specify the IEEE 1588 version 2 PTP profile.

[DeviceE-ptp-instance-2] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceE-ptp-instance-2] ptp mode oc

# Specify PTP domain 2.

[DeviceE-ptp-instance-2] ptp domain 2

# Specify the source IP address for multicast PTP messages transmitted over IPv4 UDP.

[DeviceE-ptp-instance-2] ptp source 10.10.3.1

[DeviceE-ptp-instance-2] quit

# Specify PTP for obtaining the time on the default MDC.

[DeviceE] clock protocol ptp mdc 1

# Assign GigabitEthernet 1/0/4 to PTP instance 2 and enter interface PTP instance view. Specify IPv4 UDP transport of PTP messages and the peer delay measurement mechanism and enable PTP.

[DeviceE] interface gigabitethernet 1/0/1

[DeviceE-GigabitEthernet1/0/1] ptp instance 2

[DeviceE-GigabitEthernet1/0/1-ptp-instance-2] ptp transport-protocol udp

[DeviceE-GigabitEthernet1/0/1-ptp-instance-2] ptp delay-mechanism p2p

[DeviceE-GigabitEthernet1/0/1-ptp-instance-2] ptp enable

[DeviceE-GigabitEthernet1/0/1-ptp-instance-2] quit

[DeviceE-GigabitEthernet1/0/1] quit

Verifying the configuration

1. Verify the configuration of PTP instance 1.

When the network is stable, perform the following tasks to verify the configuration of PTP instance 1.

¡ Use the display ptp clock command to display PTP clock information.

¡ Use the display ptp interface brief command to display brief PTP running information for all PTP interfaces.

# Display PTP clock information for PTP instance 1 on Device A.

[DeviceA] display ptp clock instance 1

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 1

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP running information for all PTP interfaces on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 1 Master E2E Two 0

# Display PTP clock information for PTP instance 1 on Device B.

[DeviceB] display ptp clock instance 1

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : E2ETC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 1

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP running information for all PTP interfaces on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 1 N/A E2E Two 0

GE1/0/2 1 N/A E2E Two 0

GE1/0/3 2 N/A P2P Two 0

GE1/0/4 2 N/A P2P Two 0

The command output shows that Device A is elected as the GM, and GigabitEthernet1/0/1 on Device A sends time synchronization information to its downstreams as a master port.

2. Verify the configuration of PTP instance 2.

When the network is stable, perform the following tasks to verify the configuration of PTP instance 2:

¡ Use the display ptp clock command to display PTP clock information.

¡ Use the display ptp interface brief command to display brief PTP running information for all PTP interfaces.

# Display PTP clock information for PTP instance 2 on Device D.

[DeviceD] display ptp clock instance 2

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 2

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP running information for all PTP interfaces on Device D.

[DeviceD] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 2 Master P2P Two 0

# Display PTP clock information for PTP instance 2 on Device B.

[DeviceB] display ptp clock instance 2

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : P2PTC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 2

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP running information for all PTP interfaces on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 1 N/A E2E Two 0

GE1/0/2 1 N/A E2E Two 0

GE1/0/3 2 N/A P2P Two 0

GE1/0/4 2 N/A P2P Two 0

The command output shows that Device D is elected as the GM, and GigabitEthernet1/0/1 on Device D sends time synchronization information to its downstreams as a master port.

Example: Configuring PTP (IEEE 1588 version 2, IPv4 UDP transport, unicast transmission)

Network configuration

As shown in Figure 7, configure PTP (IEEE 1588 version 2, IPv4 UDP transport, unicast transmission) to enable Device A, Device B, Device C, and the base station to synchronize the time with the ToD clock source.

· Specify the IEEE 1588 version 2 PTP profile and unicast IPv4 UDP transport of PTP messages for Device A, Device B, and Device C.

· Assign Device A, Device B, Device C, and the base station to PTP domain 0. Specify the BC clock node type for Device A, Device B, and Device C.

· Connect Device A to the ToD clock source and Device C to the base station.

· Use the default Request_Response delay measurement mechanism on all clock nodes in the PTP domain.

Figure 7 Network diagram

‌

Procedure

1. Assign IP addresses to the interfaces, and make sure the devices can reach each other, as shown in Figure 7. (Details not shown.)

2. Configure Device A:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile 1588v2

# Specify the BC clock node type.

[DeviceA] ptp mode bc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Specify PTP for obtaining the time on the default MDC.

[DeviceA] clock protocol ptp mdc 1

# Configure the delay time correction as 1000 nanoseconds for receiving ToD 0 clock signals.

[DeviceA] ptp tod0 input delay 1000

# Set priority 1 to 0 for the ToD 0 clock.

[DeviceA] ptp priority clock-source tod0 priority1 0

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP message transmission over IPv4 UDP, and enable PTP.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceA-GigabitEthernet1/0/1] ptp unicast-destination 10.10.10.2

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

3. Configure Device B:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile 1588v2

# Specify the BC clock node type.

[DeviceB] ptp mode bc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP message transmission over IPv4 UDP, and enable PTP.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/1] ptp unicast-destination 10.10.10.1

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# On GigabitEthernet 1/0/2, configure the destination IP address for unicast PTP message transmission over IPv4 UDP, and enable PTP.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/2] ptp unicast-destination 11.10.10.1

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

4. Configure Device C:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile 1588v2

# Specify the BC clock node type.

[DeviceC] ptp mode bc

# Specify a PTP domain.

[DeviceC] ptp domain 0

# Enable PTP globally.

[DeviceC] ptp global enable

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP messages transmitted over IPv4 UDP, and enable PTP.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceC-GigabitEthernet1/0/1] ptp unicast-destination 11.10.10.2

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

# On GigabitEthernet1/0/2, configure the destination IP address for unicast PTP messages transmitted over IPv4 UDP, and enable PTP.

[DeviceC] interface gigabitethernet 1/0/2

[DeviceC-GigabitEthernet1/0/2] ptp transport-protocol udp

[DeviceC-GigabitEthernet1/0/2] ptp unicast-destination 12.10.10.1

[DeviceC-GigabitEthernet1/0/2] ptp enable

[DeviceC-GigabitEthernet1/0/2] quit

5. Configure the base station.

# Specify PTP domain 0.

# Specify IPv4 UDP transport of PTP messages.

# Set the destination IP address of unicast PTP messages to 12.10.10.2.

# Specify the Request_Response delay measurement mechanism.

For more information, see the configuration guide for the base station.

Verifying the configuration

When the network is stable, perform the following tasks:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : BC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : ToD0

ToD direction : In

ToD delay time : 1000 (ns)

Clock domain : 0

Number of PTP ports : 1

Priority1 : 0

Priority2 : 128

Clock quality :

Class : 6

Accuracy : 32

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master E2E Two 0

# Display PTP clock information on Device C.

[DeviceC] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : BC

Slave only : No

Lock status : Locked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 50 (ns)

Mean path delay : 2791 (ns)

Steps removed : 2

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device C.

[DeviceC] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Slave E2E Two 0

GE1/0/2 0 Master E2E Two 0

Example: Configuring PTP (IEEE 1588 version 2, IPv4 UDP transport, unicast transmission, unicast forwarding)

Network configuration

As shown in Figure 8, configure PTP (IEEE 1588 version 2, IPv4 UDP transport, unicast transmission, unicast forwarding) for time synchronization between Device A, Device B, and Device C.

· Specify the IEEE 1588 version 2 PTP profile and unicast IPv4 UDP transport of PTP messages for Device A, Device B, and Device C.

· Assign Device A, Device B, and Device C to PTP domain 0. Specify the OC clock node type for Device A and Device C and E2ETC clock node type for Device B.

· Enable unicast forwarding of PTP messages on Device B.

· Use the default request-response delay measurement mechanism for Device A and Device C.

Figure 8 Network diagram

‌

Procedure

1. Assign IP addresses to the interfaces, and make sure the devices can reach each other, as shown in Figure 8. (Details not shown.)

2. Configure Device A:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceA] ptp mode Oc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Specify PTP for obtaining the time on the default MDC.

[DeviceA] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify IPv4 UDP transport of PTP messages, configure the unicast destination IP address for PTP messages, specify the request-response delay measurement mechanism, and enable PTP.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceA-GigabitEthernet1/0/1] ptp unicast-destination 10.10.3.1

[DeviceA-GigabitEthernet1/0/1] ptp delay-mechanism e2e

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

3. Configure Device B:

# Enable unicast forwarding of PTP messages.

<DeviceB> system-view

[DeviceB] ptp unicast-forward enable

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile 1588v2

# Specify the E2ETC clock node type.

[DeviceB] ptp mode e2etc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet1/0/1.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# Enable PTP on GigabitEthernet1/0/2.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

4. Configure Device C:

# Specify the IEEE 1588 version 2 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile 1588v2

# Specify the OC clock node type.

[DeviceC] ptp mode oc

# Specify a PTP domain.

[DeviceC] ptp domain 0

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceC-GigabitEthernet1/0/1] ptp unicast-destination 10.10.1.1

[DeviceC-GigabitEthernet1/0/1] ptp delay-mechanism e2e

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

Verifying the configuration

When the network is stable, perform the following tasks:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 0

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Sun Jan 15 20:57:29 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master E2E Two 0

# Display PTP clock information on Device B.

[DeviceB] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 1588 Version 2

PTP mode : E2ETC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Sun Jan 15 20:57:29 2020

# Display brief PTP statistics on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 N/A E2E Two 0

GE1/0/2 0 N/A E2E Two 0

The command outputs show that Device A is elected as the GM, and GigabitEthernet 1/0/1 on Device A distributes timing information as a master port.

Example: Configuring PTP (IEEE 802.1AS, IEEE 802.3/Ethernet transport, multicast transmission)

Network configuration

As shown in Figure 9, configure PTP (IEEE 802.1AS, IEEE 802.3/Ethernet transport, multicast transmission) to enable time synchronization between Device A, Device B, and Device C.

· Specify the IEEE 802.1AS PTP profile for Device A, Device B, and Device C.

· Assign Device A, Device B, and Device C to the same PTP domain. Specify the OC clock node type for Device A and Device C, and P2PTC clock node type for Device B. The clock nodes elect a GM through BMC in the PTP domain.

· Use the default peer delay measurement mechanism on all clock nodes in the PTP domain.

Figure 9 Network diagram

‌

Procedure

IMPORTANT:

The IEEE 802.1AS PTP profile transports PTP messages over IEEE 802.3/Ethernet rather than IPv4 UDP in multicast rather than unicast mode.

1. Configure Device A:

# Specify the IEEE 802.1AS PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile 802.1AS

# Specify the OC clock node type.

[DeviceA] ptp mode oc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Specify PTP for obtaining the time.

[DeviceA] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

2. Configure Device B:

# Specify the IEEE 802.1AS PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile 802.1AS

# Specify the P2PTC clock node type.

[DeviceB] ptp mode p2ptc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# Enable PTP on GigabitEthernet 1/0/2.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

3. Configure Device C:

# Specify the IEEE 1588 802.1AS PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile 802.1AS

# Specify the OC clock node type.

[DeviceC] ptp mode oc

# Specify a PTP domain.

[DeviceC] ptp domain 0

# Enable PTP globally.

[DeviceC] ptp global enable

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# Enable PTP on GigabitEthernet 1/0/1.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

Verifying the configuration

When the network is stable, perform the following tasks:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 802.1AS

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 0

Number of PTP ports : 1

Priority1 : 246

Priority2 : 248

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 16640

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master P2P Two 0

# Display PTP clock information on Device B.

[DeviceB] display ptp clock

PTP global state : Enabled

PTP profile : IEEE 802.1AS

PTP mode : P2PTC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 246

Priority2 : 248

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 16640

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 N/A P2P Two 0

GE1/0/2 0 N/A P2P Two 0

The command outputs show that Device A is elected as the GM, GigabitEthernet1/0/1 on Device A is the master port, and Device B has synchronized to Device A.

Example: Configuring PTP (SMPTE ST 2059-2, IPv4 UDP transport, multicast transmission)

Network configuration

As shown in Figure 10, configure PTP (SMPTE ST 2059-2, IPv4 UDP transport, multicast transmission) to enable time synchronization between Device A and Device C:

· Specify the SMPTE ST 2059-2 PTP profile and multicast IPv4 UDP transport of PTP messages for Device A, Device B, and Device C.

· Specify the OC clock node type for Device A and Device C, and the P2PTC clock node type for Device B. All clock nodes elect a GM through BMC.

· Use the peer delay measurement mechanism on all clock nodes in the PTP domain.

Figure 10 Network diagram

‌

Procedure

IMPORTANT:

The SMPTE ST 2059-2 PTP profile transports PTP messages over IPv4 UDP rather than IEEE 802.3/Ethernet. The profile supports both multicast and unicast transmission modes.

1. Configure Device A:

# Specify the SMPTE ST 2059-2 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile st2059-2

# Specify the OC clock node type.

[DeviceA] ptp mode oc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceA] ptp source 10.10.1.1

# Specify PTP for obtaining the time.

[DeviceA] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the delay measurement mechanism as p2p and enable PTP.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp transport-protocol udp [DeviceA-GigabitEthernet1/0/1] ptp delay-mechanism p2p

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

2. Configure Device B:

# Specify the SMPTE ST 2059-2 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile st2059-2

# Specify the P2PTC clock node type.

[DeviceB] ptp mode p2ptc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Configure the source IP address for multicast PTP messages transmitted over IPv4 UDP.

[DeviceB] ptp source 10.10.2.1

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, enable PTP.

[DeviceB] interface gigabitethernet 1/0/1

DeviceB-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# On GigabitEthernet 1/0/2, enable PTP.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

3. Configure Device C:

# Specify the SMPTE ST 2059-2 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile st2059-2

# Specify the OC clock node type.

[DeviceC] ptp mode oc

# Specify the PTP domain.

[DeviceC] ptp domain 0

# Enable PTP globally.

[DeviceC] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceC] ptp source 10.10.3.1

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the delay measurement mechanism as p2p and enable PTP.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp [DeviceC-GigabitEthernet1/0/1] ptp delay-mechanism p2p

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

Verifying the configuration

When the network is stable, perform the following tasks to verify the PTP configuration:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : SMPTE ST 2059-2

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 0

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master P2P Two 0

# Display PTP clock information on Device B.

[DeviceB] display ptp clock

PTP global state : Enabled

PTP profile : SMPTE ST 2059-2

PTP mode : P2PTC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 N/A P2P Two 0

GE1/0/2 0 N/A P2P Two 0

The output shows that Device A is elected as the GM and GigabitEthernet1/0/1 on Device A sends time synchronization information to its downstreams as a master port.

Example: Configuring PTP (SMPTE ST 2059-2, IPv4 UDP transport, unicast transmission)

Network configuration

As shown in Figure 11, configure PTP (SMPTE ST 2059-2, IPv4 UDP transport, unicast transmission) to enable Device A, Device B, Device C, and the base station to synchronize time with the ToD clock source .

· Specify the SMPTE ST 2059-2 PTP profile and unicast IPv4 UDP transport of PTP messages for Device A, Device B, and Device C.

· Assign Device A, Device B, Device C, and the base station to PTP domain 0. Specify the BC clock node type for Device A, Device B, and Device C.

· Connect Device A to the ToD clock source and Device C to the base station.

· Use the default Request_Response delay measurement mechanism on all clock nodes in the PTP domain.

Figure 11 Network diagram

‌

Procedure

IMPORTANT:

The SMPTE ST 2059-2 PTP profile supports IPv4 UDP transport rather than IEEE 802.3/Ethernet transport of PTP messages. It supports both multicast and unicast transmission of PTP messages.

1. Assign IP addresses to the interfaces, and make sure the devices can reach each other, as shown in Figure 11. (Details not shown.)

2. Configure Device A:

# Specify the SMPTE ST 2059-2 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile st2059-2

# Specify the BC clock node type.

[DeviceA] ptp mode bc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Specify PTP for obtaining the time on the default MDC.

[DeviceA] clock protocol ptp mdc 1

# Configure the device to receive ToD 0 clock signals and set the delay correction value to 1000 nanoseconds.

[DeviceA] ptp tod0 input delay 1000

# Set priority 1 to 0 for the ToD 0 clock.

[DeviceA] ptp priority clock-source tod0 priority1 0

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP messages and enable PTP. (The SMPTE ST 2059-2 PTP profile transports PTP messages over IPv4 UDP by default.)

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceA-GigabitEthernet1/0/1] ptp unicast-destination 10.10.10.2

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

3. Configure Device B:

# Specify the SMPTE ST 2059-2 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile st2059-2

# Specify the BC clock node type.

[DeviceB] ptp mode bc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP messages and enable PTP. (The SMPTE ST 2059-2 PTP profile transports PTP messages over IPv4 UDP by default.)

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] ptp unicast-destination 10.10.10.1

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# On GigabitEthernet 1/0/2, configure the destination IP address for unicast PTP messages and enable PTP. (The SMPTE ST 2059-2 PTP profile transports PTP messages over IPv4 UDP by default.)

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp unicast-destination 11.10.10.1

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

4. Configure Device C:

# Specify the SMPTE ST 2059-2 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile st2059-2

# Specify the BC clock node type.

[DeviceC] ptp mode bc

# Enable PTP globally.

[DeviceC] ptp global enable

# Specify a PTP domain.

[DeviceC] ptp domain 0

# Configure the device to send ToD 0 clock signals and set the delay correction value to 1000 nanoseconds.

[DeviceC] ptp tod0 output delay 100

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP messages and enable PTP.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceC-GigabitEthernet1/0/1] ptp unicast-destination 11.10.10.2

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

# On GigabitEthernet 1/0/1, configure the destination IP address for unicast PTP messages and enable PTP. (The SMPTE ST 2059-2 PTP profile transports PTP messages over IPv4 UDP by default.)

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceC-GigabitEthernet1/0/1] ptp unicast-destination 11.10.10.2

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

5. Configure the base station.

# Specify PTP domain 0.

# Specify IPv4 UDP transport of PTP messages.

# Set the destination IP address of unicast PTP messages to 12.10.10.2.

# Specify the Request_Response delay measurement mechanism.

For more information, see the configuration guide for the base station.

Verifying the configuration

When the network is stable, perform the following tasks to verify the PTP configuration:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP running information.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : SMPTE ST 2059-2

PTP mode : BC

Slave only : No

Lock status : Locked

Clock ID : 000FE2-FFFE-FF0000

Clock type : ToD0

ToD direction : In

ToD delay time : 1000 (ns)

Clock domain : 0

Number of PTP ports : 1

Priority1 : 0

Priority2 : 128

Clock quality :

Class : 6

Accuracy : 32

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP running information on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master E2E Two 0

# Display PTP clock information on Device C.

[DeviceC] display ptp clock

PTP global state : Enabled

PTP profile : SMPTE ST 2059-2

PTP mode : BC

Slave only : No

Lock status : Locked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 50 (ns)

Mean path delay : 2780 (ns)

Steps removed : 2

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP running information on Device C.

[DeviceC] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Slave E2E Two 0

GE1/0/2 0 Master E2E Two 0

Example: Configuring PTP (AES67-2015, IPv4 UDP transport, multicast transmission)

Network configuration

As shown in Figure 10, configure PTP (AES67-2015, IPv4 UDP transport, multicast transmission) to enable time synchronization between Device A and Device C:

· Specify the AES67-2015 PTP profile and multicast IPv4 UDP transport of PTP messages for Device A, Device B, and Device C.

· Specify the OC clock node type for Device A and Device C, and the P2PTC clock node type for Device B. All clock nodes elect a GM through BMC.

· Use the peer delay measurement mechanism on all clock nodes in the PTP domain.

Figure 12 Network diagram

‌

Procedure

IMPORTANT:

The AES67-2015 PTP profile transports PTP messages over IPv4 UDP rather than IEEE 802.3/Ethernet. The profile supports both multicast and unicast transmission modes.

1. Configure Device A:

# Specify the AES67-2015 PTP profile.

<DeviceA> system-view

[DeviceA] ptp profile aes67-2015

# Specify the OC clock node type.

[DeviceA] ptp mode oc

# Specify a PTP domain.

[DeviceA] ptp domain 0

# Enable PTP globally.

[DeviceA] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceA] ptp source 10.10.1.1

# Specify PTP for obtaining the time.

[DeviceA] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the delay measurement mechanism as p2p and enable PTP.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ptp transport-protocol udp [DeviceA-GigabitEthernet1/0/1] ptp delay-mechanism p2p

[DeviceA-GigabitEthernet1/0/1] ptp enable

[DeviceA-GigabitEthernet1/0/1] quit

2. Configure Device B:

# Specify the AES67-2015 PTP profile.

<DeviceB> system-view

[DeviceB] ptp profile aes67-2015

# Specify the P2PTC clock node type.

[DeviceB] ptp mode p2ptc

# Specify a PTP domain.

[DeviceB] ptp domain 0

# Enable PTP globally.

[DeviceB] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceB] ptp source 10.10.2.1

# Specify PTP for obtaining the time.

[DeviceB] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, enable PTP.

[DeviceB] interface gigabitethernet 1/0/1

DeviceB-GigabitEthernet1/0/1] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/1] ptp enable

[DeviceB-GigabitEthernet1/0/1] quit

# On GigabitEthernet 1/0/2, enable PTP.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ptp transport-protocol udp

[DeviceB-GigabitEthernet1/0/2] ptp enable

[DeviceB-GigabitEthernet1/0/2] quit

3. Configure Device C:

# Specify the AES67-2015 PTP profile.

<DeviceC> system-view

[DeviceC] ptp profile aes67-2015

# Specify the OC clock node type.

[DeviceC] ptp mode oc

# Specify the PTP domain.

[DeviceC] ptp domain 0

# Enable PTP globally.

[DeviceC] ptp global enable

# Configure the source IP address for multicast PTP message transmission over IPv4 UDP.

[DeviceC] ptp source 10.10.3.1

# Specify PTP for obtaining the time.

[DeviceC] clock protocol ptp mdc 1

# On GigabitEthernet 1/0/1, specify the delay measurement mechanism as p2p and enable PTP.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ptp transport-protocol udp [DeviceC-GigabitEthernet1/0/1] ptp delay-mechanism p2p

[DeviceC-GigabitEthernet1/0/1] ptp enable

[DeviceC-GigabitEthernet1/0/1] quit

Verifying the configuration

When the network is stable, perform the following tasks to verify the PTP configuration:

· Use the display ptp clock command to display PTP clock information.

· Use the display ptp interface brief command to display brief PTP statistics on an interface.

# Display PTP clock information on Device A.

[DeviceA] display ptp clock

PTP global state : Enabled

PTP profile : AES67-2015

PTP mode : OC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0000

Clock type : Local

Clock domain : 0

Number of PTP ports : 1

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : 0 (ns)

Mean path delay : 0 (ns)

Steps removed : 0

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device A.

[DeviceA] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 Master P2P Two 0

# Display PTP clock information on Device B.

[DeviceB] display ptp clock

PTP global state : Enabled

PTP profile : AES67-2015

PTP mode : P2PTC

Slave only : No

Lock status : Unlocked

Clock ID : 000FE2-FFFE-FF0001

Clock type : Local

Clock domain : 0

Number of PTP ports : 2

Priority1 : 128

Priority2 : 128

Clock quality :

Class : 248

Accuracy : 254

Offset (log variance) : 65535

Offset from master : N/A

Mean path delay : N/A

Steps removed : N/A

Local clock time : Tue Jul 23 09:41:50 2019

# Display brief PTP statistics on Device B.

[DeviceB] display ptp interface brief

Name InstID State Delay mechanism Clock step Asymmetry correction

GE1/0/1 0 N/A P2P Two 0

GE1/0/2 0 N/A P2P Two 0

The output shows that Device A is elected as the GM and GigabitEthernet1/0/1 on Device A sends time synchronization information to its downstreams as a master port.

13-Network Management and Monitoring Configuration Guides

Basic concepts

PTP profile

PTP domain

PTP instance

Optimal PTP domain

Clock node and PTP port

Master-member/subordinate relationship

Grandmaster clock

Specifying PTP for obtaining the time

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Specifying a PTP profile

Restrictions and guidelines

Procedure

Restrictions and guidelines

Configuring an OC to operate only as a member clock

About configuring an OC to operate only as a member clock

Restrictions and guidelines

Procedure

About PTP domains

Procedure

Restrictions and guidelines

Procedure

About enabling PTP on a port

Restrictions and guidelines

Procedure

About configuring the role of a PTP port

Restrictions and guidelines

Procedure

About the mode for carrying timestamps

Restrictions and guidelines

Procedure

About the delay measurement mechanism

Restrictions and guidelines

Procedure

About configuring one of the ports on a TC+OC clock as an OC-type port

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Configuring PTP message transmission and receipt

Setting the interval for sending announce messages and the timeout multiplier for receiving announce messages

About this task

Procedure

About this task

Procedure

About the minimum interval for sending Delay_Req messages

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About PTP message encapsulation protocols

Restrictions and guidelines

Procedure

Configuring a source IP address for multicast PTP message transmission over UDP

About configuring a source IP address for multicast PTP message transmission over UDP

Restrictions and guidelines

Procedure

Configuring a destination IP address for unicast PTP message transmission over UDP

About configuring a destination IP address for unicast PTP message transmission over UDP

Restrictions and guidelines

Prerequisites

Procedure

About the MAC address for non-Pdelay messages

Restrictions and guidelines

Procedure

Setting a DSCP value for PTP messages transmitted over UDP

About DSCP values for PTP messages

Restrictions and guidelines

Procedure

About specifying a VLAN tag for PTP messages

Procedure

About this task