Abstract: A network device may identify a link aggregation group (LAG) of a plurality of links between the network device and another network device. The network device may identify link aggregation control protocol (LACP) parameters that were communicated by the network device and the other network device in association with the LAG. The network device may determine, based on the LACP parameters, a priority order of the plurality of links in the LAG. The network device may communicate with the other network device, and based on the priority order of the plurality of links of the LAG, one or more precision time protocol (PTP) messages via the LAG. For example, the network device may determine that a first link and a second link in the priority order are not available, and therefore may communicate the one or more PTP messages via a third link in the priority order.

Abstract: A method may include (1) preparing, at a slave device, a request message that identifies an initial time-to-live value, (2) sending the request message to a plurality of candidate master devices, (3) receiving, at the slave device from one of the candidate master devices, a reply message that identifies a number of hops between the slave device and the one of the candidate master devices, (4) receiving, at the slave device from another one of the candidate master devices, another reply message that identifies another number of hops between the slave device and the another one of the candidate master devices, and then (5) synchronizing a clock of the slave device with a clock of the one of the candidate master devices due at least in part to the number of hops being less than the another number of hops. Various other apparatuses, systems, and methods are also disclosed.

Abstract: A first network device may receive, from a second network device, a clock quality indication that is associated with a clock of the second network device, wherein the clock of the second network device is a reference clock for a network that includes the first network device and the second network device. The first network device may determine, based on a clock signal of the second network device, that a quality metric of the clock does not satisfy a threshold. The first network device may provide, to the second network device, a clock fault notification to cause the second network device to downgrade the clock quality indication transmitted by the second network device. The first network device may select a new reference clock for the first network device based on receiving the downgraded clock quality indication from the second network device.

Abstract: A first network device may receive, from a second network device, a clock quality indication that is associated with a clock of the second network device, wherein the clock of the second network device is a reference clock for a network that includes the first network device and the second network device. The first network device may determine, based on a clock signal of the second network device, that a quality metric of the clock does not satisfy a threshold. The first network device may provide, to the second network device, a clock fault notification to cause the second network device to downgrade the clock quality indication transmitted by the second network device. The first network device may select a new reference clock for the first network device based on receiving the downgraded clock quality indication from the second network device.

Abstract: A first device may provide, to a second device, a first message that includes a first request for a first type of precision time protocol (PTP) message and a second request for a second type of PTP message. The first device may receive, from the second device, a second message based on the first message. The second message may identify whether the first request and the second request are granted. The first device may provide, to the second device, a third message that instructs the second device to provide a first set of messages, associated with the first type of PTP message, and a second set of messages associated with the second type of PTP message. The first device may synchronize a first clock of the first device with a second clock of the second device based on the first set of messages and the second set of messages.

Abstract: A first device may provide, to a second device, a first message that includes a first request for a first type of precision time protocol (PTP) message and a second request for a second type of PTP message. The first device may receive, from the second device, a second message based on the first message. The second message may identify whether the first request and the second request are granted. The first device may provide, to the second device, a third message that instructs the second device to provide a first set of messages, associated with the first type of PTP message, and a second set of messages associated with the second type of PTP message. The first device may synchronize a first clock of the first device with a second clock of the second device based on the first set of messages and the second set of messages.

Abstract: A first device may provide, to a second device, a first message that includes a first request for a first type of precision time protocol (PTP) message and a second request for a second type of PTP message. The first device may receive, from the second device, a second message based on the first message. The second message may identify whether the first request and the second request are granted. The first device may provide, to the second device, a third message that instructs the second device to provide a first set of messages, associated with the first type of PTP message, and a second set of messages associated with the second type of PTP message. The first device may synchronize a first clock of the first device with a second clock of the second device based on the first set of messages and the second set of messages.

Abstract: A device may determine a link master/slave relationship for an Ethernet link associated with a connection between a component of the device and a component of another device. The device may determine that Synchronous Ethernet (SyncE) is to be enabled on the Ethernet link. The device may identify the component of the device as a SyncE slave or a SyncE master associated with enabling SyncE on the Ethernet link. The device may provide an indication that the component of the device has been identified as the SyncE slave or the SyncE master. The device may determine a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link. The SyncE master/slave relationship may supersede the link master/slave relationship without altering the link master/slave relationship. The device may cause the component of the device to recover a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.

Abstract: A first device may provide, to a second device, a first message that includes a first request for a first type of precision time protocol (PTP) message and a second request for a second type of PTP message. The first device may receive, from the second device, a second message based on the first message. The second message may identify whether the first request and the second request are granted. The first device may provide, to the second device, a third message that instructs the second device to provide a first set of messages, associated with the first type of PTP message, and a second set of messages associated with the second type of PTP message. The first device may synchronize a first clock of the first device with a second clock of the second device based on the first set of messages and the second set of messages.

Abstract: A device may determine a link master/slave relationship for an Ethernet link associated with a connection between a component of the device and a component of another device. The device may determine that Synchronous Ethernet (SyncE) is to be enabled on the Ethernet link. The device may identify the component of the device as a SyncE slave or a SyncE master associated with enabling SyncE on the Ethernet link. The device may provide an indication that the component of the device has been identified as the SyncE slave or the SyncE master. The device may determine a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link. The SyncE master/slave relationship may supersede the link master/slave relationship without altering the link master/slave relationship. The device may cause the component of the device to recover a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.

Abstract: A device may determine a link master/slave relationship for an Ethernet link associated with a connection between a component of the device and a component of another device. The device may determine that Synchronous Ethernet (SyncE) is to be enabled on the Ethernet link. The device may identify the component of the device as a SyncE slave or a SyncE master associated with enabling SyncE on the Ethernet link. The device may provide an indication that the component of the device has been identified as the SyncE slave or the SyncE master. The device may determine a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link. The SyncE master/slave relationship may supersede the link master/slave relationship without altering the link master/slave relationship. The device may cause the component of the device to recover a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.